3 ms·
if the only problem with PowerShell is that it feels clunky and annoying, why not try to extend/improve it (like Kotlin over Java)? Why start a new project that
by black3r 6y ago
if the only problem with PowerShell is that it feels clunky and annoying, why not try to extend/improve it (like Kotlin over Java)? Why start a new project that will maybe catch up in X years?
- mehrdadn 6y agoI can imagine lots of reasons. To build on PowerShell means either integrating your changes upstream (not likely, given fixing some of the clunkiness would require breaking changes) or maintaining a separate fork and incorporating patches from upstream constantly (a lot of work, and constant conflicts aren't fun). Plus the fact that PowerShell is .NET-based and not the most snappy shell out there either. Plus the fact that extending something requires investing a lot of work just understanding how things tie together, and then avoiding messing up all the hacks and idiosyncrasies added along the way instead of having a clean slate to build on.
- kanobo 6y agoI'm not the author but it's probably for the simple reason that writing something from scratch without dependencies can be extremely rewarding and fun.
- kevin_thibedeau 6y agoPowerShell is tied to the CLR APIs. You shouldn't have to run a Mono instance just to get basic shell behavior.
- nickcox 6y agoPretty sure you don't need Mono to use any modern version of PowerShell.