The distinction here is between word-addressed and block-addressed memory. Cartridges were more often word-addressed, but it isn't quite a reliable predictor of this. TG16 "cards" were word-addressed and allowed execution in place. Nintendo 64 and Game Boy Advance "cartridges" had seek-and-read protocols, which were a compromise between word-addressed and block storage but allowed execution in place through caching (N64) or lots of wait states (GBA). Later systems were more likely to use block devices because RAM had become so cheap and block devices require fewer pins on the connector.

The "system cards" used with the TurboGrafx-CD expand the TurboGrafx-16's capabilities. And any SPI peripheral can be put on a DS Game Card. Most often it's used for a serial flash memory for save data, but the Pokemon HeartGold and SoulSilver Game Cards for DS also include an infrared transceiver for communication with a "Pokewalker" pedometer that the player uses to take one of his party members on walks.

If no Mega Cartridge or Sega Card was inserted into certain revisions of the Master System, the player could launch the built-in Snail Maze game by holding Up + 1 + 2.

No, "anti-Bono" means you oppose the unbounded extension of the copyright term.

With even home Internet providers enforcing monthly caps, how will you fit your 3D 4K movies across a home Internet connection without having to take a week off surfing after streaming a single movie? (4K, or quad HD, is the next step beyond high-definition video. The consumer version has roughly 3840x2160 pixels.)

Unless Debian happens to be compromised at the time you download packages, as it was in October 2003 and July 2006.

No, they come on a "game card", like games for Nintendo 3DS, Nintendo DS, and TurboGrafx-16, and smaller games for Sega Master System.

You missed my point. A game card, like a cartridge, is solid-state storage on which a game is shipped. What is the essential difference between cartridges and game cards other than that game cards are thinner? Would you claim that the Master System and TG16 were not cartridge-based consoles because of Sega Card and HuCard?

Unless you want to play games with house guests who happen not to have brought a gaming laptop. In theory a home theater PC could serve this use, but in practice there are more consoles than home theater PCs.

Every iTrinket since the first generation iPod has had a headphone jack. Plug in a pair of Koss PortaPro headphones and hear all.

But once you tap the app, how do you control the character in the game? A flat sheet of glass gives the thumbs no tactile feedback as to where the on-screen action buttons are. Swipes on the left third of the screen can substitute for an analog stick, as first seen in Super Mario 64 DS and Metroid Prime Hunters First Hunt, but how can the player make sure he doesn't miss the jump, fire main weapon, and fire secondary weapon buttons? What's the uptake for clip-on Bluetooth gamepads?

Let me guess: You don't have a Game Boy Advance, Nintendo DS, Nintendo 3DS, or PlayStation Vita. All use cartridges.

Presumably the same way OnLive works: a pile of blades in the carrier's datacenter.

The only thing "blazing fast" about a mobile operating system built around access to an application server through VNC or OnLive is how fast it'd eat up your monthly data cap.

The whooshing sound was David A. Wheeler flushing Ken Thompson down the drain.

If today's phones had to put up with the web of eight years ago, that'd be one thing. But eight years ago, you didn't expect your desktop to render the CSS3, AJAX, and social widget filled monstrosities that are 2013 web sites. Eight years ago, webmasters expected some of their PC viewers to be on dial-up and their few (if any) phone users to be on something like WAP. This meant the average download size of all items on a web page was far smaller than it is today.

How many different compilers did you use? Did you try any cross-compilers, such as compilers on Linux/ARM that target Windows/x86 or vice versa?

See bunratty's comment.

See replies to bunratty's comment.

If you've compiled the compiler with competitors' compilers (try saying that ten times fast), you should be fairly safe from Trusting Trust.