Comments for PowerShell.org https://powershell.org Wed, 24 Aug 2016 11:27:48 +0000 hourly 1 https://wordpress.org/?v=4.6 Comment on Coming Soon! by Thorsten Butz https://powershell.org/2007/02/07/coming-soon/#comment-11832 Wed, 24 Aug 2016 11:27:48 +0000 http://powerscripting.wordpress.com/2007/02/07/coming-soon/#comment-11832 a) Remoting
The primary purpose of PS on *nix will be remoting to Win-Hosts, such as Bash on Windows vice versa.

Due to the nature of *nix as document driven OS, an object based shell does not make that much sense. We're missing the API level. Jeffrey told us so, long ago.

b) Religious affairs
It's not about publishing the code (which is nevertheless great!).
The GPL especially is the denial of the biz model that drives the revenue of Microsoft. So, indeed, haters will hate. Agree.

But, in for a penny, in for a pound, PoSh is part of Windows which is an expensive, closed down product, increasingly incapacitating the user.

c) The role of Community
Sorry to say that, but the PS community is so much more than the few "Get-Expert -wellknown | Get-Random" MVPs. I know it's hard to see that inside the bubble.

PoSh itself is gorgeous but - at the end - just a shell, such as Korn, C, Z and all the others.

Far more important: the promise of a datacenter abstraction layer beyond the borders of specific vendors, automation and the refusal of a click UI.

In this sense, publishing the underlying code is a statement which can't be exaggerated!

Great Post, Don!

]]>
Comment on Coming Soon! by Arie H. https://powershell.org/2007/02/07/coming-soon/#comment-11826 Wed, 24 Aug 2016 06:33:37 +0000 http://powerscripting.wordpress.com/2007/02/07/coming-soon/#comment-11826 Do you really think in 20 years well be dealing with "OS war" ?

Do you think well see linux or windows in 20-30 years ? I dont.

Do you think there is a loosing side or a winning side ? There are never winners in any war.

From my POV, the shift towards lean kernels to accommodate the cloud, will get us eventually to a unified kernel of some sort getting the best of breed of all OSes, giving developers and IT the option to focus on the tools and the frameworks and less about the underlying layers.

Running a business that creates OS is becoming very expensive. No one wants to be limited in the tools they want to use, thus the SQL on Linux is a huge huge thing in that sense and it will only get bigger with more such products going the same way. I have yet to see any major party offer anything similar things, coming from the Linux side because it takes money and effort very little companies have, so MS in that sense is helping transform the ecosystem again and its in a very good direction.

Powershell on Linux exists so I, as a windows admin will have a lower barrier of entrance, if my boss decides one day to invest some our company assets on linux. If I can help my company get the right decisions that will save it money and achieve more and if that means going with a non MS way, guess what, I can still use my skills from the windows side without the hassle of the learning curve.

For a long time I've been an advocate of learning both windows and Linux, no matter what I do mostly in my work time, as they are just tools to make the job, means to achieve a goal..they are not the goals themselves, and the movement to the cloud just emphasize it even more.

I think your notion of what open source and free means is what's leading you in the line of thought and that's where I think you were wrong, imho.
Not saying that my notion of what open source and free means is better, but its somewhat less biased. Nothing is free. Open source doesn't mean security (look at the horrible OpenSSL hole that's been there for two years and only recently been closed, or support-when-you-NEED it, that will always cost money, either by support contracts or having devs that know that specific language to deal with the bugs internaly (which by itself is even more limiting with the amount of languages and frameworks popping every second day).

As for hidden agendas, you need to remember this is still a business. There's always money involved and business opportunities to be made. MS along they years was always good in creating those opportunities for itself and its partners and it continues to do so, the bottom line will be the tools. If you have ones that do the job for you, keep using them. If MS puts money and effort to create better tools with the community, who's the winner ? Everyone.

I've seen this in the heated arguments on the PS repo the second it went public. The lack of broader vision some of the Linux base audience showed, the arrogance, the "Its mine, dont touch it" is somewhat alarming. I'm just happy to know that the sysadmins in 20 years, the ones born today well have a different starting point where they will choose the tools and be told what to use by old retiring sysadmins that are trying to hold to their precious seats instead of embracing change and supporting it in the evolving it world.

]]>
Comment on Microsoft did WHAT? by Arie H. https://powershell.org/2016/08/23/microsoft-did-what/#comment-11824 Wed, 24 Aug 2016 05:37:47 +0000 https://powershell.org/?p=51548#comment-11824 The future is going to be quite interesting in that regard Missy. Breaking more barriers between the Operating system with the push MS is doing with Nano server (can only managed by powershell) and containers is going to eventually lead, imho, to a best of breed OS, a UniKernel, taking the good of both worlds towards a full cloud world, so the OS will no longer be a restriction to the tools we use to achieve the task. In that sense I would recommend you take time to learn ansible, the younger cousin of puppet and chef but, again to my view, the better solution to config managers (even though chef is somewhat more loved by MS). I would even go bit further and foresee ansible or ansible-like framework done completely in .net core and thus powershell.core that will be run on a windows server to manage Linux servers using ssh. To overcome one of puppet/chef biggest limitation of needing a Linux server to run the server part even if I have a fully windows network for example.

