That was OS/2 2.0, the 32-bit version released well after Windows 3.0. Windows 3.0, unlike the contemporary 16-bit OS/2 1.x, allowed one to finally use all their RAM (plus virtual memory in 386 enhanced mode) and multitask DOS applications, which could also use extended memory. See: http://virtuallyfun.supergloba...

More like Google doesn't appear to support RTMP like everyone else. Someone could add support though as its open source.

NetUSB is used by some printer servers to allow use of USB only All-in-One printers and scanners over a network. I had to fix a setup once, and it was nothing but a buggy mess. The printer and its drivers were never designed to be used in a shared environment and the client machines needed some really ugly "Virtual USB" driver to fool the AIO's software into thinking it was directly connected to the machine. It worked sometimes, just never EVER try to print or scan from multiple machines at once.

I encountered this with the Cairo Graphics library. They do have very basic tutorials, but nothing that covers the advanced functions. Any graphics library/API should show the desired output alongside the code since a picture is worth a thousand words. :P The best example of this I have encountered is Postscript: A Visual Approach. The book's examples showed the source code on the left page and the actual output of the code on the right page. The book also did a good job of explaining how coordinate transforms work, something that is important when dealing with vector graphics.

Sounds like the man page for the "tar" command. This is analogous to someone giving you a box of tools and some materials with a piece of paper explaining what each tool is used for, but no instructions on how to put whatever it is together! I am trying to address this with an open source project I am working on. I broke the document down to the following sections:

Getting Started: Covers basic setup and configuration. It gets the user up and running step-by-step with the defaults complete with screen shots. It tells users everything they need to know and nothing they don't. This is what is usually lacking from most open source projects. Many times they leave you hanging after "apt get"

Advanced Configuration: Covers every configuration option in detail and the option's expected behavior. This is for the power users and the folks who need something other than the defaults.

FAQs/Troubleshooting: Covers common problems and how to fix them. Also covers any questions that can't be explained by the configuration options alone.

I am in the process of documenting a system I added to an open source project. Its not easy to write, particularly if one doesn't have a background in technical writing. The basic process the same though, you have to write for your audience, and revise.... a lot. In my case, I have been sending drafts of my work to other developers in the project to not only proofread, but to actually read through the directions and perform the listed tasks as an end-user would. So far the feedback has resulted in changes in both the documentation and the program to make things easier/clearer for the user.

I guess what I'm trying to say is, don't skip review and just post the documentation. Give the documentation and software to someone not familiar with it and see how they interpret and understand it. Listen to their feedback. Way too many developers don't (I'm looking at your Google!). Wikis are supposed to address this, but don't seem to engage enough people to actually contribute.

The working examples are the most helpful thing. I have seen documentation that covers the API in all of its technical glory, but with very few/no working examples for each of the functions.

That company was Motorola. Now look at them.

That being said, its still possible to repair a modern TV. I fixed a 4 year old plasma TV with a service manual and a multimeter to determine the fault. Actual component repair of the faulty board was outsourced to a refurbishing company (the price over buying the parts kit alone was minimal). Popped the repaired board in and the TV is as good as new.

Oil changes are typically "loss leader" pricing to get your car in the service bay for other work. I used to know someone who owned a car dealership and he said the most profitable thing he ever did was give free oil changes to anyone who purchased a car there.

SATA Express is the cabled equivalent of M.2, but it is limited to 2 PCIe lanes vs. the 4 possible with M.2.

Those illegal opcodes caused problems on the Apple II. Later machines starting with the Apple IIc used the 65c02 which defined new functions for some of the previously unused opcodes.

NJ (#2 in solar in the US) has a subsidy scheme with "Solar Renewable Energy Credits". Many local governments bet on that subsidy to pay off solar panel installs with these SRECs, only for the market to crash (a victim of its own success) : http://www.nj.com/morris/index...

Note the collapse in prices: http://www.srectrade.com/srec_...

Some of this can be attributed to the College Board changing the language of choice for the AP Computer Science test curriculum from C++ to Java in 2004. Most universities in the US phased out C++ in their introductory programming classes after that. I'm also disappointed they phased out the AB Computer Science test.

You can also add NJIT to that list of places that require programming. Check out the syllabus for CS288. I was required to take that class back in the day. It was a joke, mostly because it was developed and taught by a tenured professor that didn't seem to enjoy his job. Somebody else appears to have taken over a revamped it. Plenty of pointers to be found there.

After taking several semesters of Calculus without a calculator (department enforced), I can say its more about developing problem solving skills than it is actual arithmetic. Some of the higher end math beyond the basic undergrad Calculus courses is used in advanced programming algorithms (things like encryption and data compression) , but the majority of programmers aren't going to be exposed to that in the real world.

There are quite a few people who enter CS programs that are game players that want to be game programmers, but quickly drop out or switch majors once they find out how difficult it really is.