you must consult with Imagination before you change it.

Yes. And what happens then?

I haven't in general met many professors (or EEs) who understand much about intellectual property.

OK. Can we see your agreements, please? Because that did sound very much like trolling for additional intellectual property to add to your portfolio.

People who read this article have pointed out three open CPU designs in addition to the one that I remembered.

While your product might be "production ready", please keep in mind that open projects are very often written to a higher standard than commercial ones, and the researchers involved are no less professional than your own developers. And their projects come with fewer intellectual property issues than yours.

Well, sure, but here's a question for you:

What was the first version of Internet Explorer that included it?

Because the IE XMLHttpRequest documentation doesn't list it as a member. (I think that's the most recent documentation, but with MSDN, who even knows.)

And their example uses oReq.readyState == 4 /* complete */.

Then again, who knows when that page was last updated, and the standards they link to do include DONE. (And I checked: IE 11, at least, has it.)

It's only "free" for academia.

Not even them. This is a lure for universities to create tech that they are not allowed to produce in hardware, but the company that provided the original tech can monetize.

The patent terms are whatever they want them to be. In general "reasonable" and "patent" don't happen together much. And "tiny", well I really doubt it.

Having a company provide funds for a research grant and then reap the patent royalties isn't in general a good thing for society. The student researchers get paid like slave labor (if they get paid at all) and put what may be the best idea of their lives in some company's pockets.

Basically this. jQuery is one of those things that's almost literally bloat: it adds nothing that your browser can't already do, it just wraps around it. You absolutely do not need to use it.

However it saves on development time. It's effectively a bunch of boilerplate code that you don't have to deal with. It's one of those things that if you were to decide not to use it, you're likely to end up rewriting a chunk of it by the time you're done anyway, so you might as well go ahead and use it from the get-go and save yourself some time.

(Which isn't to say you should always use it. I've written pages where the amount of dynamic code was small enough that using jQuery would make absolutely no sense. But the larger your project gets, the more sense it makes to use frameworks like jQuery.)

You mean it's there now. Going back through previous version of the XMLHttpRequest spec, it wasn't added until June 2007.

Who knows when it finally made it into enough browsers to be safe to use. By now no one uses it more out of momentum than anything else, but it wasn't a part of the spec originally, and people writing tutorials would use "4" because that would work even in browsers that hadn't been updated to use the latest spec.

But I was under the mistaken impression that one could only burn an FPGA once. Thanks for clarifying that they can be reused.

You burn an EEPROM so I was using the same terminology. It's still usually called "burning" even though you can re-burn the same device with different code.

...cannot build it into silicon.

Isn't the whole point of an FPGA being able to "burn" a design into a chip rather than "building" it? Are they saying you can only run your modifications through a simulator instead of burning an FPGA to test it?

If so, what's the point of the exercise? Wouldn't it make more sense to have students play with an open sourced or freeware design that they can actually implement and test?

If only your "Exhibit A" wasn't mostly selective golden memory tinted by rose colored glasses. The "great uplift" was indeed (mostly) great - if you were a white collar worker in the city, or an industrial worker with a union. For the laborers down on the farm, the topic of discussion, not so much.

Pretty sure it was proportionally at least as good - probably better - for unskilled labour.

And even then the "great uplift" wasn't powered by smaller profit margins or worker's rights - it was powered by rising salaries, employment, and consumer spending. (Emphasis on the last.) It couldn't last, and it didn't.

You need strong worker's rights for (sustained and economy-wide) rising salaries, secure employment and, consequently, high consumer spending.

I'm stunned at how many sports channels I had to block even with basic IPTV from SaskTel here in Saskatchewan, Canada. I have ZERO interest in sports, and I'm kind of pissed off that some of the money I pay is going to support that crap, which I do not and will never watch.

I'd much rather have something like BBC News or BBC1 than a bazillion sports channels.

Given a choice, more is always better.

Even though my Lenovo Z580 has four USB ports, I often find myself wishing I had a couple more so I wouldn't have to swap devices. In particular, I'd appreciate another USB 3.0 port for an SSD (seeing as the "second" hard drive tray slot is occupied by the DVD drive, which I *do* use.) Sure USB 3.0 isn't as fast as I'd get with SATA, but it'd be a darned sight faster than the 5400RPM drive that's built in to the unit.

Normally I have the printer, mouse, and external HDD plugged in. That leaves one slot for a keyboard (I have no room for another one on my desk, though, so I rely on the built-in keyboard), camera, MP3 player, and charging the ole' eCig.

It's very common these days for companies to allow universities to use their technology at the cost of tying the company into the university's patent revenue. And of course this is often publicly-funded research, so not only is the taxpayer paying for the development of patents used to sue that same taxpayer, the patents go directly to a company from academia.

The net effect is to feed intellectual property centered companies at the expense of the technology sector in general and small technology companies in particular.