Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

PowerShell

Name: Anonymous 2013-08-12 15:05

Anyone else having to deal with this pile of shit they call a shell?

We had to wait three fucking decades for a mildly serious attempt at creating anything that could be as "usable" as the Unix' shell (in their own systems), and this is the very best shit we could ever get?

It seems that MS can't get a single thing right, not even fucking once.

Name: Anonymous 2013-08-12 15:09

If Microsoft could get a single thing right, it would be a "keep left" sign.

Name: Anonymous 2013-08-12 15:09

there are other options...
gnuwin32
Cygwin
Windows Subsystem for UNIX Applications

Name: Anonymous 2013-08-12 15:17

>>2
Lol'd. This one's new to me.

>>3
IOW, Bash inside Windows. Works like shit and useless for deploying purposes. Also, GNU.

Name: Anonymous 2013-08-12 15:37

If I remember correctly, many Windows developers want to change these steaming turds but can't because it would break The Forced Backwards Compatibility Of Code. Microsoft takes The Forced Backwards Compatibility Of Code so serious, they once left a bug in Windows because fixing it would break a somewhat popular application that relied on it.

Name: Anonymous 2013-08-12 15:41

>>5
I thought that the code is full of hardcoded work-arounds so that, when such old apps are detected, the old relied-upon behavior is performed instead, while new apps get the correct behavior.

Name: Anonymous 2013-08-12 15:42

>>5
they once left a bug in Windows
Just once?

Name: Anonymous 2013-08-12 15:49

>>7
EXPERT JOKESTER

I was talking about leaving it in intentionally.

Name: Anonymous 2013-08-12 15:55

>>5
We all know this, but this isn't an excuse at all. Supposedly .NET  itself is an attempt to give Windows programming a clean start, to attempt an entirely new Windows API without touching legacy working code, and guess what? It is already full of shit again, as you expected.

PS is built on top of .NET and it is unbelievably lame at being a script language, let alone a shell. Some ridiculously simple tasks (such as creating proper command aliases) are overwhelmingly complex to implement and some design decisions are so stupid one can't imagine what took anyone to implement some feature in that particular way. Everything seems unplanned and rushed, as if just striving hard to reach the market as soon as possible.

Name: Anonymous 2013-08-12 16:33

>>9
Isn't .NET already deprecated?

Name: Anonymous 2013-08-12 16:33

>>8
Fuck off.

Name: Anonymous 2013-08-12 16:49

>>10
In favour of what?

Name: Anonymous 2013-08-12 16:57

>>12
My anus.

Name: Anonymous 2013-08-12 22:25

>>1,3,4
*nix on windows:
http://www.mkssoftware.com/products/
https://en.wikipedia.org/wiki/UnxUtils
https://gna.org/projects/wwwcdset
https://en.wikipedia.org/wiki/GNUWin_II
https://en.wikipedia.org/wiki/Cygwin
https://en.wikipedia.org/wiki/MinGW
http://support.microsoft.com/kb/324081

Pick your favorites!

>>5
I know, its like the Sun tribulations. At the least the lead developers were able to conquer the company multiple times in the v2 times. What you get now is OpenSolaris. Hail the company that did it right, even selling to Oracle, after everyone knew the USA was going to be become North Korea 5.0.

>>6
NOPE.drc. Remember XP? How about Vista?

>>9
Now it is F#.

>>12
[insert any C derived laguage out there, even if it is Open source] Although the push by most IT departments are stupid PHP

Name: Anonymous 2013-08-13 3:07

I'm pretty sure PS isn't really a shell. It's more of a Perl wannabe language for .NET apps that can't use anything else.

Don't change these.
Name: Email:
Entire Thread Thread List