As fir Linux learning, being a windows admin and devops enthusiasts and practitioner for a long while, I've always endorsement investing time in learning Linux on the side just as means to understand the ecosystem, to see what's out there and what I can use to help my employers get the best results. Its good to see some of that investments paying off. With windows 10 now offering the bits of Ubuntu I'd also recommend investing time in that distro, as well and on centOS. But to not get overwhelmed, use the same methods we have in devops, start small, take one small part, learn it, the build around it.

]]>
Comment on Microsoft did WHAT? by Mike Rosado https://powershell.org/2016/08/23/microsoft-did-what/#comment-11817 Tue, 23 Aug 2016 17:36:37 +0000 https://powershell.org/?p=51548#comment-11817 Come join us at @DevOpsDaysDFW and hear Jeffrey Snover in person as he gets excited talking about this announcement and all the awesome things Microsoft is working on to embrace the DevOps community. https://twitter.com/DevOpsDaysDFW/status/768134335895592960

]]>
Comment on Coming Soon! by Jonathan Walz https://powershell.org/2007/02/07/coming-soon/#comment-11814 Tue, 23 Aug 2016 13:14:12 +0000 http://powerscripting.wordpress.com/2007/02/07/coming-soon/#comment-11814 I can't say for sure if it will cause memory problems on your system but you may want to look at this https://github.com/RamblingCookieMonster/Invoke-Parallel

I have found that it's an easier and faster way to parallelize workloads and works faster than using jobs. You will want to play with the Throttle parameter because I know for a fact you can run into memory problems if you set it too high. 😉

]]>
Comment on Coming Soon! by shawn bequette https://powershell.org/2007/02/07/coming-soon/#comment-11811 Tue, 23 Aug 2016 03:55:20 +0000 http://powerscripting.wordpress.com/2007/02/07/coming-soon/#comment-11811 To start this is a thing of beauty in it's simplicity.
Does anyone have experience with how much memory the results occupy and doing Get-job | Receive-Job at the end? If I run say a 1000 or 10,000 will this cause memory problems? I am thinking doing Get-Job -State Complete | Receive-Job & then |remove-job inside the loop (and logging it) would reduce the chance of running the host out of memory, or am I just over complicating it?

]]>
Comment on Why "Objects," Remoting, and Consistency are Such a Big Deal in PowerShell by Stephen Mathews https://powershell.org/2016/08/22/why-objects-remoting-and-consistency-are-such-a-big-deal-in-powershell/#comment-11810 Tue, 23 Aug 2016 00:40:32 +0000 https://powershell.org/?p=51512#comment-11810 Great write-up! I especially like the explanation of the API properties not having to be in order because they're referenced by name.

]]>
Comment on Create Custom Monitors with PowerShell by Alex Innes https://powershell.org/2016/08/21/create-custom-monitors-with-powershell/#comment-11808 Mon, 22 Aug 2016 07:29:31 +0000 https://powershell.org/?p=51381#comment-11808 Very cool article. Can see using some of this in our environment. Thank you.

]]>
Comment on Coming Soon! by Richard Diphoorn https://powershell.org/2007/02/07/coming-soon/#comment-11805 Sun, 21 Aug 2016 19:57:18 +0000 http://powerscripting.wordpress.com/2007/02/07/coming-soon/#comment-11805 Interesting perspective. But I think you missed the point why Microsoft is actually open sourcing PowerShell. If you followed the talks that Jeffrey Snover did the last few years, it became clear that they want to be able to support heterogeneous environments. And for what I've seen now from Microsoft, and especially the PowerShell team, is that they don't have a hidden agenda. Microsoft is not the Microsoft anymore from let's say, 5-10 years ago.

I agree with you, that there's a lot of Linux on Azure. But many, many companies I come are mainly Windows based infrastructures. Also guys that I know that work for other companies almost only see Windows based infra's.

Yes, Linux has it's place in this world, but according for Microsoft there's no battle between Windows or Linux. They're citizens in IT which Microsoft wants to support best. And PowerShell is not a tool per se, it's meant to be a management framework. A framework that operates with built-in tools or in the case of Windows, the .NET framework.

Windows Server has a big future, just look at the developments Microsoft is doing on Nano server.

]]>
Comment on Episode 316 - PowerScripting Podcast - Jeffrey Snover from Microsoft on Open Sourced PowerShell v6 by Aaron Christianson https://powershell.org/2016/08/19/episode-316-powerscripting-podcast-jeffrey-snover-from-microsoft-on-open-sourced-powershell-v6/#comment-11800 Sun, 21 Aug 2016 09:08:54 +0000 https://powershell.org/?p=51253#comment-11800 oh goodness! that came out as one long, horrible paragraph. The reply on the youtube video is properly formatted.

]]>