I'd say not. Then again I have a lot of experience with many different operating systems, not just those for PCs.
Let's see. I have supported MVS(IBM mainframes), MPE-V(HP minicomputers), VOS(Stratus minicomputers), Ultrix (DEC-Unix), AIX (IBM Unix), Solaris(Sun Unix), VMS(DEC minicomputers), Linux(various and sundry versions), FTX (Stratus Unix), OS2, and all of the various Windows incarnations. I'm reasonably sure I left some out. Each had it's own strengths and weaknesses. Some were extraordinarily resiliant, for instance, you could pull a motherboard out of a Stratus box running VOS or FTX and the box just kept on running. AIX was an excellent Unix in many ways. VMS was an uptime freight-train. MPE-V was doing some really cool things with networking that I absolutely loved as an administrator. I recall logging into an AIX box once that had 5 years(!!!) worth of uptime when I was asked to take over support of it. I really hated having to patch that box the first time. No version of MS-Windows has ever had any kind of reliability. For quite a while Windows (I think it was XP) had a bug where the system would hang with a BSOD after about 50 days. It was a hard stop, every single time even if the system was doing nothing for that entire time. It took ages for them to even uncover the bug because the systems were generally so unstable anyway. Every version of MS-Windows has been a virus-magnet, and until Windows 7 or so, always seemed to have security as a bolted on afterthought.
If your computer is a toy that you like playing games with, I'm sure it's fine. Some of us want to do actual work with our computers though.
This was stolen from this page.
Why Windows 95 and Windows 98 would crash after 49.7 days of uptime
There’s a famous bug in Windows 95 and Windows 98 (now patched) that caused these systems to stop functioning after 49.7 days of uptime. I used to wonder how this happened – in addition to wondering how many Windows 95 / 98 systems could achieve such uptimes to begin with!
Finally, I did a little math and figured out what must be behind this bug. It’s actually quite cute.
First, we need to know about a function called GetTickTime which is part of the Windows API. This function returns a DWORD value representing the number of milliseconds which has elapsed since the system has come up.
What’s a DWORD? A Word on an x86 is 16 bits, so a Double Word is 32 bits. The maximum number expressed in 32 bits is 2 to the power of 32.
2^32 = 4,294,967,296
We’re expressing a number of milliseconds here. How many milliseconds are there in one day?
(milliseconds per second) * (seconds per minute) * (minutes per hour) * (hours per day) = 1000 * 60 * 60 * 24 = 86,400,000.
Finally, we can find out how many days’ worth of milliseconds we can fit in the DWORD:
4,294,967,296 / 86,400,000 = 49.7102696
Voila! After 49.71 days, the number of milliseconds since startup exceeded the maximum value of a DWORD, and rolled to 0 (kind of like the odometer on Al Bundy’s Dodge rolling to 0 after the 999,999,999th mile)
Depending on how you process the return value of GetTickCount(), this may or may not be a problem. Clearly some code in Windows didn’t handle this too well, and Windows hung.