Decline and Fall
-
Decline and Fall In hindsight there are always signs that a powerful empire has long since reached its peak and is in decline. Repeated failure at a core part of their business is one important sign. Microsoft's success has long been the ability to balance performance and user-friendliness at a reasonable price. It has not often been a pretty compromise - these things seldom are. The Microsoft developer flagship has always been their compilers, particularly the C++ compiler. The developer community has been waiting for a decent IDE from Microsoft for years now. VS2010 was released lately and we eagerly powered it up salivating at the prospect of lightning fast drop down menus displaying all the members and methods of the class. No sir. To our utter astonishment, it was an order of magnitude worse than its disappointing predecessor, VS2008. You see a function call, and click on Goto Definition. The horrifying news is that VS2010 is even more confused and doddering than VS2008. VS2008 has always been confused about function definition versus declaration. But at least it went to the wrong place quickly. VS2010 sinks into a senile stupor, consuming the entire resources of your computer. You cannot edit documents, view or reply to emails, do anything at all ... in fact you can't even soft-reboot, which I have repeatedly tried. 30 seconds later, it triumphantly displays the declaration of the function for which you requested the definition. Knowing it is pointless, you nevertheless click on the declaration, and request to see the definition, hoping against hope that it will this time deliver. Your computer fan noise rises to a howling scream. Your colleagues are abusing you, shouting, "What is that bloody noise? Turn it off!" After a promethean struggle, which has consumed the entire resources of your 8 CPU's for half a minute, it again settles ponderously on the declaration. You have to be kidding! A trained pigeon could find the definition in less time. The declaration is in MySource.h. The definition is in MySource.cpp. Here's a clue: the declaration has no body - the signature is terminated by a semicolon. The definition *does* have a body, enclosed by braces like this { ... }. We don't have whacko headers - there are no conditional #includes - it's all pretty standard. Yes, we do have #ifdef WIN32 declare the Windoze stuff #else declare the Linux stuff #endif, but surely that is not sending VS2010 nuts. Sure, conditional #includes could drive anyone crazy, but we don't do tha
-
Decline and Fall In hindsight there are always signs that a powerful empire has long since reached its peak and is in decline. Repeated failure at a core part of their business is one important sign. Microsoft's success has long been the ability to balance performance and user-friendliness at a reasonable price. It has not often been a pretty compromise - these things seldom are. The Microsoft developer flagship has always been their compilers, particularly the C++ compiler. The developer community has been waiting for a decent IDE from Microsoft for years now. VS2010 was released lately and we eagerly powered it up salivating at the prospect of lightning fast drop down menus displaying all the members and methods of the class. No sir. To our utter astonishment, it was an order of magnitude worse than its disappointing predecessor, VS2008. You see a function call, and click on Goto Definition. The horrifying news is that VS2010 is even more confused and doddering than VS2008. VS2008 has always been confused about function definition versus declaration. But at least it went to the wrong place quickly. VS2010 sinks into a senile stupor, consuming the entire resources of your computer. You cannot edit documents, view or reply to emails, do anything at all ... in fact you can't even soft-reboot, which I have repeatedly tried. 30 seconds later, it triumphantly displays the declaration of the function for which you requested the definition. Knowing it is pointless, you nevertheless click on the declaration, and request to see the definition, hoping against hope that it will this time deliver. Your computer fan noise rises to a howling scream. Your colleagues are abusing you, shouting, "What is that bloody noise? Turn it off!" After a promethean struggle, which has consumed the entire resources of your 8 CPU's for half a minute, it again settles ponderously on the declaration. You have to be kidding! A trained pigeon could find the definition in less time. The declaration is in MySource.h. The definition is in MySource.cpp. Here's a clue: the declaration has no body - the signature is terminated by a semicolon. The definition *does* have a body, enclosed by braces like this { ... }. We don't have whacko headers - there are no conditional #includes - it's all pretty standard. Yes, we do have #ifdef WIN32 declare the Windoze stuff #else declare the Linux stuff #endif, but surely that is not sending VS2010 nuts. Sure, conditional #includes could drive anyone crazy, but we don't do tha
Too long to read on a Monday. ;P
That's called seagull management (or sometimes pigeon management)... Fly in, flap your arms and squawk a lot, crap all over everything and fly out again... by _Damian S_
-
Decline and Fall In hindsight there are always signs that a powerful empire has long since reached its peak and is in decline. Repeated failure at a core part of their business is one important sign. Microsoft's success has long been the ability to balance performance and user-friendliness at a reasonable price. It has not often been a pretty compromise - these things seldom are. The Microsoft developer flagship has always been their compilers, particularly the C++ compiler. The developer community has been waiting for a decent IDE from Microsoft for years now. VS2010 was released lately and we eagerly powered it up salivating at the prospect of lightning fast drop down menus displaying all the members and methods of the class. No sir. To our utter astonishment, it was an order of magnitude worse than its disappointing predecessor, VS2008. You see a function call, and click on Goto Definition. The horrifying news is that VS2010 is even more confused and doddering than VS2008. VS2008 has always been confused about function definition versus declaration. But at least it went to the wrong place quickly. VS2010 sinks into a senile stupor, consuming the entire resources of your computer. You cannot edit documents, view or reply to emails, do anything at all ... in fact you can't even soft-reboot, which I have repeatedly tried. 30 seconds later, it triumphantly displays the declaration of the function for which you requested the definition. Knowing it is pointless, you nevertheless click on the declaration, and request to see the definition, hoping against hope that it will this time deliver. Your computer fan noise rises to a howling scream. Your colleagues are abusing you, shouting, "What is that bloody noise? Turn it off!" After a promethean struggle, which has consumed the entire resources of your 8 CPU's for half a minute, it again settles ponderously on the declaration. You have to be kidding! A trained pigeon could find the definition in less time. The declaration is in MySource.h. The definition is in MySource.cpp. Here's a clue: the declaration has no body - the signature is terminated by a semicolon. The definition *does* have a body, enclosed by braces like this { ... }. We don't have whacko headers - there are no conditional #includes - it's all pretty standard. Yes, we do have #ifdef WIN32 declare the Windoze stuff #else declare the Linux stuff #endif, but surely that is not sending VS2010 nuts. Sure, conditional #includes could drive anyone crazy, but we don't do tha
johnsyd wrote:
It's convenient when debugging to be able to break on that statement and inspect `n
Look at the eax register. And I agree. VS 2005 is the last one I will use.
"It is a remarkable fact that despite the worldwide expenditure of perhaps US$50 billion since 1990, and the efforts of tens of thousands of scientists worldwide, no human climate signal has yet been detected that is distinct from natural variation." Bob Carter, Research Professor of Geology, James Cook University, Townsville
-
johnsyd wrote:
It's convenient when debugging to be able to break on that statement and inspect `n
Look at the eax register. And I agree. VS 2005 is the last one I will use.
"It is a remarkable fact that despite the worldwide expenditure of perhaps US$50 billion since 1990, and the efforts of tens of thousands of scientists worldwide, no human climate signal has yet been detected that is distinct from natural variation." Bob Carter, Research Professor of Geology, James Cook University, Townsville
fat_boy wrote:
And I agree. VS 2005 is the last one I will use.
me, too. The others were designed by people who insisted on not having any user input.
“The fact that some geniuses were laughed at does not imply that all who are laughed at are geniuses. They laughed at Columbus, they laughed at Fulton, they laughed at the Wright Brothers. But they also laughed at Bozo the Clown.” ~ Carl Sagan