Mh, the unix philosophy I know is another: to reduce costs instead of creating a fully graphical and featured environment we just need a basic system with small

Mh, the unix philosophy I know is another: to reduce costs instead of creating a fully graphical and featured environment we just need a basic system with small programs acting like functions users can combine with some IPCs. This allow to reduce costs while not limit much users computers usage. Unix break it's own rules adding graphics environment who do not nor can follow it's own philosophy. The everything is a text stream is a good principle, unix fails to implement enough. Plan 9 implement it better but was simply too late to have a chance and yes, both fall because they choose to avoid Lisp and the concept of OS as a single application. On contrary modern ideas trying to supersede absurd limits of modern OS design like the modern web with JSON and co prove to be an excellent source of bugs and still being far behind the power of classic systems because they completely fails in the basic principle to put the user and user programming at the center doing on contrary their best to give something to some intermediate levels (like devs) AVOIDING give real power to users. PowerShell is the apotheosis of a systems designed by people who are very skilled in mere programming without ANY CLUE on the purpose a desktop computer should have, and that's why is something modern programmers love while sysadmins and users prefer to avoid. You are right stating that we can't made good software with JSON and so passing as IPCs, but you fail to see the classic model instead of PS. PS is very well designed in software engineering terms, and it's then perfectly useless for a casual user usage. An org-mode table is not much a good idea in software engineering terms, but it's perfect for casual usage. That's the point.