Linked by Thom Holwerda on Fri 15th May 2009 07:11 UTC, submitted by Georgi Petrov
Thread beginning with comment 363802
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by FealDorf - wouldn't blame the devs
by license_2_blather on Fri 15th May 2009 14:56
in reply to "RE: Comment by FealDorf - wouldn't blame the devs"
Maybe, but this looks like they went out of their way to mess this up. I know Microsoft has some security-minded people working for them, and they are probably screaming about this. But, incredibly, they are ignored. Let's just hope that security by public outcry prevails and once again convinces Microsoft's management to pull their heads from their a**es.
RE[2]: Comment by FealDorf - wouldn't blame the devs
by kaiwai on Fri 15th May 2009 15:17
in reply to "RE: Comment by FealDorf - wouldn't blame the devs"
I suspect the developers are more encumbered by the company culture. Even if they want to put out good design work and code, they have budgets, delivery dates and marketing/management mandates like continuing to support everything back to Dos virus code.
You're right; when I hear managers within Microsoft say that 'legacy code is an asset' - I know they've lost touch with reality. An asset as anyone knows can eventually turn into a liability. This idiotic idea of code being an asset forever simply ignores the reality of situation - it helps no one promising backwards compatibility indefinitely because it results in castrating any possible future improvements to the operating system itself. Windows in its current half-baked state is a by-product of this policy - it has nothing to do with a lack of smart people within Microsoft and everything to do with management placing unrealistic limitations in programmers on what they can do by virtue of this backwards compatibility fixation of theirs.
Edited 2009-05-15 15:21 UTC
RE[2]: Comment by FealDorf - wouldn't blame the devs
by bousozoku on Fri 15th May 2009 15:18
in reply to "RE: Comment by FealDorf - wouldn't blame the devs"
I suspect the developers are more encumbered by the company culture. Even if they want to put out good design work and code, they have budgets, delivery dates and marketing/management mandates like continuing to support everything back to Dos virus code.
It's more likely that they're too busy shooting rubber bands at each other than designing and coding good software. It takes too much effort to do things correctly.
Not directed to you, but why should the operating system bother the user to death to avoid disaster? Why shouldn't the UAC require a password even when the Administrator is using the machine to do certain things? The company seems to have a skewed view of how things should work to be correct and effective.
RE[3]: Comment by FealDorf - wouldn't blame the devs
by brandonlive on Fri 15th May 2009 21:47
in reply to "RE[2]: Comment by FealDorf - wouldn't blame the devs"





Member since:
2007-09-06
I suspect the developers are more encumbered by the company culture. Even if they want to put out good design work and code, they have budgets, delivery dates and marketing/management mandates like continuing to support everything back to Dos virus code.