brundolf

There is fun friction and unfun friction. Game design is distinguishing the two. But optimizing for minimal friction will sand off engagement itself

The point of a game is not to be Convenient. The friction is the entire game

Bad UX is often good game design. So much of the industry doesn't get that

getting nostalgic for morrowind

Hi! Glad to see you here

VIDEO VIDEO

I wonder if AI vulnerability-finding tools will further accelerate unsafe languages' decline

Rust actually hit this issue, and that's why rust-analyzer is a whole separate project

But if you start out designing for these constraints, it's very easy to go back and say "ok now just do this on all the files at once and then take the ASTs and compile them"

Which means, a classical compiler that does one pass on everything, and then the next pass on everything, stopping at any point where things are broken, won't really work as a starting point for an LSP

Sorta! Except it needs the ability to partially-reevaluate and cache not just individual files, but individual bits of files. And to make sense out of partially-formed syntax and do its best, so it can provide type checks and autocomplete as you're in the middle of editing

Don't know about Steve, but on my most recent language project I actually started with the language server because a) it's much easier to make a compiler out of an LSP than the other way around, and b) it gave immediately satisfying feedback which made development more debuggable and fun

This is the first I'm hearing about ruelang. Got anything I can read?

Did you try different tip sizes?

americans in fifty years denying our nation’s unforgivable crimes during the early 21st century:

hahahaha well done

Purpose-built gadget idea: a little LED display you can plug in with USB that always shows the computer's current IP address on the local network. For little servers you don't want to plug a display into

(you can of course put resetMocks in a beforeEach clause, but you still have to remember to do that)

For example: by default, mocks made in one test will affect all the other tests in that module. To isolate tests from each other, you have to remember to call resetMocks() before each of them

I can't imagine a situation where you would ever want the default behavior, much less expect it

Made by and for crazy people

Jest (javascript testing framework) has the most batshit insane default behavior

anyone out there who has had music removed from spotify due to false accusations of artificial streaming — is there any recourse besides re-uploading stuff?

The @oxide.computer podcast has made me better at debugging

"the croconony" 🙀

til "crocs charms" are a thing

screenshot of classic dril tweet that reads: “This Whole Thing Smacks Of Gender,” i holler as i overturn my uncle’s barbeque grill and turn the 4th of July into the 4th of Shit

happy 4th of Shit to all who Smack Of Gender

‪Not specifically *creating* glitchy behavior, mind you. Then it isn't a real glitch‬

‪Just like... not trying to guard against race conditions, etc‬

A video game that intentionally uses poor coding practices to make glitches more likely to exist, because glitches are fun

It's weird that we don't have better tools for visualizing code

Simple example: if I want to reason about a function call tree that's a few layers deep, it's fairly miserable to get all that information visible at once on screen, and there will be lots of noise, if it fits at all

the way if/else is implemented in shell scripts ("[" is actually a command that accepts arguments, which is why it requires whitespace before and after itself)

No Kings, y'all 🇺🇸