Jonathan Blow

Hmm, I thought your main objection was the stuff about "they are buggy and clumsy and have weird failure states". For me as a spectator, it seems like they're at least following the right trail in that regard...

Well that's one objection of many. But a big part of the bugginess is not the bugginess of the individual programs, it's that they are combined via loose coupling, communicating with non-statically-typed textual data.

man... I'm actually SUPER torn on that one. A lot of devs might benefit from not getting anything but passing textual data as it could help them to see the complexity they're piling on top of basic, textual data...

Okay, but doing that under the Unix Philosophy is like programming in Javascript and passing strings between all your functions ... exactly the opposite of the idea of writing stuff in Rust. It does not scale.

Actually, it's like programming in Tcl, even worse than programming in Javascript...

Hah! Well, I wouldn't subscribe to that interpretation. There is communication between programs and the files they operate on between them. The latter part is definitely whrer you want well specced and designed stuff. "oh just handle text for chrissake" has its place tho imho

I think it's fine to have text as an option. But you should also be able to get structured + fast data instead.

Yes! I guess I'm just tired of seeing people building their babylonian towers when more than half of their designs could be moved to the OS, making the other half a lot more pleasant to deal with.