Spot on; I had a rant / post about this back in 2009 (that I had drafted years earlier)... hoping Apple would take over this market:
http://tronsterhartley.blogspot.com/2009/01/starting-to-clean-out-my-many-drafts-of.html

While it doesn't specifically have to be Apple, it seems that none of the established brands really understand what consumers need in a great car stereo. The Alpine model I mention in the above post included: a remote? Required holding a button for a few seconds to active a feature... in a car Has no way to fast scroll mp3 artists or songs, etc....

The only reason I settled on it was because it could connect to my iPod and play MP3s without a skip between the track. This was after calling up another manufacturer about their models of MP3 playing stereos and being told that gapless playback was "impossible". Thank you business man; you know jack about tech, but it doesn't matter because your company doesn't make a car stereo with a killer feature I need. (Although I could change the color of buttons; which was fun for about 1 day and I haven't touched since.)

I hate Apple's lock-in but vote for their products with my money because they really do care about design beyond what is in a device. It makes all the difference in the world when you have a product that "feels" right. Check out the Nest Thermostat, or Dyson Vacuums to see other companies who also match form and functionality.

I've witnessed writing documentation / seudo lines of code in comments on what a section is suppose to do is a quick way to ensure all pieces come together; frequently able to leave those comments afterwards to describe the following 1-N lines below it.

On the flip side, writing documentation after code can indeed point out bugs if the code is scanned as the documentation is written; it's not unlike a form of Rubber Duck Debugging https://en.wikipedia.org/wiki/Rubber_duck_debugging .

In the end, the only glaring weakness is rewriting the (more minuet) documentation when refactoring the code it's describing. But I'd argue the extra time it takes to rewrite the documentation is, again, Rubber Duck Debugging the refactored code.... a good thing.

Actually the water pressure for the (hot water in the) showers has increased since the tankless system. It wasn't awful with the old one, but one could tell the difference if two people were taking showers at once. Now you cannot tell the difference. I don't interact with my house's water system any differently before; nor was I given instructions to.

The only limitation has been a slightly longer time for the hot water to start coming out.

I had mine installed last year (4/13/2011) because my traditional water heater was cracking and had started a leak. The plumber recommended it; said while they are relatively new to (residential) US, they have been used for awhile in Europe. I did do-diligence with Google and had it put in. The brand is: Noritz ( http://www.noritz.com/ )

So 1 year past its running well; if there is a follow up thread 4+ years down the road, I'll let you know how it's handling.

I haven't had a cold water sandwich effect. Only drawback is that it takes about 25 seconds for hot water to start coming out of the faucet (vs 10 seconds with the tank). Advantages:
- Mounted on wall (above washer/dryer) in basement; just gained about 3'x3' space back where my old huge tank was sitting
- I have seen a lower gas/electric bill since installed
- Should I choose; I can take a ridiculously long hot shower (of course always doing this would negate energy savings)

Two items I can recommend that cost a bit upfront but do indeed save money down the road:
- Nest Thermostat ( http://www.nest.com/ )
- Tankless water heater

A good tankless water heater will cost a few K (with installation, etc...) so perhaps just start with the Nest. There is currently a waiting list for them, but I was able to get mine about 3 months after waiting. It looks cool, and if used properly, will continually save you money over the life of the house.

I did listen to the full retraction, the dust incident is true and confirmed. Michael Daisey did not experience that on his trip. Is that a sign of poor factory conditions? Yes. Did the factories he visit have those issues? From the official reports it seems unlikely, beyond those we'll never know for sure because the bulk of Mr. Daisey's observation were lies; including the new lies NPR brought to light based on his first responses.

It's a shame because it would be great to hear a first hand account from a credible source. There are some good pro and con observations on the overall state of factory conditions (not just Apple factories) and overtime for workers at the end of the full retraction.