Seriously Slashdot, you may be good at math, but you suck at accounting.
And accountants are ruining things. Passing that fraction of a cent on to the passengers is not going to change anything. I'm all for saving weight on planes, but 18 pounds (out of how many hundred thousand?) for safer battery seems obvious if you've looked into the hazards with batteries. This is why artificial sweeteners are all the rage. If it's 100 times sweeter than sugar you can but 10 pounds instead of 1000 pounds - a win even and 10x the price. When you're willing to multiply a tiny percentage savings by large volumes and claim thousands or millions of dollars in savings you should stop and ask yourself - am I that close to going out of business? If so, you've got other problems.
That said, I have no doubt Boeing will sort the problems and normal service will be resumed shortly.
You are an optimist. The auto industry has been learning the lessons of high energy-density batteries for a long time now and you still see news about some issues in unusual circumstances. If they can pin these incidents on a single specific flaw that has a fairly simple remedy they could be flying by February. Maybe. IMHO. For example, someone suggested they are charging too fast - that may be fairly simple to fix at the expense of charging time, but it would get them back in the air. If it turns out to be something structural (hard landing causing physical damage to cells) it could be quite a while, though there might be some quick fixes you may not like - put foam rubber under that box! Time will tell both what the issue is and when they fly again.
They used to predict in the 50s that in the future a man would be able to easily support himself while only working two days a week.
Lots of people do this today. The sad thing is they make them show up to the office 5 days a week.
"I have an idea for an app" is exactly what riles up programmers. Ideas are a dime a dozen. If you, the "nontechnical person", do your job right, then you'll find a competent and cooperative programmer.
GOOD ideas are NOT a dime a dozen. If they were, every programmer would have a successful business simply by implementing their own good ideas. I've been programming for decades and have a couple ideas I think are really good. One has been described as a "billion dollar idea" by a friend of mine. We don't have the type of experience necessary to bring it to life on our own (without huge learning). We do embedded software and the idea is web/network/mobile. Another neat idea I've got could be put together by a competent Android programmer in a week or two - again, I haven't tried 'droid and when I have looked at Java it made me cringe. This one seems less likely to be a blockbuster, but the risk/reward is still good 'cause it should be relatively easy.
So what do you propose I do? My best bet is probably to bite the bullet and learn Android programming on the simple app. That would then provide some experience for the mobile part of the other. Or should I hire an Android programmer for the simple app? And would they be an asshole because all I'd provide is the "idea" while they write the code for a price?
With a theme park, at least, you can also choose to avoid the place entirely
Yeah, but when you're already booked and just spent 2 days driving 1200 miles to get there, already checked in and spent one night at a resort, then show up at a theme park where they ask you to stick a finger in a scanner.... That's not really the time to opt-out. Thanks Disney World.
I've looked at the listing, and it's right! -- Joel Halpern