OSDev.org

I have found this website that says why windows is so unstable and what the major flaw of windows is..
http://osdata.com/holistic/reliable/rel ... m#registry

Windows' and Microsoft's major flaw is their complicatedness. This also applies to incoming vista. MS can't do simple or complex without doing it complicated also. MS vista is the biggest waste of time I can think about.

It's not the concept of a central settings database which is flawed, it is the implementation. The "flaws" the text describes could all be solved easily by a proper implementation of the concept. It's just typical Microsoft that they implemented the Registry so poorly that even a flat-file solution like /etc looks better by comparison...

website wrote:“I see the existence of the registry as a ‘fatal design flaw’ in NT for the following reasons: 1.) it is the most modified file in an NT system. 2.) the most modified file is the one most likely to be corrupted. 3.) when corrupted the registry crashes the OS.
“No amount of changing data structures or algorithms can fix those fundamental problems.” —Bob Canupe88

What ever happened to journalled file systems such as NTFS? They make corrupting files impossible negating point 2, which might just explain a few bits of design of NT. That everybody keeps installing XP/Vista on FAT partitions is their own stupidity.

It's not only about journalled file systems. I mean, if concurrent access to a file were such an impossible-to-solve problem, how come that MySQL, PostgreSQL etc. work so fine, even on non-journaling FS? (Rethorical question warning.)

Solar wrote:I mean, if concurrent access to a file were such an impossible-to-solve problem, how come that MySQL, PostgreSQL etc. work so fine, even on non-journaling FS? (Rethorical question warning.)

Let me answer that question for you

It's not about concurrent access. That's fine. It's about Windows itself crashing or something bad happening to the hardware underlying the system, causing a non-stable status of the disk in which some writes did and some didn't occur. That could make the registry part-deleting a key and part-not-deleting a key. Starting with such a registry makes a bad start.

Understood. But still: You don't need a journalling file system to protect against this; all you need is a journalling file (which Microsoft "forgot" to implement).

Wouldn't it be nice if Microsoft would go back and fix what is wrong with Windows BEFORE they add new features and release the next version? Unfortunately, people run Microsoft and these people don't seem to care that they're releasing the equivalent of a faulty product.

Of course, there are some good things in Windows, it's just that the bad things are what we all remember .

pcmattman wrote:Wouldn't it be nice if Microsoft would go back and fix what is wrong with Windows BEFORE they add new features and release the next version?

Joe Average doesn't pay for "obscure" fixes, Joe pays for shiny new features. Since the Joes are the vast majority of Microsoft's customers, they get what they want - that's capitalism for you.

Solar wrote:

pcmattman wrote:Wouldn't it be nice if Microsoft would go back and fix what is wrong with Windows BEFORE they add new features and release the next version?

Joe Average doesn't pay for "obscure" fixes, Joe pays for shiny new features. Since the Joes are the vast majority of Microsoft's customers, they get what they want - that's capitalism for you.

Capitalism pur sang is getting the product that joe average will pay for, at the price most joe averages will pay you for a total max profit, at a minimum of development expenses. In other words, cutting as many corners using the shittiest systems available so that joe average thinks it's good enough to buy once.