Now my workstation in the office has been playing up for a couple of months now - slowly deteriating along the Verity Stobbs cruft scale.
Windows 2000, despite what people claim, just isn't stable - maybe if you just run IIS and nothing else it might be able to run for a month or two before requiring a reboot.
But when you are doing development - it is totally unreliable. The combination of (what microsoft reccomends) SQL Server, InterDev, Outlook and Internet Explorer ensures that your machine is unusably slow unless powercycled at least 3 times a week and whenever internet explorer crashes (now several times a day) it can take the whole desktop with it.
This being windows with IE embedded into the kernel along with big chunks of office and sql server means that often when one application crashes it is impossible to recover the desktop at all and you must reboot the machine.
This isn't stability and you can't even blame dodgy shareware - I'm running all MS software and protected from viruses, at the mailserver and locally - my virus definition files are regularly updated and all the service packs applied.
The only way to have a workable windows 2000 desktop is to either run only notepad or to reboot daily and reinstall weekly.
I did buy the Visual Studio
So I agree that if you are doing cutting-edge stuff on Win2k, then God bless you and your sanity. But let's not ignore the fact that Win2k is an awesome platform for us simple folk.
Jason
Re:No prob's for me...
TeeJay on 2002-10-03T13:03:43
as I said its not suitable as a development platform. Not unless you have a pristine and never use it for more than a few weeks after which it fills with detrius and collapses under its own weight.You don't have to be doing cutting edge stuff - all the work stuff here is IIS 5 / ASP / interdev nothing newer than 18 months - should be pretty stable by now but it isn't.
we're not doing custom c++ objects or java, just plain old vbscript and its unreliable and slow.
I spend as much time as possible on the linux box on my desk that is supposed to be for R&D but has been up for 6 months without a glitch despite trying out cutting edge libraries, installing huge ammounts of packages and reconfiguring daemons and servers!
