And if you deactivate the crippleware anti-virus software that almost always comes pre-installed on Wintel boxes, you'll have a very stable Windows environment, at least under W2K. I won't speak of XP because I don't like it, but W2K was extremely stable and I've had it running for months between boots.
I think most of Windows' reputation for instability comes from that damned anti-virus software.
Amen. Good luck getting anything but knee-jerks on this, though; MS-bashing in the Linux world is far more repellant than it needs to be. I'da turned penguin years sooner were it not for all the OS-war crap.
Anyone with a little rigor can write software that performs as expected and only crashes on hardware anomalies. It's just discipline and structure.
I've been developing 15 years and I would say that in that time I've worked with less than a half-dozen developers who understood what they were doing, people who could tell you *why* to write a certain way, the advantages and disadvantages. The others just go through the motions and justify stupid habits like mid-function returns with lame excuses like "I've always done it this way."
Slashdot Mirror
You left out the important one: (0) design before coding
And if you deactivate the crippleware anti-virus software that almost always comes pre-installed on Wintel boxes, you'll have a very stable Windows environment, at least under W2K. I won't speak of XP because I don't like it, but W2K was extremely stable and I've had it running for months between boots. I think most of Windows' reputation for instability comes from that damned anti-virus software.
Amen. Good luck getting anything but knee-jerks on this, though; MS-bashing in the Linux world is far more repellant than it needs to be. I'da turned penguin years sooner were it not for all the OS-war crap.
Anyone with a little rigor can write software that performs as expected and only crashes on hardware anomalies. It's just discipline and structure. I've been developing 15 years and I would say that in that time I've worked with less than a half-dozen developers who understood what they were doing, people who could tell you *why* to write a certain way, the advantages and disadvantages. The others just go through the motions and justify stupid habits like mid-function returns with lame excuses like "I've always done it this way."