> UNIX commands are more an accident of history than a cohesive, coherent, composable design. PowerShell was designed. It was designed by one person, in one go, and it is beautiful.
I'm curious about that design and would love to learn about it.
Note, that I'm not interested in learning how to actually use powershell as a developer, but understand the abstraction design choices, that went into it.
Every time I tried to learn about that, I'd find recommendations about Books with 1000+ pages and similarly time consuming resources.
Do you have an recommended read for understanding the design choices, that went into powershell, while not learning the details, that a everyday windows would need?
Things I care about:
-How do Lamdas work?
-Arrays are Objects. How exactly? -Typesystem
-Are there native wrappers for the kernel APIs how do they fit into the objectmodel?
-Since to my understanding no shortflags exist, how is verbosity avoided?
-How thight are interfaces defined. If a tool provides a new interface in a new version, can old tools still work with it?
I'm curious about that design and would love to learn about it.
Note, that I'm not interested in learning how to actually use powershell as a developer, but understand the abstraction design choices, that went into it.
Every time I tried to learn about that, I'd find recommendations about Books with 1000+ pages and similarly time consuming resources.
Do you have an recommended read for understanding the design choices, that went into powershell, while not learning the details, that a everyday windows would need?
Things I care about: -How do Lamdas work? -Arrays are Objects. How exactly? -Typesystem -Are there native wrappers for the kernel APIs how do they fit into the objectmodel? -Since to my understanding no shortflags exist, how is verbosity avoided? -How thight are interfaces defined. If a tool provides a new interface in a new version, can old tools still work with it?