4 ms·
'Separating interface from engine' clashes with the shortsighted 'text is the universal interface' rule. A great deal of Unix prefers the latter to the former
by nailer 17y ago
'Separating interface from engine' clashes with the shortsighted 'text is the universal interface' rule.
A great deal of Unix prefers the latter to the former - eg, hunting for a regex to identify some data rather than being provided with something which properly separates the data from the presentation.
Object pipelining shells (powershell) and higher level shells (ipython) get this right.
- thwarted 17y agoThere was an endeavor to create versions of all the shell utilities that take and generate XML streams before powershell, but it never caught on and I don't think it got very far.
- eru 17y agoPerhaps S-Expressions would have been more hacker-y? XML smells of pointy-haired bosses, nowadays.
- thwarted 17y agoThis was before XML acquired the, ahem, "seriousness" of the rep it now has. Really, I don't think the exact format mattered, because it would only be used between the processes themselves, you'd use some kind of formatter on the output end to produce something actually readable. The transport format isn't what killed it; one might argue that flat text is good enough, and that's what killed trying to create an alternative inter-pipe format. I still think it's a good idea, but even the success of powershell (how often do you hear of someone actually using it?) says it's not going to go anywhere.
- gnosis 17y agoPowershell seems to go against the whole "Windows philosophy" (ie. monolithic, inscruitable, and dumbed-down). More seriously, I have no doubt that many Windows admins are using it, but it's not likely too many typical Windows users even know what it is.
- nailer 17y agoIt's pretty common these days - most Windows infrastructure folk I work with check a new product for Powershell support as a purchase condition.
- thwarted 17y agoAdmittedly, I'm no longer seriously in the market for Windows software (and haven't been for a long while), so I wasn't even aware that "powershell support" was a possible selling point. What are some examples of software that do have powershell support? I could see it making a big difference with some system management tasks.
- silentbicycle 17y agoWell, none of these are hard and fast rules, just rules of thumb that let you work with Unix's strengths. For example, if you store your data in config files, you can keep them in git (or whatever), and neither has to know anything about the other. Text isn't the universal interface, it's just a simple one. You wouldn't stream video data as text, but that's because there are other major factors that make doing so an unreasonable trade-off.