(Not just for the HKP evo trajectory rundown but also for the takedown on currying and how excessive effort at pretending arity isn't a thing is actually ergonomically harmful: screamingly, YES! THANK you, author of this FAQ! You Nailed it!)

Man this FAQ just keeps absolutely hitting the notes square on about "and Here's Why your Pet Language Feature has Consequences" and I've rarely been so here for something

I'm trying to resist screaming "YES, EXACTLY" like a madman as I ride the train and read this lol

Holy smokes the faq discussion around HKP is GOOD

...maybe they're right and Result can do the work alone, but, I'd better find that there's either a named Unit/None/Bottom or else a syntax for creating a universally equal value to that effect, or I'm going to be annoyed at the miss.

The crime of null was making it implicitly possible Anywhere, without talking about it clearly.

Maybe/optional already address that.

Being precious about not having a stdlib/prelude/whatever type called none/empty/unit/etc strikes me as purely strange. 🤷 and prob net neg but i should wait+see ig.

www.roc-lang.org/faq#option-t... weirds me out a little. It's valid to call null bad names but having a default-named unit type is not imo a bad thing.

Starting a peano arith from unit on up is also theoretically pure.

I basically don't see any reason to be precious about this.

Love www.roc-lang.org/faq#import-e... and the aggro "no". This is also one of the things golang did right and I think effectively "all" languages that I consider as "serious" from here on out must do.

I like some things here! One of my first questions from tapping around the front page though is: are bang in function names an actual contract of some kind? Or is that vibe and "you should"? Because it's being presented energetically and if it's the latter my enthusiasm is going to invert..

👀👁️👁️

I have not, tho 😭

Way too much syntax maximalism.
Standard library is ass.
Toolchain nightmares abound.
Don't even wanna talk about the "nightlies" circus.
The autoformatters are a crime against attention spans and difftools alike.

It tries in some ways but it is not a good place right now.

Not *a lot* more expressiveness, mind. Golang's commitment to syntactic minimality IS virtue.

But we need
Sum Types,
exhaustive match checking,
less caveat-filled generics,
typed errors(!),
and a serious engagement with the syntactic burden of error handling, since it truly is a majority of code.

It remains until to me if that material I was reading was *willfully* bad reporting and headlining, or if the author and editor was just kind of embarrassingly clueless.

+1, read several articles about datacenter water impacts and they buried the lede on this, SO hard. But once one dug into the article and the actual people quoted, it was pretty clear it was poorly planned construction impacts.

Sometimes it's reading comprehension fail, sometimes it's outright psychosis.

How a screenshot, of all things, becomes a canvas for psychosis, I really don't know and can barely comprehend the irony of. And yet...

There's a certain kind of person (possibly having a certain kind of mental breakdown, idk) who thinks having a screenshot of your profile granted them automatic victory in an ad hominem battle that no one but them was playing.

I don't get it, but I'm starting to recognize it as a pattern. 🤷

I simply do not believe that I need to get angry in order to want safety and security for all; nor do I believe that my anger helps attain those goals

Cornbread.

You, too, can have a cornbread feed! You can just have nice things! Like cornbread!