thowaway202107
I don’t think its evangelical as much as protective.
I for one have had to endure grueling years of working in open office environments. I’ve got pretty severe adhd and anxiety, that’s not a good place for me.
With covid, the world shifted to working how I prefer. I’m terrified it’ll go back to how it was.
So I’m sorry it’s been a rough couple years for you, but please understand that it’s been a rough lifetime for people like me.
Because office work is still the default mentality for most people, this new world that’s aligned to my needs is in constant jeopardy.
IO on it’s own could mean disk, network, environment variables, sub processes, etc.
My take away is that they’d like to see IO defined as the union of its parts that can also be decomposed, so you’d have a DiskIO monad or ExecIO
That way you can be more certain that you’re not accidentally going to do a bunch of network io before your sub process kicks off. Right now you can’t have that guarantee (out of the box, at least. idk if there’re any user land libraries to do such a thing)
And released it with NO WARRANTY. And no mega corp thought it’d be a good idea to try and buy one.
> To me, this is the pretentious part. I didn't write the code, I don't use the code, so why in the world should I be expected to fix the code? Do you use the code? Why didn't YOU fix it?
If you don’t use it, then noone’s expecting you to fix anything. But those out there using it for free, complaining that it’s broken, and not doing anything to help? They should hush their hush holes. Or open pull requests. But mostly hush their hush holes.