bitmapper

It would be, if the code wasn't so horrifically bitrotted at this point. GHC has changed a lot since Elm last got any meaningful update, and they decided to use unsafe GHC primitives everywhere that have no support guarantee. You have to fix a bunch of issues with the compiler source before it will even compile on a relatively new version of GHC.

this got replaced with ghcup iirc

What do you mean the function to create a directory? When would you be creating directories outside of derivation build phases?

This is just a ChromeOS tablet except it's running a customized version of ChromiumOS?

There's cadmium there, yeah. But cadmium is not addictive, and is not a reason for cigarettes being addictive. Removing the cadmium will not make cigarettes less addictive.

Tobacco plants pull metals in from the soil, which includes cadmium, and radioisotopes of polonium and lead.

For simple languages, it can be a bit of a pain to write and maintain a lexer and a parser. For example, if I'm gonna parse JSON and nothing more, I think it's a bit silly to use a two external DSLs when I could use a simple eDSL. I think Happy and Alex both have their places, absolutely. For parsing full on programming languages I can imagine using parser combinators to be a bit painful. But parser combinators work great for a lot of cases.

I'm really not a fan of IHP for that purpose due to how it redefines so much of the Haskell Prelude without making it clear it does that.

I personally don't like Rust (I like to have a garbage collector for what I do), but I don't think it's a hard to read language.

Readability is an incredibly subjective thing. For example, APL might look like an absolute mess to most people but to the people who know it, it's incredibly easy to read. All "readability" means in this context is that it's familiar to you.

In my opinion, the only truly hard to read languages are languages that require you to keep large amounts of context in memory while reading a specific part of the codebase, be it due to lack of support for abstractions for proper encapsulation, messy overloading, insane inheritance hierarchies, or something else.

EDIT: Readability also requires you have a codebase that's well written, and even that's subjective.

Parametric polymorphism is even older than that! It's almost 60 years old, having originated in CPL.

Honestly, my main issues are with the lack of generics and the "dynamically typed effect system". The idea of a minimalist runtime and language reminds me of Clean a little bit.

Fair enough! Sorry, I didn't intend that to be rude, I just genuinely didn't understand as it seems to be two very conflicting ideologies merged.

Since when are generics automatic casting?