4 ms·
The culture that kept Smalltalk alive failed. So it goes. My understanding is that it had schisms. I've worked with Smalltalkers; they talked like conquered peo
by ArkyBeagle 10y ago
The culture that kept Smalltalk alive failed. So it goes. My understanding is that it had schisms. I've worked with Smalltalkers; they talked like conquered people.
I PREFER - strongly - text-based because graphical based means some obscure binary protocol/file format that bitrots into obscurity. You can always learn to do hardcore text manipulation. You can't necessarily reverse-engineer, say, a Word 1.0 document.
Text is the cockroach format.
- TeMPOraL 10y ago> Text is the cockroach format. I.e. ugly and hard to get rid of? ;). The problem with Unix isn't text - it's unstructured text. Every utility needs to implement its own copy of ad-hoc, bug-ridden parsers to operate on the same data - and if you want to string some of those utilities together, you often end up writing ad-hoc parsers too. The sad thing is that we knew how to work with structured text. Then the Unix came and ignored all that experience.
- unimpressive 10y ago>The sad thing is that we knew how to work with structured text. Which is?
- TeMPOraL 10y agoS-expressions for instance, which were popular back then. JSON is a modern reinvention of that particular wheel.
- thomasahle 10y agoYup, having more structure and types would be nice. However, that would require effort from all application writers, where as unstructured text is what they'd naturally output, and it works well enough for most things.
- ArkyBeagle 10y agoHere, let me show you my ASN.1 ... :) Or worse, my TL1. :)
- Something1234 10y agohttps://en.wikipedia.org/wiki/Abstract_Syntax_Notation_One https://en.wikipedia.org/wiki/Abstract_Syntax_Notation_One https://en.wikipedia.org/wiki/Transaction_Language_1 https://en.wikipedia.org/wiki/Transaction_Language_1