Not sure what the GP actually intended, but I'm convinced the fact that the kernel and a few thousand drivers all simultaneously have to be bug free for any given "release" is a serious problem. Should your hardware experience a driver problem you get to roll the dice again and hope the next version fixes your problem without breaking something else. Good luck, especially if you have a couple dozen different hardware configurations to contend with, especially if any of them are not x86.

Its futile, the drivers and the kernel should be separate and there should be a stable API, if not a full blown ABI for them. Linux has been evolving for ~20 years now its probably time to start trying to maintain some kind of actual kernel mode API. That way the _USER_ can pick and choose the kernel and any given set of drivers independently from one another. If kernel X happens to be "good" but you need a driver newer than that kernel you shouldn't have to upgrade to the latest buggy kernel just to get a driver for a more recent piece of hardware.

Android avoids this problem because the OEM spends time assuring that the driver set for their device is working/stable before shipping the device. Then rarely are they ever upgraded for anything other than bug fixes.

Hmmm, compare the options available via:

http://www.eightforums.com/tut...

with the options available in windows7 (and previous) in the "window color and appearance" dialog.

There are probably 4x the number of options in win7, including font selection/size changes that are simply not available on win8.

If this device is anything like the dell venue pro with 32GB, it works out to something like 17GB usable when you turn the device on, but by the time windows update runs its going to be less than 10GB free.

Lots of discussion about this on the internet, for example:

http://en.community.dell.com/s...

My only complaints are that Chrome actually performs quite poorly on sites with heavy AJAX (specifically Yahoo Mail), and that Flash is better off left not installed (darn). But Firefox appears to be much better optimized for low-end hardware, so I just use Firefox with no Flash.

On low end hardware I've been installing qupzilla. Its a webkit based browser minus much of the junk. It actually runs pretty good on windows2000 era machines, something that cannot be said for chrome/firefox at this point.

2GB per process - closer to 1.75 in practice.
3.25GB total usable.

First the 2GB limit is not fixed, it can be increased to 3GB. See http://msdn.microsoft.com/en-u...

The latter is a license restriction, not an OS one. There are 32-bit windows machines that can use 64GB of RAM and by default PAE is actually enabled by default on all versions of windows since XPSP2 (or was it SP3?) when DEP became the default as well.

http://msdn.microsoft.com/en-u...

So, if MS cared they could release a 32-bit windows professional that supports more RAM, they just choose not to. The real question is about drivers failing to use the HAL provided API's for DMA and such. While there were a few driver issues in the early 2k days most of them actually tended to work.

Classic shell gives you a start menu, and some of the customizations back, but your still up a creek if you want to say, customize the coloring of your window controls at a fine granularity, or a large number of other less noticeable UI changes.

I am, because after a single install for classic shell, you get a Windows that functions almost identically to a Windows 7 box

I use classic shell on the win 8/8.1, and frankly while its pretty tweak-able, it can't actually replicate the way I ran windows 7 nor the way I run windows XP. A big part of the problem in 8 is the removal of the ability to control with fine granularity pieces of the window decoration.

There are a lot of other issues, but win8 is just another half ass interface from microsoft layered on top of the half dozen other application UI paradigms they have tried to thrust on people over the past two decades. It doesn't take long before you notice that there are actually more than just metro/modern applications and applications with ribbons in win8. In fact last I counted there were 6 different application paradigms in the applications shipped with the OS going all the way back to windows 3.0. That is even before you install any 3rd party software.

I like the netflix app, that's about it.

Yah, duh, application that runs full screen on a single monitor for watching movies.

Full screen first person games might work too...

Same for XP which appears to have become the POS/embedded appliance with UI, OS choice a number of years ago. Those people seem to be in the "you can pry it from my cold dead fingers" type.

And since those machines probably don't even have web browsers in use they don't show up in surveys like this.

I have yet to see a windows 7 POS system, or display sign. Even technically savvy places like fry's are still running XP on their in-house systems.

I'm going to ad that I think usability with regard to discoverable interfaces probably peaked somewhere around 2000 as well.

Since they we have have had one trend after another to make interfaces look slicker at the expense of discoverablity.

First we started hiding visual hints (underscores on windows menus to indicate matching keyboard shortcuts). On and on, and lately we have the "flatten" UI paradigm where its impossible to even tell what is an active control from its surroundings until you start clicking/touching it.

Of lot of the problems in the computer industry stem from lack of proper well thought out standards. As well as the lack of licensing individuals and tool implementations. Diversity of implementations is good if the products adhere to standards. Everybody and their brother creating their own tool chains and proprietary (but open!) widgets that all solve the same basic problem has become the problem itself. We would still be in the preindustrial age if we were unable to standardize even basic things like thread patterns on bolts.

