l'empathie mécanique @dpwiz@qoto.org

@ZDL @Ambulocetus @grrlscientist TLDR: it went badly and had to be reverted. I would like to provide an authoritative source, but I'm not sure what counts as such for you.

@AmenZwa I'm worried though about BNFC. It feels too much like pleasing the toolchain instead of working on users' needs. Basically this is why we have stuff like semicolons and other redundant syntax -- to make the parsing simpler instead of focusing on ergonomics.

@AmenZwa My favorite Haskell bookcamp!
Impressive learning-to-length ratio.

@kaleissin @haskell Since the repo has stack.yaml and no cabal.freeze you'd have more luck installing it with stack. (use ghcup anyway, though)

my, the repo needs some love..

[Narrator: He was not, in fact, right.]

… terminated by signal SIGSEGV

@grumpy_website If it knows what to do, then it should just do that and not pester you with such trivialities.

log levels --> nag levels

@bascule Good. Can we please stop degrowthing ourselves back into caves now?

@zeux

@Mastodon While it would be nice to have a way to avoid X, the crux is that lots of people are just migrating from one silo to another instead of adopting the Fediverse. And the officials are the regular people too.

> single-header library
> looks inside
> 3.5 MB code dump

@tristanC It is advent of hardware now! 🦾

@haskell `type String = [Char]`

@jack @marianoguerra ditto FSMs

@jack @marianoguerra "S-expressions are the well-known solution to every syntactic problem—neat, plausible, and wrong."

@wilfredh They usually do follow-ups, but in some lame way.

But to ask for clarification is rare indeed. They should do this more instead of smugly answering the wrong question.

@carnage4life You can replace some of the human workers. And in time will replace more. This is a non-negligible effect already and will get more profound with time.

@cbarbermd It was already known in 2019. Did we do something about it? Nope.

With OOP you're always just one step away from *oops*