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 Office Excel spreadsheet
and windows partial terminology the table or spreadsheet is a collection of objects or just collection
for shot each row in a single object.
And each colon is a property.
When you run get service the command produces a collection of soulless objects.
Each has properties like name display name status and so on.
Windows for Chelsea use of object is very different from all their command line shells whose commands
primarily generate text in a text based shell.
Suppose that you wanted to act 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 pipe that text to a second command by use in
parameters to define a particular call and position that contains status information in 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 with text bars.
This makes scripting languages such as Perl popular because it offers drawn text Bosson and text manipulation
features in Windows shell.
It would just tell the shell to produce a collection of service objects and to then display only the
name property.
The structure of the objects and memory enables the shell to find the information for you instead of
you having to worry about the exact exact form or the command output working with objects is much easier
and gives you much more possibilities.