The software industry is the equivalent of recent HS grad noticing that his neighbor built a house using haybales (http://en.wikipedia.org/wiki/Straw-bale_construction) showing up at the city council and convincing them he can build a bridge over the local creek with haybales faster and cheaper than the local engineering firm. They proceed to hire, him and he in fact manages to build a bridge over the creek in an afternoon. Gets a lot of money, fame and further jobs. Its only 6 months later when the creek floods and washes the bridge away are the design tradeoffs apparent. By then, the kid has spent the money, moved out of state and is building cars out of cow manure for a large company.

The problem is, designing a building, pulling a tooth, or fixing a toilet is relatively easy. There are not so many different ways to do it.

There are actually a lot of different ways to do what you describe, you only think its straightforward because the industry has standardized on methods/tools/etc. Pumbing would be a lot harder if pipe sizes weren't standardized and every plumber around designed a toilet from scratch using tools designed by the guy down the street.

The problem with the computer industry is that lots of times people without a lot of formal training/experience are allowed to create a computer languages, application framework/etc. Those kinds of things are limited to the higher levels of licensing and standardization bodies in most industries. Its this very limit that results in the standardization, not the other way around. You can't even get a Journeyman plumbers license in TX without 4 years work experience as an apprentice.

Frankly, the basics of computer operations tend to be standardized by natural selection, the problems are the fact that there are a million different toolkits (often designed by people without a clue) with a million different bugs/edge cases to bite developers. Plus, a person certified with some level of "web development" wouldn't necessarily be tied to an industry like banking or medical software, especially if there was a higher level industry specific "master" license or some such that would sign off on the work. Its similar to the "architecture" positions in these organizations that are responsible for the design of the system, while the lower level coders do a lot of the grunt work.

In fact the PE licenses for civil/etc work much the same way. Getting a civil PE allows you to work in lots of different industries, but usually there is a senior person with a specialty that signs off on a given project. Freshly minted PE's don't get jobs signing off on large bridges, buildings, etc. Plus, a Civil PE usually will enlist the services of a Electrical PE or Mechanical PE for parts of any given project larger than a tool shed.

So, the problem you describe is a symptom of the lack of licensing not the other way around. Frankly, its only the ease of creation of software that allows this to propagate, any other industry would be hamstrung if it couldn't even depend on something as simple as bolt thread patterns and heads being somewhat standard. Sure programming might not be as exciting if everyone had to learn and prove some level of mastery of Ada but I'm betting there would be fewer stupid mistakes being made by bright people writing an application in languages they have never used before because its the "cool" language du jour.

Heck, I am not even allowed to pull a simple tooth without a proper license. If that is not a real scandal....

Maybe the real scandal is that any idiot can convince themselves they are the next Dijkstra, blow some smoke up a midlevel MBA's backside and get hired to write the front-end for the bank you use, or the local software contractor building some part of the control system for the car you drive.

As a society we have decided that we actually want people to have some level of licensing before they design a building, pull a tooth, or even fix your toilet. Yet we allow people without any formal licensing, or competency to design/write critical software.

If you want to have the same level of usefulness now as there was in the 80's, learn Mathematica, MatLab, or Learn Perl,Python, or Ruby

If you want a career in programming maybe, but most of the people writing spreadsheet macros and dbase forms in the 80/90 weren't professional programmers either. Excel and Access are still around, and can solve the same basic problems that they solved back in the 90's without the huge learning curve of ruby, rails, html, javascript, css, datastructures and algorithms, etc just to perform a couple fairly simple computations or graph some data, or create a couple basic input forms.

Sure the solutions created may not be professional programmer quality, or scale to millions of users, but they are often simple solutions created in a matter of hours for real problems being faced by real people.

Frankly, the web is the absolute worst platform for many of these kinds of applications because its takes a problem solvable by a non programmer in a few hours and turns it into a problem that can take a team months. I suspect that a lot of web developers would really have their eyes opened if they spent a few dozen hours slapping together a couple little applications in Access VBA.

Only makers of proprietary modules, and sycophants and nay-sayers complain about the Linux kernel not having a static API and ABI for kernel modules.

Ok, so this is going to sound like flaming but its not.. Because _ANYONE_ who has used linux for any extended period of time in a non trivial manner and, who is being honest with themselves has had problems due to the kernel and associated drivers being tied together.

Thats because without fail, the drivers for every single piece of hardware and the kernel/userspace API's don't all tend to move at the same speed. This means that when you have a problem with a driver for a particular piece of hardware in your system, being forced to take newer versions of drivers for every other piece of hardware is a recipe for something breaking. I have a pretty functional laptop running a recent distribution, I was pretty estatic when about 90% of my use cases actually worked. Sound, 3d graphics, suspend/wakup, wifi, EFI boot, on and on. But, in the end, i'm not running the latest GL SL, because its not supported, I have to hand modify the bluetooth driver to get my wireless mouse working, and I had to hack KDE and the OS to get the back-light dimmer to work properly. Then every couple weeks/months a new kernel gets rolled out to fix some problem or another and I have to reapply my changes.

I could write a 1000 page book about driver/kernel problems I've personally seen, and you need only spend a little time on LKML to notice that driver developers on linux don't really appear to be any better than any other OS. They make forward progress most of the time, but they also regularly regress some feature or another resulting in plenty of pain. Expecting the few hundred developers involved in the kernel/drivers for any particular machine to GET IT RIGHT for in any given kernel release is an exercise in fantasy land. Expecting the ten thousand or so involved in every driver in the kernel to GET IT RIGHT for every single machine running linux is even more fantastic.

So, a problem like this has a solution, ignoring it for religious reasons doesn't.