Automating the world one-liner at a time…
A year ago I broke my habit and made a set of News Years resolutions and then published them on the team blog HERE. Lee Holmes suggested I go back and review how I did on those. Glug! Let’s give it a go:
All and all, I’m very happy with the year but there are still lots of opportunity to improve.
Experiment! Enjoy! Engage!
Jeffrey Snover [MSFT] Distinguished Engineer Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
Hi; I'm curious to what you refer by "We are digging ourselves out of a 30 year hole". What's the 30-year hole? My first guess is "dependence on shell/scripting languages other than Microsoft ones" (Perl comes to mind)?
Good post Jeffrey. Regarding WMI, there's still a fair amount of misplaced optimism out there that powershell is _replacing_ it rather than augmenting it. This will be a tough nut to crack.
There were times when I wanted to complain in the Connect site, but since I'm not really a part of the target audience for Powershell, I didn't want to get in the way.
I'm not really sure how many others like me are out there.
Happy New Year!
@Matthew - 30 year hole is the lack of good command line management and interactive shells.
@Oisin - I agree that there is confusion about PS replacing WMI. I've NEVER understood it.
@Francis - Provide feedback and trust us to make the judgement call.
Hi Jeffrey, good review - I continue to think you guys do a fantastic job given the wide range of inputs coming your way!
I love WPK and have used it to write a tabbed application for running a badminton league - excellent. If James can fix the (BAD) bug and if the doc can be improved then it's a winner.
What are your resolutions for this year?! It's been a bit quiet from the team on direction after V2. Can you tease us some more?
Great going PowerShell Team!
Excellent assessment Jeffery
I am sure you have already thought of the following but just in case:
Now that no one person can know all of PowerShell there is more danger of it becoming fragments. All of the hard work to build and implement a strong design specification will help but constant vigilance is still needed.
WMI may be an issue in PowerShell for some due to overall nomenclature of Windows Management parts. This will sort out when users start using WMI in PowerShell. To lake this better the team needs to eliminate some inconsistencies and deficiencies in WMI implementation in PowerShell. A better implementation of WMI SDK would go a long way towards getting more vendors and developers to “instrument” their products. I am sure that this will happen soon as the Windows Management Team has been very busy lately. What they have been doing is starting to become exciting. Hurrah!
Great post and great job for you all.
As I am working with WMI almost every day I love new WMI cmdlets in v2 and I am looking forward for working with them in 2010.
P.S.: I like this: "no one knew everything about PowerShell anymore – not me, not Bruce, not Lee – no one!"
Great post and great job PowerShell Team.
In regards to #5, are there script sharing sites you can recommend? I have found a few but if you recommend it I will trust it to be a useful site.
re: Ensure that everyone knows how easy it is to develop Delegated Web-Based Self-Service Portals using PowerShell.
Sounds great where do I find "the highlight of my talk at TechEd"? Is there a video or the material for another great post?
BTW: Great work powershell team. It is best new tool I have learnt in YEARS! Scripting is actually enjoyable on Windows. I never thought I would see the day and didn't imagine it could be SO good.
I used to like PowerShell.
Now I do not. I find your documentation fragmentary and a mess. I don't want to have to search through tens of blogs (most of which I probably don't even know that exist) to find out how to do simplestuff.
Well, the good thing is that what you liked with v1 is still there for you to like in v2. Yes, v2 gives you more power, but I wouldn't necessarily qualify some of the new features as simple... Do may require a little bit of research, but once learned, you'll get all the benefits.
Now, if you could add "Make PowerShell remoting on Windows at least as seamless and flexible as SSH on Unix" to your list for 2010, it would be quite nice! ;)
@L. I second that. SSH can be both open (think cygwin, copssh, etc.) and closed (think ssh.com, pragma, bitvise, etc.) while:
- providing remote command exectution
- providing remote file transfer
- scriptable commands both interactive and non-interactive, password and key-exchange
- cross platform compatibility (every OS and some mobile OS's have SSH)
- firewall friendly (single port, single protocol, no conflicts with other software, etc.)
- providing secure tunneling and proxy ability for other protocols, especially through firewalls (see above)
BITS over SSL will never have some of those. I don't understand the reasoning. I've been waiting for native SSH from Microsoft for about 10 years now. We buy and use an SSH server software for every Windows system. It's a cost of doing business for now. Of course, we looking for ways to reduce costs... so maybe they'll include SSH in the next version of PowerShell or Windows. Or take that thread wherever you want.
Noone wants to shell out more money for SSH than the cost of the OS to install it on. Especially when the other OS's (Linux, Solaris, Mac, etc.) include it for free.
If I had a wish-list Jeffrey, that would be number 1 for me. An included SSH server that plays very well with the rest of my systems, and powershell as the terminal behind it.
#13 - there's no download there. Sounds great, didn't know, immediately went over there. Currently vaporware.