Installing a new program:

The program I want ............4.5mb
Entire Haskell runtime.....432.9mb

So, that might not have been worth it.

On the other hand, I now have a Haskell runtime, so I've got that going for me

@codesections
Not a fan of runtimes but I acknowledge that storage is less expensive than manhours these days.

@DistroJunkie Yeah, agreed. I'm not really *complaining*. I mean, for that matter, most of my real programing is in javascript/node, which isn't exactly a lightweight runtime. Just observing

@codesections
I remember dealing with memory with Kb limits as opposed to MB or GB. We spent much time conserving memory at the expense of manhours. That trend has reversed.

@DistroJunkie And I'm all for conserving manhours. On the other hand, there is something to be said for actually understanding what's going on under the hood instead of stacking abstractions on top of abstractions—and working to save Kb can be one way to keep something simple enough to be understandable

@codesections
Fortunately(or unfortunately) I still think this way. I like to code in C and it's not unusual for me to develop something just as quick as one of my younger cohorts might do it in JS or Python. I don't think they could do that in C but I could probably get close to them in JS or Python. And that is why JS and Python rule the web. We've dumbed it down. It's kind of like Rembrandt vs Arts&Crafts.