I had compressed memory on a Mac nearly two decades ago in the 7.5.x days with Connectix RAM Doubler. Did OS X just get native compressed memory after Connectix's patents ran out?

As I understand it, that's because bitrate peeling drastically reduced the "analog-like noise" advantage of vector quantization over the more warbly scalar quantization used in MP3. But with several Moore's law doublings of transistor count since the release of Vorbis, reencoding shouldn't be quite as painful anymore.

Then Germany needs to start exporting to the United States and other markets outside the euro zone. The whole USA, roughly comparable in population to the euro zone, shares one dollar; why doesn't it collapse?

Unless the prices rise so sharply that the rise destabilizes governments.

The other markets would buy things and export other things back to us. That's what trade is supposed to be about. Under the Balassa-Samuelson model, the quickest way to increase a currency's value is to ramp up export production. If all were net exporters, on the other hand...

Should oil prices rise and remain high, producers of wind turbines, PV panels, solar thermal collectors, storage batteries, and maintenance services for same can get rich.

Would you prefer to consume everything so that your children have nothing left to consume?

And because Android allows multiple competing web browsers to compete for standards support, it picks up support for these standards sooner than iPhone. Firefox for Android appears to support WebGL as of version 24 according to this table. Safari and Safari wrappers, on the other hand, support standards only once Apple makes the business decision to no longer deliberately exclude them. For example, iOS supports WebGL, but only in iAds approved by Apple. The limits of Safari and Safari wrappers appear calculated to encourage application developers to buy an additional computer and a developer license and develop a native application instead of not buying a Mac, not buying a developer license, and developing a web application instead.

The universe will die of heat death "eventually". To exaggerate slightly less, anyone can make an iPhone "eventually" once copyright in iOS expires. To exaggerate even less, if I eat "eventually", I will die of starvation first. People making applications for the phones that exist now need to eat now. I was referring to the foreseeable future, not 95 years from now.

By the time MultiFinder was made mandatory in System 7, Windows 3 was doing the same cooperative multitasking that Mac OS would continue for nearly the next decade.

So what's the best practice for a web site to use all 116em* of a 1920x1200 monitor's active width without making the main text column wider than the 30-36em** that's best for readability?

* Assuming the default font size of 16px per em, minus 2em for scrollbars and 2em for outer margins.
** Assuming the 80-character line length and just over 2 characters per em.

So that you know the final score the moment it becomes final without spoiling the rest of the game. As far as I can tell, it's OK to DVR it and fast-forward past the downtime and commercials between plays, so long as the viewer has caught up to live by the fourth quarter's two-minute warning.

How, for example, would Capcom have gone about reimagining the Mega Man series for touch?

Nschubach would disagree, citing this list. Even if it is a problem, I would volunteer to be among the first to fix this problem by having my team develop couch-centered PC games. But naysayers on Slashdot keep telling me that even if someone were to make and sell a PC game focused around couch multiplayer, nobody would buy it because nobody is willing to build a second PC for the living room just for one game.

Let me know when people start time-shifting Sunday Night Football or Monday Night Football.

Unless you view DST as a tool used to coordinate work hours with everything else that depends on work hours.