3 ms·
> Powershell improves on Unix commands being based on text streams, and makes them based on objects I assume this means that PowerShell is deeply integrated wi
by paskozdilar 4y ago
> Powershell improves on Unix commands being based on text streams, and makes them based on objects
I assume this means that PowerShell is deeply integrated with the .NET ecosystem? I don't like .NET very much, so that's a downside for me.
One of the reasons I use Bash is the decades-old ecosystem of various utilities people have written. Can PowerShell use the same CLI utilities as Bash, and do the plain-old-text-stream processing pipelines like Bash, or is it .NET objects only?
- majkinetor 4y ago> I don't like .NET very much, so that's a downside for me. LOL. So arbitrary... do you like java vm or python? > Can PowerShell use the same CLI utilities as Bash, and do the plain-old-text-stream processing pipelines like Bash, or is it .NET objects only? Sure. Even better, it can convert wall of text into array of lines on the fly :) You should forget about parsing text in shell though. Because it sux and we know better now. Parsing text in pwsh is once-a-year thing.
- deleted 4y ago[deleted]
- paskozdilar 4y agoYeah? Well, you know, that's just, like, uh, your opinion, man.
- majkinetor 4y agoYours is not even opinion. You need to put some logic behind it man :) As for me, I will keep my Decade-And-More-Old-And-Still-Shiny-Shell-With-Objects-And-Stuff to myself :)
- paskozdilar 4y agoI don't think I need to "put some logic behind" not liking .NET, same as I dont need to put some logic behind not liking Java. It just sux and we know better now :) Also good luck with your emacs pinky. :) :) :) :D :D :D :) :) :^)