Viewing profile — JeffreySnover

Step by step we've been doing more and more focused on Linux users. If you take a look at our telemetry - it is clear something is working because Linux usage is through the roof!!…

Those youngings probably don't remember what the Germans and Japanese did in the 40's either. Or the good old day's when Ultrix ran like a racehorse on 4MB of ram (it did BTW!). We…

That's not quite right. We have always focused on CUSTOMER success. You are right that there is self interest in that (as Satya likes to say - it is hard to be successful if your c…

There are enough examples of companies doing terrible stuff that concerns are entirely understandable. Let me take the opportunity to say: 1) YOU ARE NOT OUR PRODUCT! 2) Our goal i…

Process creation on Windows has always been significantly slower than Unix. That is why PowerShell is skewed towards "built-ins" vs launched applications. The ramification of that …

If you have modules in your module path that don't declare their exports in the manifest, PowerShell has to inspect everything to find all the cmds. This is often what is going on …

The second half of the quote is, “but sometimes it takes us a couple decades to get right”. :-) Seriously though, have you checked out the search in O365? It is starting to get rea…

We thought about that but the reality is that it does not work well for interactive experiences. When you look at how admins get their job done, it starts in the interactive shell …

Syntax is like ice cream. Some people like vanilla. Others like chocolate. Jeffrey Snover [MSFT]

PowerShell was designed to provide a very wide dynamic range of capabilities from interactive actions to simple ad hoc scripts to more formal programming. The goal was to have a si…

That is correct (prevent accidental script execution). It is ABSOLUTELY NOT a security mechanism. That is why we we support this: Set-ExecutionPolicy -ExecutionPolicy Bypass I want…

Yikes! - you shouldn't have to do Set-ExecutionPolicy every time you start a shell. Something is definitely wrong there. Try doing a: Get-ExecutionPolicy -List to see what is setti…

That was the approach I took before inventing PowerShell. We didn't WANT to invent a shell - we were forced into it. The problem was that Bash on Windows wasn't effective. At the h…

Here is how you do that: $PSDefaultParameterValues["Out-File:Encoding"]="utf8" Jeffrey Snover [MSFT]

That is right. CMD.exe will be around to support script execution for a long long time. Jeffrey Snover [MSFT]

Major improvements in V5. Even more in V5.1 (which ships with WS2016). But still slower than CMD. CMD starts very quickly but then you have CMD. :-) Jeffrey Snover [MSFT]

I've never quite understood the concern about needing to Set-ExecutionPolicy before running scripts. In Unix, you have to chmod a+x a file before running it. And you have to do it …

That is a good tip. There are certain product teams that produced ENORMOUS objects and your suggestion helps when dealing with that. Jeffrey Snover [MSFT]

We are incapable of sustained error. 25+ years was enough. :-) Jeffrey Snover [MSFT]

Sorry about that - we lost control of our startup times in PS V3 and have been working to get it back under control. PowerShell V5 had substantial improvements but we keep working …

FYI - we don't charge for PowerShell. Jeffrey Snover [MSFT]

That is how we got started on this. We didn't want to invent anything here. We had a technology called Services for Unix which provided all the shells and utils and I got 99.5% of …

We have a hotspot compiler. We have talked about having it create a stand-alone executable but it has always fallen below the cut line. Jeffrey Snover [MSFT]

Everyone has a family to feed right? There is no shame in trying to make money. Satya was super clear on this point - he told us to get out of our offices and go talk to customers …

Yes but I think the better solution is to fix the alias problem and then work with Daniel to make it super simple for people on Windows to get his latest/greatest bits. I've reache…