the web author has already explicitly said he wants strict rendering, because he said so in the DOCTYPE.
That's not a realistic assumption. It'd sure be nice, but it's complete fantasy to assume that every page with a strict DOCTYPE was written by a benevolent developer who is willing to fix every page he ever wrote after every release of IE.
Microsoft's solution is messy, but breaking millions of pages for the sake of standards is just a purist's dream.
Drivers - People say an OS is only as good as the software for it, and I'd argue an OS is only as good as the drivers. If you can't support your hardware, then software isn't even an issue. Now all drivers MUST be signed, yet many signed drivers don't work very well, if at all. I think it would be a good idea to have all drivers in one central repository (like the Linux kernel) so you won't have to worry about tracking down drivers for old hardware, but make sure the drivers work. And here is an idea, make the drivers modular. Drivers cause more BSODs and crashes than anything else. Don't let a single driver bring down a system. This is just basic common sense.
First of all, you do know that the vast majority of drivers for Windows are written by third parties, right? (nVidia, ATi, 3com, etc.)
Second, the reason they cause BSODs is because most driver code runs in Kernel mode. When the OS executes driver code in kernel mode, it is basically handing control over to the driver for a short period of time. If the driver makes a booboo, there's typically no recovery. In user mode, the OS would be able to catch the error and halt the process, but in kernel mode it is the CPU itself that often throws the error.
When you're in kernel mode, even small things can BSOD the box. For example, going into dispatch mode (disabling interrupts) and then waiting for a message from another process. This results in deadlock, and the CPU can detect this. The result is a BSOD (technically the CPU is calling the code to generate the screen). When you see the stop error IRQL_NOT_LESS_OR_EQUAL, that's usually what the problem is.
Theoretically, the OS could load the drivers in an emulated mode, to make the drivers think they are running in kernel mode when they are actually in user mode. That would slow current drivers to a crawl, though. Forget about games, gigabit ethernet, and Fibre channel.
A true solution would be to rearchitect the whole driver model to allow performant drivers operating entirely in user mode, and Microsoft actually pondered this, but it received so much pushback from third parties that it was scrapped.
In short, you have the right idea here, but it's just not that simple.
Welcome, welcome to City 17. You have chosen or been chosen to relocate to one of our finest remaining urban centers. I thought so much of City 17 that I elected to establish my administration here, in the Citadel so thoughtfully provided by our benefactors. I have been proud to call City 17 my home. So whether you are here to stay, or passing through on your way to parts unknown, welcome to City 17. It's safer here.
It's interesting to note that Netflix' former COO, Bill Henderson, was the United States Postmaster General from 1998 to 2001, so I have to think their relationship with the USPS is nothing but close.
Note: Henderson's role changed to strategic advisor in February 2007.
Slashdot Mirror
Here, a gift for you: . . .
Specially made, just for you!
Microsoft's solution is messy, but breaking millions of pages for the sake of standards is just a purist's dream.
Second, the reason they cause BSODs is because most driver code runs in Kernel mode. When the OS executes driver code in kernel mode, it is basically handing control over to the driver for a short period of time. If the driver makes a booboo, there's typically no recovery. In user mode, the OS would be able to catch the error and halt the process, but in kernel mode it is the CPU itself that often throws the error.
When you're in kernel mode, even small things can BSOD the box. For example, going into dispatch mode (disabling interrupts) and then waiting for a message from another process. This results in deadlock, and the CPU can detect this. The result is a BSOD (technically the CPU is calling the code to generate the screen). When you see the stop error IRQL_NOT_LESS_OR_EQUAL, that's usually what the problem is.
Theoretically, the OS could load the drivers in an emulated mode, to make the drivers think they are running in kernel mode when they are actually in user mode. That would slow current drivers to a crawl, though. Forget about games, gigabit ethernet, and Fibre channel.
A true solution would be to rearchitect the whole driver model to allow performant drivers operating entirely in user mode, and Microsoft actually pondered this, but it received so much pushback from third parties that it was scrapped.
In short, you have the right idea here, but it's just not that simple.
They're pretty neat but if you look at the sun it bur#!2k4#$#$#_#_####[NO EYEBALL FOUND]
Chapter 5
???
Welcome, welcome to City 17. You have chosen or been chosen to relocate to one of our finest remaining urban centers. I thought so much of City 17 that I elected to establish my administration here, in the Citadel so thoughtfully provided by our benefactors. I have been proud to call City 17 my home. So whether you are here to stay, or passing through on your way to parts unknown, welcome to City 17. It's safer here.
It's interesting to note that Netflix' former COO, Bill Henderson, was the United States Postmaster General from 1998 to 2001, so I have to think their relationship with the USPS is nothing but close.
Note: Henderson's role changed to strategic advisor in February 2007.
No cause for panic, everybody. I checked, and it's still running just fine.
And in A.D. 2101, war was beginning.
Now you see the true genius of Sony.
I believe you are referring to John Gabriel's Greater Internet Fuckwad Theory.
http://docs.google.com/Doc?id=dhjjdf9j_5c2cch4
Space. It seems to go on and on forever. But then you get to the end and the gorilla starts throwing barrels at you.