Microsoft's Most Successful Failure
m4dm4n writes "As we near the end of mainstream support of Win2k The Register looks back at what it has achieved. What was meant to be Microsoft's most secure OS ever turned into a disaster. Worm after worm changed the face of internet security in Win2k's first 2 years. Five years down the line the battle is far from won, but the improvements are dramatic." From the article: "Things were different in the year 2000. Programmers felt vindicated that the Y2K bug didn't turn out to be that big of a deal. We made it past January 1st, and then it was time to move on. Windows 2000 came out that first quarter, just as security was becoming more interesting to more people -- and Windows was a good place to start. It was also seemed to be the start of a new breed of Windows hackers."
but atleast it didn't took me 4 years to get my printer up and running... all in all I am very happy with linux, but why does it always have to be win=bad lin=good everywhere.
I won't make an arguement about security problems in Win2k, since the article is correct. However, I will say that I think Windows 2000 is the best MS OS to yet come out. The GUI is far better then XP (IMHO), has support for all the latest "bells and whistles", and it is FASTER than the equivalent XP machine.
I can't see how you can honestly call Windows 2000 a failure -- Microsoft didn't spend more making it than they made off of it, and it was actually (in my experience, at least) more reliable than XP.
I was the first STABLE windows platform that could handle multimedia apps.
Security became a joke, but stability was superb.
It was a gigantic leap from the 9x series.
Cheers,
Adolfo
Considering this is supposed to be a joke . . .I recently got an XP machine at our office without an a: drive (31/2"). Windwos seams to think it has one though, it shows up in explorer, and you get an error if it is selected. It also generates an error every time the computer is shutdown.
Sad when jokes become reality. . .
A slightly off-topic comment, that I feel I have to make to someone somewhere...
My boss and I were talking a week or so back, and we were talking about taking a bunch of our libraries and somehow making them into something we can use everywhere. Now realize that we, unfortunatly, have about 200 applications to maintain, across Visual Basic, Delphi, Java, C++ in many flavors (Borland and MS are the majority) and a slew of other crap, including some VB scripts.
Now, obviously, a plain DLL isn't going to cut it... VB would be a pain in the arse to translate all of the declares to, and Java would need something similar to use a native library.
This IS where ActiveX control/libraries come in. And thanks to even automation, I can EVEN use said libraries in the windows scripts via a magical CreateObject.
The nightmare of using ActiveX controls on a webpage shouldnt blur the actual usefulness of the technology possibly elsewhere.
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
just imagine if the nature of the stack wouldn't allow [buffer overruns]. If some kind of mechanism beside a simple jump had been used. Like registering an address in the CPU via an instruction and then calling that jump.
Would it annoy you to no end if I explained that you've just described the segmented memory model that has been available on the 386 and up since 1986? It just so happens that today's "Modern OSes" (right load of bull that is) map only two memory segments, then completely ignore the GDT, LDT, and TSS after that? It is, of course, done all in the name of "Performance", the mini-god for which many a programmer has sacrificed his first born for, but has never actually managed to show that this "performance" was worth it.
<sarcasm>But wait, we must claim that Java is slow in order to appease this mini-god! </sarcasm>
Javascript + Nintendo DSi = DSiCade
I agree.
Most people who bash ActiveX controls haven't really been in enterprise development environments where they have used them.
While their security aspect is a bad thing, they're quite useful in their own way.
They've got security confused with reliability.
Before Win2k, reliability was what everybody complained about, blue screens of death, constant crashing, runing out of resources, that sort of thing.
Microsoft listened, claimed reliability was their priority, and eventually released Win2k which fixed all of those problems. Win2k has crashed on me all of 3 times while using it both at work and at home for nearly five years, twice due to worn out CPU fans, and once due to hard drive failure. So while my experience is anecdotal I must say Win2k was an incredible success - more than I thought was possible from that company, it certainly changed my view of Microsoft.
Fast forward a few years (2002 - 2003ish), BSODs are now a thing of the past, leaving the increasing viruses and malware as the #1 headache on Windows.
Microsoft listens, claims security is now their #1 priority...
Will their security push be as effective as their stability push? only time will tell, but after the magic they worked with Win2k I'm no longer putting it above them.
Personally I care little, Windows boxes I've had connected to the internet for years without a virus checker are still clean. It appears Windows viruses so far have been limited to inexperienced users and boxes that aren't behind a proper firewall.
Microsoft execs - remember you have a fiduciary responsiblity to shareholders to do what's in the shareholder interest. Clearly your newfound obsession with security hype is not playing to your strenghts, and forcing you to play in a market where you're clearly outclassed (linux/bsd). Microsoft, as a shareholder, I'm begging you do go back to your previous policies of balancing Time-to-Market vs Security in a way that plays to your strengths and maximizes your profits and my stock value.
" Step 1: Build a monopoly for a required commodity"
You can't build a monopoly without producing something a lot of people will come along and buy.
"Derp de derp."
There's no way i could ever claim that 2000->XP was as big or as useful of a jump as 95->2000, but i personally think it's kind of annoying that people bash XP. I mean, maybe it's over-priced, and yes, it does have a hideous default window theme, but i actually thought XP was a great step up from 2000.
Granted, better graphics and window themes and a better Start menu and user switching and a graphical log-in screen and better drivers and a better taskbar and a better tray and a better file manager and a better network manager and nicer-looking fonts and easier access to scanners/cameras and so on might not make or break the operating system, but i sure think they make XP a lot nicer than 2000.