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

getting nostalgic for morrowind

Hi! Glad to see you here

VIDEO VIDEO

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?

hahahaha well done

(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

"the croconony" 🙀

til "crocs charms" are a thing