When Unix was released, the USA was still doing missions to the moon ... that's how long ago it was!
-
-
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.
-
That's my working hypothesis, anyhow. So far, it has not stopped astonishing me with how much complexity you can avoid with it. I don't have a final verdict, though.
-
Also - I'm mostly working on (web) content, which I know you don't have much love for, so our perspectives are quite different.
End of conversation
New conversation -
-
-
I thought the everything-is-a-file paradigm in conjunction with these small, interoperable programs, handling only byte streams, were the actual key to success. ¯\_(ツ)_/¯
-
It was the actual key to success in 1970.
-
So? Which problem are you trying to solve?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
