JeffreySnover

6 ms·

1.
by JeffreySnover 7y ago
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!!! https://aka.ms/psgithubbi I don&#x2
2.
by JeffreySnover 7y ago
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 don't do our credibility any favor when
3.
by JeffreySnover 7y ago
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 customers aren't succeeding) but the PowerShell tea
4.
by JeffreySnover 7y ago
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 is to use telemetry to help us make better decisions about wh
5.
by JeffreySnover 7y ago
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 is slower startup times. Interesting note - it
6.
by JeffreySnover 7y ago
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 when you have terrible startup times.
7.
by JeffreySnover 7y ago
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 really good and wait till you see how this progresses in the n
8.
by JeffreySnover 9y ago
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 and then when the do things frequently, they put it into a s
9.
by JeffreySnover 9y ago
Syntax is like ice cream. Some people like vanilla. Others like chocolate. Jeffrey Snover [MSFT]
10.
by JeffreySnover 9y ago
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 single tool that admins and programmers could share to create
11.
by JeffreySnover 10y ago
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 wanted to make it: Set-ExecutionPolicy -ExecutionPolicy DoAnyth
12.
by JeffreySnover 10y ago
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 setting it. Then use -SCOPE on Set-ExecutionPolicy. BTW - I
13.
by JeffreySnover 10y ago
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 heart of the matter is the difference in architec
14.
by JeffreySnover 10y ago
Here is how you do that: $PSDefaultParameterValues["Out-File:Encoding"]="utf8" Jeffrey Snover [MSFT]
15.
by JeffreySnover 10y ago
That is right. CMD.exe will be around to support script execution for a long long time. Jeffrey Snover [MSFT]
16.
by JeffreySnover 10y ago
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]
17.
by JeffreySnover 10y ago
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 for every script you want to run. So to run 1 cmdlet to
18.
by JeffreySnover 10y ago
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]
19.
by JeffreySnover 10y ago
We are incapable of sustained error. 25+ years was enough. :-) Jeffrey Snover [MSFT]
20.
by JeffreySnover 10y ago
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 on it and V5.1 is even faster. Give it a try - I think you
21.
by JeffreySnover 10y ago
FYI - we don't charge for PowerShell. Jeffrey Snover [MSFT]
22.
by JeffreySnover 10y ago
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 the way to getting that shipped natively in Windows b
23.
by JeffreySnover 10y ago
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]
24.
by JeffreySnover 10y ago
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 and find out what they needed to be successful. "Don&#
25.
by JeffreySnover 10y ago
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 reached out to him to start that conversation. Jeffrey S
26.
by JeffreySnover 10y ago
Fair feedback - we are in learning mode. Jeffrey Snover [MSFT]
27.
by JeffreySnover 10y ago
When I had no customers - I had lots of flexibility. PowerShell is now installed on many hundreds of millions of machines. With great success comes great responsibility. We can and will change things but we have to do so in a thoughtful man
28.
by JeffreySnover 10y ago
Interesting hypothesis! I'll ask Bill the next time I see him. Jeffrey Snover[MSFT]
29.
by JeffreySnover 10y ago
There are lots of aliases for cmdlets for exactly this reason - interactive use. The verbose commands are useful when reading a script that isn't working at 3am in the morning when your boss is breathing down your neck to fix it &quot
30.
by JeffreySnover 10y ago
I take a super utilitarian view. At the end of the day, PowerShell on Linux is another tool in the toolchest. PowerShell has a POV about abstracting gorp into high level task oriented abstractions, object pipelines, structured data, and the

More ›