Sridhar Ayengar writes:
If you write *any* code at all on Windows, you can
expect to crash the OS
fairly regularly. I've written *Java* code that ran *in the VM* that
crashed the OS. And don't tell me not to write buggy code, everyone has a
bug or two in their initial revision.
I beg to differ. I've developed code primarily on NT-based Windows for over
ten years now in a variety of languages for a variety of purposes and not
ONCE have I managed to write userland code that was capable of causing a
hard-stop (BSOD, freezing).
In fact, I'd go so far as to say that the ONLY crashes I've gotten over the
last ten years have been due to terrible 3rd party drivers (Creative's
drivers for the SBLive were notoriously bad, and for awhile around the win2k
timeframe, nVidia's drivers were TERRIBLE on multiproc systems). This is
unfortunate, but these problems have since been resolved and these days I
can't even recall the last BSOD I've gotten.
If you're honestly crashing the OS fairly regularly (esp. w/Java code) then
I'd definitely suggest investigating the STOP code you're getting, and
checking your hardware out for faults. And update your drivers. Either
that or stop running Windows 95 :).
I realize it's par for the course on a list like this to bash anything
Microsoft, but I think the "it crashes ALL THE TIME" argument is no longer
valid. It's not like there aren't plenty of other complaints to make :).
- Josh