Again, it's not guaranteed, but Airs are rather more at risk than other laptops because of their construction.
use http://www.macupdate.com/app/mac/23049/smcfancontrol - when the thing gets hot, just increase the fan speed (to 5700 rpm or whatever you machine's max is) for a minute or two, and then everything gets back to normal.
One glass of water on the desk (not in the machine!). Capillary action sucked water around the seal on the base. It was turned over to remove the battery and the sucked up water rained on the logic board resulting in all sorts of crackling, smoke etc and one dead MacBook.
Being a qualified and experienced EE, I'm qualified to say that it's electronics 101 to be able to isolate power (like every other vendor allows).
After breaking my second laptop with fluids (first was ruined with coffee; second with it standing in water, which was rain accumulated in my not properly closed "watertight" bag) I started buying Thinkpads. They have specially designed "Fluid drains". Because all laptop manufacturors know that spills are one of the highest death-causes for laptops. http://youtu.be/d7cvi00OZDM
But as always, you shouldn't place your drinks directly to all kind of electronic stuff. It's common sense.
However, there is no excuse not to design something with safety in mind.
If you look at the base, the edge rim of it is where it seeped in and sat in the curved section like a pool when oriented normally. There was at least 10ml of water which had been sucked off the table via that rim. The logical step is "isolate power". Any movement of the device resulted in the water spilling onto the logic board.
Pictures: http://www.ifixit.com/Guide/Installing-MacBook-Pro-13-Inch-U...
Now TBH I've personally done this with an acer timeline. I yanked the battery out in 5 seconds flat and hung it up to dry. It was fine the next day.
The Powerbook 5300 was recalled because some batteries caught fire on the assembly line. (1995)
The batteries, manufactured by LG Chem Ltd. of South Korea, could overheat and pose a fire hazard, according to the CPSC. The recall affects laptops sold since January, which contain batteries produced last December. Approximately 28,000 batteries are affected by the recall. (2004)
Apple Computer Inc. on Thursday recalled 1.8 million Sony-built notebook batteries that could overheat and catch fire. (2006)
Maybe I didn't provide references. Here's the references, most with the official statement from the U.S. Consumer Product Safety Commission.
The powerbook 5300 was explicitly recalled, by Apple, for the short-circuit problem. Reference:
http://www.nytimes.com/2001/03/15/technology/laptop-batterie...
http://news.cnet.com/Apple-woes-continue/2100-1001_3-211692....
http://books.google.com/books?id=R7zgbMJM3vwC&pg=PA10...
2004 recall, same problem:
http://www.cpsc.gov/cpscpub/prerel/prhtml04/04201.html (Problem: An internal short can cause the battery cells to overheat, posing a fire hazard to consumers.)
2005 recall, same problem:
http://www.cpsc.gov/cpscpub/prerel/prhtml05/05179.html (Hazard: An internal short can cause the battery cells to overheat, posing a fire hazard to consumers.)
2006 recall, related problem:
http://www.cpsc.gov/cpscpub/prerel/prhtml06/06245.html
http://www.seattlepi.com/business/article/Fire-threat-spurs-...
http://www.macworld.com/article/52084/2006/07/recall.html
This is precisely what he asked for, and now I've included references. But really, if you guys don't value facts, research, and actual answers, then to hell with it. Why do I try? Might as well hang out on Digg.
So presumably I'm so lucky I ought to be winning the lottery at least once a week.
Yes you are lucky because you spilled from the top which it's obviously at least slightly better at handling. If the base gets even slightly wet, boom.
Right. No hyperbole.
But what you said before is that the notebook in your story was sitting in a puddle of water, 10ml seeped in, and then when you turned it over, you heard "crackling, smoke, etc."
An electrical short, yes. But not an explosion.
Sure, if the cathode comes into contact with water, that's a big problem. But the battery itself is well sealed. Your criticism seems to be half baked here:
When you say their design is "dangerous" that sounds like you're saying its dangerous to the user. That it will cause injury.
But your real criticism is that you can't "isolate the power." That is, the sealed case makes the battery dangerous to the machine: You turned the machine over, and logic boards, still hot with power, shorted when the water hit them.
But the implication that it's dangerous to consumers just doesn't make sense: Removable or not, if the lithium comes into contact with water, you've got a problem.
Moreover, I think it's disingenuous when you pull the "I'm an expert" card and then provide editorial analysis: Of course if you google you'll see the bad "unlucky" macbooks that got wet. The people who are "lucky" do not post pictures of a pristine, dried-out computer. There's a selection bias there.
http://www.youtube.com/watch?v=yGBoJjfMuAk
Did you use a different way under SunOS4 ? it seems a lot of boilerplate on the video (apple bias I guess)
As per everyone else back then, we wrote pretty much everything in Perl and occasionally C when Perl hit a bottleneck. GUIs were built in Tk, not in OpenLook. Still far easier and quicker than IB on XCode.
TBH it took as long as it takes in Visual Studio now, which says exactly what little progress the world has made in the last 15 years.
I agree with the build quality - they are good quality as in good materials and good fit. However, with my EE cap on, the designs themselves are bad and are quite dangerous. When there is literally that amount of LiPoly cells sitting inside a chassis, you want to be able to isolate the power. One bit of water in it and it's effectively an incendiary device. I've seen one recent MacBook Pro (pre-thunderbolt) go up with my own eyes quite spectacularly and wouldn't want something you can't drop the cells out of rapidly if you inevitably pour your coffee in it.
With regards to the software, I found the OSX environment inconsistent and XCode absolutely terrible. The OSX environment is inconsistent from the "task focused" application designs that you see. Every shipped application has its own set of behaviours and pretty much ignores a common standard resulting in head scratching. The keyboard shortcuts system is horrid and doing anything without the trackpad is hard work. XCode was just a mismash of concepts thrown together badly. As a comparison point, Visual Studio is a lot more mature and consistent and that is saying something.
The whole Apple/OSX ecosystem is a good attempt but it's not good enough for the money on the basis that some of the fundamentals are flawed. I'd actually throw more money behind Microsoft at the moment as they are heading in what I percieve to be the right direction. Apple started at a good point and have got worse. Microsoft started at a bad point and are getting better.
TBH however, the best OS/hardware ecosystem I've come across so far was SunOS4 and Sun4 architecture in the early 90s.