Hacker News Reader

Comment by mike_hearn | Hacker News Reader

There have been regressions even. PowerShell 7 isn't backwards compatible with PowerShell 5 and some features that used to exist are just gone with no plan for a return, due to (surprise) fights between .NET and Windows teams over API metadata formats or something. Most incredibly Microsoft situation ever.

Say what you want about bash, at least it doesn't pull stunts like that.

View on HN

So the old org chart comic is correct:

https://flowingdata.com/2011/06/30/organizational-charts-in-...

Wow, the Oracle chart is so spot on.

Always was ︻┳═一

(hey, I managed to sneak a rifle past HN's Unicode filter :-D)

As someone deep into Microsoft ecosystem since MS-DOS 3.3, it feels like the old ways of WinDev vs DevDiv politics have slowly creeped back into daily Microsoft.

It is as if DevDiv is now full into UNIX like, poliglot, FOSS culture and such, now under Azure business unit, whereas WinDev is back into how to sneak people into Windows licensing and the usual old culture.

Are there any currently-supported versions of Windows that don’t support Powershell Core? I recall installing it on Windows 2012, even.

> Say what you want about bash, at least it doesn’t pull stunts pile that.

I guess it depends on what you consider to be included in the terminal’s domain? There are entire papers and guides on which commands are considered safe (sometimes only when run in a very specific way), and which variants, alternatives, etc. you should use instead, for Bash scripts, because of the inconsistency in what a command evaluates, does, and returns for various distros. That’s not to hate on Bash, but just to point out that it’s not a strength of Bash vs PS.

When Powershell was first released I was primarily working with Unices and was very curious what would work better: The Unix way in cutting, changing and grepping some part of stdout (in some OS a bit simplified b with options for automated pricessing which commands the programm to output colon delimited or otherwise formatted)

Or the Powershell way where on can access data members directly.

I thought I would prefer the second method more, because the access looked much cleaner/structured.

But after all these years (still mostly Unix scripting but Powershell and some other environments too) my mind has changed.

Would like to hear what others would prefer' Unix method with some scripting language or windows method with Powershell)

Combining both powershell and unix is neat!

> The Unix way in cutting, changing and grepping some part of stdout

And this is exactly the problem.

You no longer have en_US as a locale? Have some titles lounger.

You no longer have en locale at all? Have an greška instead of error.

Oh, you the schmuk who don't agrees to use the best units in the world, totally retarded and "bUt iF yoU WriTe THe dATe as in the journal..."[0] but freedom ones? No longer accept 13 as an hour. Like come on, every idiot knows there is no such thing as an 13th hour!

Oh, you added an additional column to help your busniessor whatever? Your sEd MagIK gone to hell.

Should I continue?

[0] when was the last time you actually wrote multiple documents so you can actually benefit from MMM-dd?

> because of the inconsistency in what a command evaluates, does, and returns for various distros.

I'm not aware of any difference in bash between vendor distributions for which this is true.

It's less of a problem in today's Linux monoculture, but I actually initially learned Perl and Tcl precisely because of subtle incompatibilities between systems for tools like sed and awk, not to mention utilities like ps and tar.

This may not count because it's not bash specifically or even Linux -> Linux, but one place you might run into this is running scripts between Linux and Mac/BSD.

In the past I've seen bad things happen because a script was written by someone on OSX that gets run on a Linux (GNU) based system.

Two common examples are the `sleep` and `sed` commands.

Edit: I meant to reply to the parent comment.

My guess from external observations is that the reward and bonus structure inside Microsoft is entirely decoupled from customer feedback and response. The middle managers are in charge of the product and they're fully insulated from any concerns outside of getting this years maximum bonus for themselves.

Monopolies always destroy innovation.

I was under the impression much of that is due to the fact that PowerShell is Windows-only, while PowerShell Core is multi-platform.

They now refer to the former as Windows PowerShell, and the latter as PowerShell. The Core part was dropped.

It's easy not to lose features when you don't have many to begin with... I mean, what are the features that disappeared? What's the bash equivalent of these features?

For a programming language, losing a feature is much, much worse than not having it in the first place.

I'd like to see examples to judge. What are the features? Also, are you confusing "the language" with "the standard library"?

Years old existing code suddenly breaking because of an infrastructure update is just way worse than limitations when writing new code.

For example: https://github.com/PowerShell/PowerShell/issues/13138

Reply on news.ycombinator.com