sprout

Hypocrisy isn't a crime, but it can invalidate a claim if you publicly state one interpretation of law and later state another.

But I don't know, maybe HN really is that gullible when it comes to governmental malfeasance.

I can think of other situations, for example highway driving, where going 80mph in a 65mph zone probably has an only minor effect compared to going 65mph, and depending on traffic could be safer.

Gives 1538 Calories per pound of whole wheat flour.

According to these folks an acre of wheat yields 42 bushels: http://www.wheatfoods.org/AboutWheat-wheat-facts/Index.htm

At 60 pounds/bushel that gives you 2520 lbs. * 1538 Calories = 3875760 Calories / acre / year. We'll divide by two to assume you're mixing wheat with some foods that are a little less calorically dense, because you'll want at least some green leafy veggies and beans for iron and protein, and that gives us 1937880 Calories per acre per year, divided by 365 days in a year yields 5309 Calories per acre per day.

So, back to the original point, it looks like you can easily power a human using half an acre of land and photosynthesis. Possibly one quarter of an acre if you're willing to live on bread alone. (Whole grain being not so unhealthy as white.)

I've never really had problems with HostGator or asmallorange. HostGator can be slow, but it's good value for the price, and pretty clean cpanel interface on the whole. ASO has good support and seems pretty snappy. (Of course I'm using an absurd amount of disk space on HostGator, mostly for backups.)

The biggest thing with 1and1 is what a huge mess their administrative interface is. Almost half of the space is ads trying to upsell you to their other services. You would think as a paying customer they could leave me alone.

Or any pushed through with NCLB, to my knowledge.

90% of office workers would benefit from the ability to write an Excel Macro. I don't even think that's a hard sell. Any businessman who understands what Excel does would understand that.

Of course, long term Excel is a toy, and there are all sorts of benefits to be had from more general tools like Python.

Facebook unveils roughly 8 anti-patterns with every re-do and rolls back the most egregious 4. The result is Facebook get significantly worse with every iteration.

Most of the recent ones though, I've solved with NoScript and only browsing Facebook in a dedicated browser. (I really need to make something a little more robust; effectively a Facebook app running on a Webkit core that opens all external links in Firefox. That would sandbox the social graph, and let me read links out of Facebook normally.)

Really, there's nothing wrong with them having sex - just so their partners are aware of the risk.

People will whine and moan about the privacy concerns, but when it comes right down to it people with untreated or untreatable STIs should not be having sex (and if they are their partners should be made aware.)

Facebook's introduction of 2000px wide images (close to the output of most consumer cameras) makes this all the more important. If Facebook's letting people upload directly from their cameras to the site with no scaling, the format the camera uses is a big deal.

Also, Facebook is a very large portion of photos shared over the web.

My boss' Vostro was inexplicably hanging on logout/login, that seems to have corrected itself after a few forced reboots. (And I've had that experience a few times on all OS's, including OS X.) Actually, I can't remember it for Linux, but Ubuntu is much less careful about shutting down gracefully than Mac/Windows.

What exactly is being argued for if not that prescriptions should be allowed even when efficacy is unsure?

So anything released today is of necessity in it for the long haul. That said, maybe releasing a spec today from one player isn't the way to go. Google should be talking with Microsoft, Apple, and their hardware partners to look at next-generation technology they can put out, unencumbered by any patents and figure out a 3-year timetable after which they will have the format ready for use in cameras and phones. At the hardware level where the data is encoded off the CCD. Partnering with Flickr, Facebook, etc. they could make sure that these phones and cameras with next-gen encoders work out of the box, on the web.

The biggest way is they don't want to make it easy for you to get your data out of Facebook. Any robust, well-documented API would have to enable that.

In some ways this is even a good thing. A small number of compromised accounts can give access to most of the data on Facebook.