PowerShell is open sourced and is available on Linux

Post by fsloth » Fri, Aug 19, 2016, 4:15 AM UTC

vardump wrote: post #519

fsloth wrote: post #467

Earlier quoted context omitted.

"Something as simple as finding next text search match takes about a second." I'm not sure how our configurations differ but on a fairly modern machine (say, surface pro 4 i5) I've not had visual studio 2015 slow down, and editing and searching is az zippy as with Vim for me. I've had the experience that some third party tools have bogged down the experience, though.

I mostly run it on a Xeon workstation with 32 GB RAM, SSD, Nvidia K5000, etc. I think you can call it a modern machine. Other software runs fast. I don't have any third party software installed on top of VS2015. Only unusual aspect is that I also have several other Visual Studio versions installed, like VS2008, VS2010, VS2012 and VS2013. I also have many Windows SDK and DDK (driver devkit) versions. But that shouldn'…

Post by witty_username » Fri, Aug 19, 2016, 4:26 AM UTC

Senji wrote: post #581

acscott wrote: post #570

Earlier quoted context omitted.

Microsoft does not grow food, build houses, create clothes, cars, or protect you from foreign invaders. The basic human needs are not met by MS. The business that claimed that open-source was a cancer is just a marketing company with memetic feedback loops. Plenty of over Operating Systems are out there. Their office product is no longer relevant (vis. a vis. Libre Office, Google Docs, and others). Are you telling me…

>Their office product is no longer relevant (vis. a vis. Libre Office, Google Docs, and others). You have no idea just how wrong you are. Excel has no competitor worthy of even talking about. Libre Office is a mess. Google docs doesn't do everything word can and is in the realm of a toy web app.

Post by denfromufa » Fri, Aug 19, 2016, 4:50 AM UTC

JeffreySnover wrote: post #42

tombert wrote: post #9

I'm always in favor of things being open-sourced, but I do kind of wonder in what universe I would use PowerShell when Bash is readily available.

It is just another tool in the toolchest. As you know, on Linux, there are tons of great interactive shells and it is sortof a lifestyle choice. You might want to kick the tires and see whether it fits your lifestyle or not. If you use Bash as your shell, think of PowerShell as you would python or perl - something you write scripts in and call from Bash. Jeffrey Snover [MSFT]

Post by ygra » Fri, Aug 19, 2016, 4:57 AM UTC

elchief wrote: post #513

ygra wrote: post #458

Earlier quoted context omitted.

PowerShell defaults to UTF-16 encoding, indeed. It's a design choice on a system that uses UTF-16LE as its character encoding and one from the early 2000s. UTF-8 wasn't nearly as prevalent back then. However, the text in both files is still the same. Get-Content -Tail some1gbfile.txt works quite well, by the way.

well, enjoy typing Get-Content -Encoding utf8 .\utf8.txt | Out-File -Encoding utf8 out.txt and manually removing the BOM, for the rest of your life

Post by beefield » Fri, Aug 19, 2016, 5:06 AM UTC

CrLf wrote: post #506

Analemma_ wrote: post #6

PowerShell is my guilty pleasure of the computing world. Once you've piped strongly-typed objects around between your shell commands, text scraping seems barbaric by comparison. The problem, of course, is that you can't use all that power for much, since the pool of PS-compatible tools and utilities is much shallower than it is for Unix shells. I'm really hoping this will help spur a new wave of PowerShell-compatible…

After a number of years using PowerShell, my conclusion is the opposite: text "scraping" is just better for most cases. Normal shell usage means doing a lot of one-shot pipelines incrementally. This is just easier and faster to do when passing text around because you can look at it and not have to inspect some object for it's type and what attributes/methods it provides. Parsing the text is not the problem here (alth…