Most Windows partial commands do not generate text as output.
Instead they generate objects or object is a generic word that describes the kind of in-memory data
structure you can imagine command output looking like a table or a Microsoft or Microsoft Office Excel
spreadsheet and windows Polish shell terminology the table or spreadsheet is a collection of objects
or just collection for a shot.
Each row is a single object and each one is a property.
When you run get service like a command produces a collection of service objects.
Each has properties like name display name status and so on.
Windows for shells use of object is very different from all the command line shells whose commands primarily
generate text in a text base.
Suppose that you wanted to put in a list of all services that were started you might run a command to
produce a text list of services you and you would then BYB that text to a second command by using parameters
to define a particular call and position that contained status information if the output of the first
command ever changed and the status information moved you'd have to write the second command to have
the new position information.
So text based shells frequently require great skill risks.
Barsoom this makes scripting languages such as Perl popular because it offers strong text parson and
text manipulation features in Windows for Shell.
Just tell the shell to produce a collection of service objects and to then display only the name property.
The structure of the objects in memory enables the shell to find the information for you instead of
you having to worry about the exed exact form or the command output working with objects is much easier
and gives you much more.