Comment by kyllo
13 years ago
Look at recent Microsoft releases: we don't fix old features, but accrete new ones. New features help much more at review time than improvements to old ones.
(That's literally the explanation for PowerShell. Many of us wanted to improve cmd.exe, but couldn't.)
Ahh, I was wondering about that. So, I guess I'll just keep using cygwin.
On another note, I recently asked a friend who works at Microsoft how work is going. His reply: "Well, it's calibration time, so lots of sucking up to the boss." Must be hard to get much actual work done when you're worried about that all the time.
For those unfamiliar with what "calibration" is in Microsoft: http://minimsft.blogspot.com/2011/04/microsofts-new-review-a...
Powershell is so damn good and is probably so because it was not improvement of cmd. Give credit where it is due.
I'm always found it difficult to read and impossible to debug.
It's useful, sure, but nice? I'm not convinced.
How about an empty recycle bin command? Why, certainly, you can do that:
Teh F33243ck. Readable much? I sure hope your powershell scripts come with comments; the one's we've inherited sure didn't and they're black magic.
That's because they don't have nice, human readable COM (and WMI) wrappers. I don't think they had time to implement them - they kept adding more and more from v1 to v2 and v3.
Every time you have Win32 spilling over in Powershell, it looks like crap (0xA).
I agree, Powershell is definitely uglier to look at. To shorten it a bit you could also do this..
Over here, on Linux-land, I used to have PS-envy whenever I thought about the PowerShell. You cured me!
Though I don't use Trash/Recycle myself, to contrast, I like the simplicity of
3 replies →
I really can't agree with that. To me, Powershell feels like it was designed by geniuses and implemented by interns.
Absolutely basic stuff, like "find the path of this file" (%~dp0 in batch) is a 5 line copy-paste. Why? It's lovely that I can pipe .NET objects places, but every time i want it to actually do something, I end up in copy-paste hell.
> Powershell feels like it was designed by geniuses and implemented by interns.
As an intern I find this slightly offensive. ;)
Now I am curious :)
I thought you just needed to do something like: $(ls $PSCommandPath).Directory
(Not that that isnt longer than %~dp0; but I am curious what the 5 lines actually does)
1 reply →
I don't understand why they felt the need to defy standards with powershell. It's not similar to anything else i'm familiar with. All they had to do was copy bash and port some of the GNU tools.
Would be better if people actually used it!
i love my windows sys admin co workers... really lovely guys!
but there is no way in hell they can/ever will or want to write powershell.
As an ex-MS employee I always feel obligated to point out that MS has well over 50,000 employees spread out across countless teams and divisions. One employee's experience is never indicative of the company as a whole. I never went through "calibration time" while at MS or anything even close to it.
Yep, sounds about right. Building new stuff is rewarded far more than fixing broken shit. Do you want to make it right or do you want to get promoted?
michaelochurch has talked about problems with this, performance reviews and closed allocation before.
well, he doesn't talk about anything else :)
I do wonder, however, whether 'boo! MS's rating system is suboptimal, to say the least!' is a very useful comment here (which might by why we haven't seen Michael write here yet)
Yeah, and that was about Google, which has a much better reputation than Microsoft in this area. I wonder how he would like working at MS. I doubt he'd last a week there!