Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PowerShell is open sourced and is available on Linux

azure.microsoft.com

Post reply on HN
Print view View original

531–540 of 790 posts

Re: PowerShell is open sourced and is available on Linux

#531

Post by flukus »

PeCaN wrote: post #107
amenod wrote: post #32

Earlier quoted context omitted.

Is this really so useful in practice? I have never used PowerShell before (nor do I have plans to do so in the near future), but I would imagine the downside is complexity, both for user and especially for developers. With text you just read and parse, while with objects you need to know the object type, its fields,... Whatever happend, I hope text stays here (and I have a bad feeling about it ever since I met system…

I find it massively useful in practice, even for mundane tasks. For example, the other day I was trying to search the columns of a very large SQL Server table¹ but also needed information about the column type. …\dbo.site> ls Columns | select Name, DataType, {$_.Properties['Length'].Value} | where {$_.Name -like '*int*'} Name DataType $_.Properties['Length'].Value ---- -------- ----------------------------- internal_…

Pretty much all databases will support "describe tablename" to do exactly that.

Re: PowerShell is open sourced and is available on Linux

#534

Post by e40 »

thenewwazoo wrote: post #74
Secretmapper wrote: post #25

Wow. I've been very impressed with Microsoft lately. They could have easily set themselves up as the next IBM, in the sense of being a monolithic corporation relying on corporate practices, but they've been spewing some crazy fun things that shows they're not out of the league yet. Might just be MY miscontrued perception that microsoft was becoming old/monolithic, but really excited with the direction they are headin…

I speak only for myself. Microsoft have been hugely focused on hiring people who have experience outside the Windows bubble, and have been encouraging cross-pollination of ideas with the OSS world. There are holdouts for the old guard of course (there's still a BU that requires Windows Phones), but I think everyone knows that the Microsoft of old cannot compete today by bringing an attitude that pleasing the CFO is a…

Well said. If it only happened a decade or more earlier than it did, I think MS wouldn't have lost as many customers.

Re: PowerShell is open sourced and is available on Linux

#535

Post by cyphar »

deno wrote: post #436
whateverdudes wrote: post #429

Earlier quoted context omitted.

So it's maintained in the open on GitHub, it's technically open source in terms of licensing. Yet you claim it's not really open source. Care to clarify?

It’s technically open-source, that’s the point. There’s more to open-source than license. Sorry but there’s no way for me to clarify without just repeating my original comment.

> It’s technically open-source, that’s the point. There’s more to open-source than license. Sorry but there’s no way for me to clarify without just repeating my original comment.

It's free software, and in that sense the license is the only thing that really matters. However, if you're discussing open collaboration styles then that's a whole different discussion. Either your project is free software or it isn't. Whether it has a diverse and open development community is a separate problem, and doesn't fall under "is this project [free software]".

Re: PowerShell is open sourced and is available on Linux

#536

Post by Nullabillity »

jimmaswell wrote: post #325
bad_user wrote: post #312

Earlier quoted context omitted.

Meh, to make Visual Studio do IDE-like things, people install things like ReSharper, built by the same people that are building IntelliJ IDEA. And I worked with both and IntelliJ is much smarter, and has support for way more technologies. And yes, it's built in Java and can be sluggish, but then again I'm using it on both Linux and OS X and runs just fine on Windows too, so it doesn't tie me to an OS I don't want. Al…

What am I missing building projects with VS or xbuild?

For one, sane dependency management that doesn't require vendoring.

Re: PowerShell is open sourced and is available on Linux

#537

Post by jjnoakes »

qwertyuiop924 wrote: post #525
viraptor wrote: post #484

Earlier quoted context omitted.

> But on UNIXes, those APIs are already well exposed elsewhere, and that data doesn't exist. I'd go with exposed, but not necessarily well. Examples I run into all the time: get an IP from an interface, change iptables entries, even change fstab options. Sure, if you write enough regex, it will probably work most of the time. But it's never going to be as reliable as get_ips('eth0'), or get_filesystem('/tmp').options…

getting an IP is still pretty ugly, somehow: ip address show dev eno1|grep 'inet '|cut '-d ' -f6 But I wouldn't call it unreliable. The cut is the only really nasty bit. Changing your fstab is easy with a little awk: $2=="/tmp"{$4=$4 ",nosuid"} {print $0} Given, it won't remove contradicting options...

And either the "ip" command can never change how it formats its output, or your script with that command will break some day.

Re: PowerShell is open sourced and is available on Linux

#538

Post by cyphar »

deno wrote: post #505
RubyPinch wrote: post #493

Earlier quoted context omitted.

do you more mean like, the decisions, and planned changes, etc, aren't open? (along with being tied to the whims of the CEO and the company's money?)

They might be open, but there’s democracy and then there’s democracy. See for example recent MSBuild incident (but don’t try to argue about it it’s just an example). As I said, it’s a feeling. The feeling is it’s Microsoft’s project, everyone else is along for a ride. And that’s fine, but it’s something different. Let’s just not pretend technical merits drive adoption, that’s rarely true.

> They might be open, but there’s democracy and then there’s democracy. See for example recent MSBuild incident (but don’t try to argue about it it’s just an example).

> As I said, it’s a feeling. The feeling is it’s Microsoft’s project, everyone else is along for a ride. And that’s fine, but it’s something different. Let’s just not pretend technical merits drive adoption, that’s rarely true.

Uhm. So many free software projects work like that. A company creates something, releases it as free software. Yes, people contribute (and that's awesome by the way) but in general all of the engineering talent works at the company because they wrote it in the first place (and they hire contributors). At SUSE this is how YaST, zypper, spacewalk, et al development works (with significant contributions from the openSUSE community, but we have teams of people working on those projects so our contributions are more of a concentrated effort). There's nothing new or different about this model of free software development (Sun did the same thing with OpenSolaris and Joyent does the same thing with SmartOS). Yes, GNU and Linux follow the hobbyist model but that's not how all projects work.

Re: PowerShell is open sourced and is available on Linux

#539

Post by Arcsech »

ocdtrekkie wrote: post #402
optforfon wrote: post #228

Earlier quoted context omitted.

By giving everything away for free? The only related revenue stream M$ seems to have left is Azure with some vague notion that giving away their ecosystem will drive people to use their cloud more

Windows isn't free. Office isn't free. All of their enterprise server software isn't free.

Support and training contracts aren't free, either. I don't know if Microsoft does much of that, but it's another option for revenue with .NET.

Re: PowerShell is open sourced and is available on Linux

#540

Post by jimmaswell »

Nullabillity wrote: post #536
jimmaswell wrote: post #325

Earlier quoted context omitted.

What am I missing building projects with VS or xbuild?

For one, sane dependency management that doesn't require vendoring.

You can reference projects or other files that are in submodules. What about the .NET build process makes vendoring the only option?

Even so, it's always been more convenient in my experience when something just ships with fixed versions of dependencies already inside it. Those versions are known to work with the codebase and there's no chance of new bugs or other incompatible behavior being introduced from updates to the dependencies.

Post reply on HN