Or, you know, they could build offices in cities with free capacity.

And yet, I am not amazed that in your world, straw man arguments are considered valid. I must not be new here.

Unfortunately, the very same thing happens in proprietary software. And "isn't supposed to happen" is a misunderstanding. It's just supposed to happen less, and it's supposed to get fixed easier. The latter, at least, has been proven out.

Given how simple USB wiring is, that's trivial to fix. Get a nice buck converter for a few bucks on eBay, and wire in a USB power injection cable.

That's what I put in my truck. You can't listen to optical media in it unless you have a heavy load, because the suspension is too hard. So I have a $20 amplifier with stereo in and four outputs.

Yes, if I had perfect foresight instead of excellent hindsight, I'd have kept my 1960 Dodge. It got over 20 mpg on the freeway and it was stupid simple. But I didn't know how to rebuild a brake system then (dirt simple, as it turns out) and so I couldn't afford to keep it.

It's more reliable. Bluetooth Audio is miserably finicky. The only thing that ever worked right with my JVC was AT&T Fuze. With a couple different Android devices now including the Nexus 4 I get occasional skips. I used to use an Xperia Play, that skipped a lot. Flawless using the headphone cable in my truck instead.

I'm going to try adding bluetooth to my car anyway, switching into the line inputs from the changer with an audio signal relay, and using an ultra-cheap receiver. but i'm also going to have line in, just in case.

So there was a bug in OpenSSL. Big bug, yes, but that's not the reason it was (and still is!) a big problem.

The genesis of the big problem is one of monoculture, not only of OpenSSL being the dominant SSL implementation, but probably more importantly, the fact that pretty much all Internet security that is accessible and matters to ordinary users is SSL/TLS in the first place.

If you think this is bad, imagine what happens if the fundamantals of SSL itself are compromised: What would we replace it with? How, considering this is effectively the only secure connection technology available across all common OSes and embedded devices? How long would that take? (Years, at least, I'd wager...)

What we need is more flexible security methods in the first place, and open, standard implementations (like OpenSSL, but growable) that can allow us to proactively extend security methods as the net matures, and *quickly* address bug-based vulnerabilities when that approach fails. (Note that this may require the implementation of some kind of standard "secuirity code VM", so new code and new methods can be easily distributed even to older systems that may not be fully supported anymore. And no, I'm not glossing over things like limits on code space, memory, and the like, nothing will allow every system to be upgraded, but we do need some way to allow and authenticate that (while preventing bad guys, including governments, from using the mechanism to create weaknesses.))

Closed source is not inherently safer. Raymond's proposition is theoretically sound, however in actual practice, the NSA has "many eyes"...

Turn on your Heartbleed,
Let it shine, wherever you go
Let it make a happy glow
For the NSA to see...

They are by Obama's $200,000/year income definition. Or is that $150,000 by now? I forget.

Besides, "wealthier" is comparative, not an absolute term. You are wealthier than a guy who lives in a cardboard box in an alley.

Ronald Reagan's administration drove the creation of the simplified forms, and AS THE SUMMARY EVEN NOTES, he supported ELIMINATING THE RETURNS ALTOGETHER.

RONALD REAGAN. You know, mortal enemy of the left.

Who's the moron who modded this up?

Just wait, the city will start to tax you for evaporation for water released into the outside world...