My wife and I have a Dell 1710 printer at home, that's a B&W non-duplex model made by Lexmark, and I'm waiting for it to die to replace it with an HP equivalent. The Dell prints great at first, but altogether too quickly , the output becomes shoddy. I've not had such problems with the HP printers in my lab (again, with 25k pages per year at work).
Out of curiosity, are you seeing print quality issues with the OEM toner, or are you using aftermarket toner?
So you're complaining and threatening to remove the drivers in the next release unless they commit resources in perpetuity to maintaing the drivers vs. *your* code base.
I don't think that's the situation. The drivers currently only exist in the -staging tree. That is far different than Linus' official tree. The -staging tree is home to driver code that does not meet the standards of Linus' tree, and it's purpose is to assist the maintainers of the code to increase its quality such that it can be included in Linus' tree. MS is not being asked to "commit resources in perpetuity," but merely to get the code up to the state where it can be included in Linus' kernel tree.
This is really a stupid demand on your part;if the kernel level APIs (what Sun calls their DDI/DKI - Device Driver Interface/Device Kernel Interface) in Linux were stable and not such a moving target, you could just forget the drivers and they'd keep working indefinitely.
See above. Once the driver is included in the kernel proper, the kernel developers themselves fix drivers when API's change. That's one of the primary benefits of being included in the kernel proper. If you're developing driver code and just dropping it on some corner of the web, then You're Doing It Wrong.
I'm using an Android phone with Sprint. The Sprint Touch/HTC Vogue runs Android like a champ.
Where is the standard UI library for C++, where the standard networking library?
I'd rather have several really good libraries (GTK, Qt, etc) than a really crummy standard library (GDI, winsock).
Also, if you want to make assumptions about type sizes, that's why uint32_t, uint64_t, intptr_t, etc, exist. Likewise with endianness and ntohl().
I know there's a Soviet Russia joke in this.A hand-held pager is given to a random member of the Regal Crown Club Loyalty Program who's attending each movie. "If any situation does arise they can just press a button which goes directly to the pager which the manager will have and they'll signal it and they'll go right into the theater and handle the situation," theater manager Heather Dematteis said.
Intel CPUs are not defective, they just act that way. -- Henry Spencer
