My Impressions of Hare

That’s a good point! I find the lower cognitive load and thus the ability of “understand” instead of trusting on multiple layers of abstractions intellectually stimulating!

Sure, I’m still trusting on a compile and an OS and a handful of libraries, but that is certainly a lot less than the standard, say, node.js app out there with a couple thousand npm dependencies.

Insufficiently expressive languages make the code long and repetitive. It becomes longer to read and harder to understand the intention. Hence more bugs go unnoticed, not less.

I'm speaking as someone who reads more code than writes for many years.

I nevertheless agree that writing clever code is a bad idea. Code should not be a riddle. But writing smart code is helpful in many ways. Dumbing down a language in order to prevent people from writing clever code looks like an obvious idea, but even such spartan language as C has numerous examples of contrived code, like the Duff's device. A more expressive language won't need these contrivances.

Genuine question, as someone who is approaching the 10 year anniversary of working in the industry: how do you deal with the inherent verbosity and bare-ness that come with that level of simplicity? To this day, loops that aren't of the standard "go through array in order" kind still take me longer to parse mentally than some map/filter/reduce calls ever did, and repetitive/uniform code (like error handling in go) makes it very difficult for me to catch the details. And that's the code I've read (and had to write) for most of my professional career (most of it was procedural legacy software), so I don't think experience is the problem (unless I need more, in which case fair enough). But I think I haven't been able to make the mental switch to be able to separate the important details from the noise, and I don't really know how to

> And while the code in more complex languages can still obviously be readable, simple languages force the code to be at least somewhat readable even at its worst.

Derived implementations of things like `equals`. An advanced language feature I guess. Easy to read in the complex language, longer to read in the simpler language, and something you have to keep in mind to update manually or regenerate when you update your data structures.

There’s this elephant in the room. But it name shan’t be mentioned. Explicitly.

Nim’s automatic memory management is explicitly designed to work efficiently on embedded systems.

> Pretty much any automatic memory management will need to be disabled or worked around when developing embedded systems or operating systems.

I have done a fair amount of hobbyist development with Rust on embedded devices. The naysayers make this sound difficult; it isn't at all.