Good grief, but MS move fast!
-
Or maybe they had a hard time accessing the bug list, because someone finally fulfilled so many people's dream of ramming the bluddy thing up their @rse.
I wanna be a eunuchs developer! Pass me a bread knife!
That's going to give him a surprise - he hasn't logged in since 2009... :laugh: Gets my 5 anyway - I was a DOS beta tester and they never fixed any of those either... :sigh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
That's going to give him a surprise - he hasn't logged in since 2009... :laugh: Gets my 5 anyway - I was a DOS beta tester and they never fixed any of those either... :sigh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Good days, the DOS days -- they were nerds, we were nerds (and God knows there are bugs of my own that I never got around to fixing, so I could forgive fellow nerds). Nowadays, they're nothing like us, and they don't give a toss what we (and people in other professions) need. I dread to think what it's like to work in their head office.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I got an email today from the MS support team, saying they are going to review a change suggestion I support. I thought "I don't remember anything about it" - so I followed the link: Open links in an actual browser – Visual Studio[^] Oh yes - VS should open help and such like in the default browser instead of inside VS. I remember that now, but wasn't that a while ago? Oh yes. Four years. It's taken MS four years to notice suggestions - not to implement them, no. Not even to decide to schedule them for implementation. Four years to to go "Oh. Yes. maybe an idea, that. Let's think about it". Fer Elephants Sake MS! No wonder you don't make any impact in the mobile devices market if everything you do is over four years late...the competition will have released three or four updated devices by then! Does explain a lot about Windows Mobile though... :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
And I thought 15 months for a response from Crystal Reports support was pretty pathetic. Oh wait mine was a SUPPORT request not a change suggestion.
Never underestimate the power of human stupidity RAH
-
David Lumm wrote:
Wow. That is slow, even for microsoft
Not even a little bit. There are thousands of bugs (*bugs*, mind) in Windows and Office that have been there for a couple of decades. They're too busy "fixing" the stuff that works, to get on with what their customers actually need.
I wanna be a eunuchs developer! Pass me a bread knife!
The guys that knows how to fix most of the bugs probably left them already. That is the sad reality of leaving something for to long. Person that actually implemented or knew how to work with the technology leaves the company. To put a newb on it will cost far to expensive. Probably take a day+ to just get to the point where he/she can fix it. Hell, if I work on something and have to return to it later on it takes a while to get what I did.
"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
-
I got an email today from the MS support team, saying they are going to review a change suggestion I support. I thought "I don't remember anything about it" - so I followed the link: Open links in an actual browser – Visual Studio[^] Oh yes - VS should open help and such like in the default browser instead of inside VS. I remember that now, but wasn't that a while ago? Oh yes. Four years. It's taken MS four years to notice suggestions - not to implement them, no. Not even to decide to schedule them for implementation. Four years to to go "Oh. Yes. maybe an idea, that. Let's think about it". Fer Elephants Sake MS! No wonder you don't make any impact in the mobile devices market if everything you do is over four years late...the competition will have released three or four updated devices by then! Does explain a lot about Windows Mobile though... :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Once, it took two years for Microsoft to notice a bug I spotted on GDI+ that I reported via connect. They acknowledged bug, but said weren't going to fix it for the same old reasons. Go figure, it makes no sense to have the tools to report stuff if they are worth nothing.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
The guys that knows how to fix most of the bugs probably left them already. That is the sad reality of leaving something for to long. Person that actually implemented or knew how to work with the technology leaves the company. To put a newb on it will cost far to expensive. Probably take a day+ to just get to the point where he/she can fix it. Hell, if I work on something and have to return to it later on it takes a while to get what I did.
"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
"Later on", in my case, is less than a week.
I wanna be a eunuchs developer! Pass me a bread knife!
