4 ms·
This isn't an issue of shell syntax, you're pointing out that the ps tool emits structured output which can be queried in standard ways by downstream filters.
by ajross 13y ago
This isn't an issue of shell syntax, you're pointing out that the ps tool emits structured output which can be queried in standard ways by downstream filters. Which is great, as a user feature.
Now explain how to write a "ps-like" command which emits mostly the same stuff and coexists in the same universe. Now things flip: unix is straightforward and easy (everyone understands how to emit text, and you can do it from literally every programming environment there is) and windows is arcane and inscrutable, and works only with whatever .NET framework understands that log stream.
Fast forward a few decades, and examine the size of the ecosystems built around "simple tools and text streams" vs. "custom logging format plus cute syntax".
It's a forest for the trees argument. Microsoft, as always, optimized for the wrong part of the problem. In this case: the admin experience is great, at the expense of the developers of the tools those admins would need to run.
- nailer 13y ago> Which is great, as a user feature. Yes, exactly. There are far, far more users than complementors (tool creators) in this space. Optimising for users is excellent, and smart tool creators will see and appreciate the benefits.
- ajross 13y agoExcept they don't, as witnessed by this thread. Powershell is a ghost town. No one uses it, because there are no meaningful tools that use it. With ssh and rsync and git and bash and whatnot, I can script up a remote deployment or replication system for a simple task in a few hours. To extend your ps example, I can throw in a little awk or perl and spit out a clean report of suspected memory hogs. Where is the powershell ecosystem? It doesn't have one, sorry. Syntax can only take you so far, and as I pointed out Powershell designed for syntactic power at the expense of extensibility. And it made the wrong choice.
- nailer 13y ago> Powershell designed for syntactic power at the expense of extensibility. And it made the wrong choice. A decent syntax is orthogonal to extensibility: Powershell uses .net because Microsoft likes .net. A Python, Ruby or node-based equivalent wouldn't use .net, and still have a clean syntax.