bona fide busta

Will Smith just slapped Chris Rock at the Oscars #wow #ohmygod

i am experiencing Simpsons of anxiety

@georgetakei@universeodon.com hey man you're an insanely annoying liberal. fuck you

really wish i killed myself 7 years ago. would've saved a lot of unnecessary pain

@tekknolagi@mastodon.social yeah this situation sucks, my condolences

i want to die

https://www.youtube.com/watch?v=jU_rpkJSulE

the obvious parallel here is "wouldn't it be super annoying if you could never write a lambda / anonymous function, and every single function had to be named in a function declaration?"

really disappointed with Haskell rn. i expected it, of all languages, to avoid cumbersome bloat when it comes to definining types. but you can't just say some function's parameter is allowed to be `Number or String`; you need to introduce a new type, bind it to a name, then add names for every option, e.g. `data SomeType = N Number | S String`. i just added 3 new meaningless names to the current context -- SomeType, N, and S -- to change one parameter!

as I understand it, this is due to Haskell having "nominal" rather than "structural" typing, but I'm not sure if/why the two forms can't be mixed to allow *optional* naming

@charlotte@trans.enby.town oh shit they finally added a parent selector lfggg

@puzzled_squid@mastodon.gamedev.place just thought of a neat sidestep of the 3D camera problem: simply don't render any terrain at all. We enter a kind of abstract cyberspace-style view where all that gets rendered is network devices. We now control an orbit camera around our packet as it moves and can see all nearby (player-owned) network devices through walls. With the obstructions removed, this also happens to function as a kind of 3D map of our network, which could help with problem-solving.

@puzzled_squid@mastodon.gamedev.place Hi, I had a lot of fun with Tunnet (I've just finished it, but now going back to try to 100% it). I desperately needed to suggest this to you: let the player send their own physical body wrapped up as a packet on a network.

The player writes a destination address, or better, control + LMB on any explored cell on the map which contains an endpoint (choose a random one if multiple endpoints exist in that cell), and doing so specifies the destination for them. Then they jump inside a port on any device and start getting pushed around like any other packet would.

You wouldn't need a complicated mid-transit 3D camera or high-resolution map display; even a scrolling console output like "RELAY... HUB... RELAY... FILTER... ENDPOINT 0.0.1.3... RELAY..." would still be a huge upgrade over walking. You could put that console log on the right-hand side of the screen, while leaving the regular map open on the left, and drawing an indicator highlighting each node's icon on the map (smoothly panning the travel indicator or the map itself as we reach each new node).

When the packet reaches its destination address, the player pops out at that device. If the packet gets dropped (which can also be manually triggered by the player), maybe the player pops out at the drop site and experiences a "shock" or "nausea" effect for a couple seconds, like they've taken a kick in the guts. Or, to make it harder, they reappears back at the source of their transit, like the transmission was "cancelled". In a "hardcore" mode, getting dropped could even kill the player.

This would solve a lot of the drudgery of long, tiresome walks back and forth, and increase the positive feedback for making a well-routed, low-latency, low-packet-loss network. It would also be a great long-distance/long-TTL alternative to the Tester for visualising the behaviour of packets (especially if you could eventually make a nice mid-transit 3D camera that follows the packet along the wire).

QOL: Remember the quick-travel destination address, so players can jump back in again quickly after making a fix.

QOL: let players jump into wires rather than device ports, with the player's position/orientation/velocity relative to the wire determining in which direction they flow. Together with the last QOL feature, this means they can jump into quick-travel as seamlessly as grinding in a skating game. I don't know if you've ever played Jet Set Radio Future or Super Mario Odyssey, but both feature very satisfying rail-grinding / wire-riding mechanics that speed up your movement. The hard part is getting the camera not to pop through to the "inside" of the voxel terrain.

QOL: endpoints with Hackers on them, infected endpoints, and devices too close to lava could cancel the transit or redirect the packet as if it were an incorrect address, and show a warning message in the travel log, rather than spawning the player into harm's way.

Thanks for taking the time to read this, and thanks for making a game with a really original mechanic!

@chrisdone@mastodon.social you're capable of doing good work, so it's deeply disappointing you're spending your time and talents stealing from the poor to give to the rich

@susam@mastodon.social quite pertinent at the moment as half of the game dev industry frantically searches for open graphics & games tools

@susam@mastodon.social not that Logo specifically is FP; I'm just interested in all kinds of abstractions/languages/interfaces for visuals, as it seems nightmarishly overly-complex at the moment (outside browsers), and even relatively old FP langs like Haskell and Racket seem to have utterly atrocious access to / workflows for graphics

@susam@mastodon.social would love if you could record any of these! very interested in FP approaches to UI and graphics

i would like all the genocide to end please

quick shoutout: death to Israel

@fortunesrun@mastodon.gamedev.place hell yeah v excited

@csepp@merveilles.town @oreolek@masto.astrra.space @j3s@merveilles.town omg good lookin out compadre!

@oreolek@masto.astrra.space @j3s@merveilles.town for ages I've wanted to make an extension for exactly this problem, except my plan was to save the attributes and contents of every input on the page so it could be helpful with long complex multi-stage forms with heaps of tiny input elements, too (imo that's the bigger problem needing automation, because users can easily copy from huge text inputs). thanks for the reference!

@paulg the fuckwit things you say encourages a culture of mocking you

@jarango lmao why do you think people who don't care about social media enough to put up with horrendous UX are "non-serious"? what is it with right-wing nerds constantly preening in public in a way that should embarrass a high-schooler?