Right you are. However, what is illegal is publically stating someone has committed illegal acts. Nohl should sue for slander.

They can't afford tabletop models anymore, so in this project they used paper cutouts on a black canvas.

The VA provides single-payer, single-provider, socialized, health care for the Army.

In other words, we need GNU Ecmas.

As a CS student I think you should focus on product development, not IT. You absolutely should intern at a technology company whose main focus is products - and whose _customers_ may include IT departments. You won't be paid a whole lot, but the tasks you get will also be very simple, relatively speaking, and while they may be important, once taken care of you'll have plenty of time to poke around with whatever interests you. You may be asked to say add an option to a compiler, tweak a kernel build, or add data gathering and instrumentation - things that the other developers would like to have but don't find time to do themselves. If in the process you find something you think might make an interesting project by all means suggest it, chances are you'll get to go do it, unless it seems overly ambitious to the extreme.

I guess at 45 I qualify as "older" in this context. I don't post personal details, or say things I don't want my business contacts to be aware of. FB serves the same purpose to me as a cocktail party - it's just a simple social function. I don't really care who wants to be my friend (which I view more as a 'live rolodex') - you never know who might be handy to know. I have about 300 friends on FB. My wife, who's a freelance writer and has to network as part of her business, has over 1500. It's just a tool, and like any other becomes what you make of it. I personally like it better than LinkedIn, which is too formal.

No kidding, I was always wondering how they got away with billing it as a screensaver. I left my PC powered on accidentally when I went on a four week trip in 2004 and came back to a 24" Sun CRT with SETI@HOME permanently burnt into the center. Screendestroyer is more like it.

With that kind of money it should be easy to keep your own private army or buy protection from a warlord.

Perhaps, but if the northern hemisphere becomes uninhabitable a billion or so people will want to migrate south. The northerners will still be the most heavily armed in the world, have a long history of manufacturing excuses for wars that are thinly disguised land grabs, and aren't going to take no for an answer.

So did I - spent time in the local woods, swam in the lakes, jumped in every muddy puddle to be seen, played out in the rain, and whatnot. I'm still allergic to cats, some detergents, and natural rubber (latex, avocado). This was in the mid 70s, and people had allergies then just like today. It's just the bar was much higher and people didn't really consider it an allergy unless they were likely to go into shock or develop serious symptoms. A little spring sniffle caused by pollen wasn't really hay fever unless it caused breathing difficulties or made your eyes puff up so bad you couldn't see. Anything else just wasn't bothered with and parents would tell their kids, "yeah it's just a little spring pollen, now go to school."

But what? There's nothing inconsistent about that - the air isn't your property to do with as you wish. It's held in common trust, so rules for its use (and abuse) is set through democratic political process.

Ah yes, that would be a pipelined design. I think that would work more efficiently than the original DDJ story's.

I think too much significance is place on the "single instruction" aspect; the DDJ design is really "single instruction format". It clearly has multiple operations, and the destination address is more or less an opcode field. So it's more accurate to describe it as a single-instruction format machine. Each operation has its own dedicated destination register which can be used as a source for operations.

All the execution units (aka co-processors in modern parlance) are still attached to a single bus, so theoretical max throughput is still one instruction per cycle. So this only makes sense if the CPs perform complex operations - like memory management, floating point, mul/div - or something of similar complexity. For the typical simple integer instruction that tends to dominate code it's no better than a microcoded processor - since now each normal instruction requires several cycles on the bus.

Compare this to a pipeline, where each step is what you'd consider a FU, but each one only needs to interface to the previous one, not counting the occasional clever bypass and special linkage. In a pipeline each FU can be fed an input in one cycle and provide an output in the next, something "FU"s (CPs actually) on a shared bus can't.

The other drawback is that anything that goes on the bus needs to implement a generic bus interface and its own internal sequencing logic. This doesn't come free. This is really just a CISC in silicon with exposed microcode, and it's pretty clear the author is thinking CISC all the way as can be witnessed by the stack operations. The typical RISC approach is to have a link register where the return address is placed on subroutine calls, so leaf functions don't have to push/pop it from the stack. Non-leaf functions start by saving the link register to the stack frame in the function prologue once space has been allocated for it.