Well, we sure didn't get into it to write boring business applications except a few in the dotcom years who quickly moved on when it went bust. As I remember it though, there were many who just wanted to play games and only a few who wanted work with code and I don't think pushing them to play more would have brought them over. Of course you needed the opportunity, but there are a lot of games that are mod-friendly if you're so inclined. I'd sure encourage and test if tweaking a game peeks their interest, but if it doesn't I wouldn't try with more game time.

It that was true, how do you account for other countries with far less then half the number of criminals per citizen as usa?

Missing codecs: AAC, H.264, MP3
Missing plug-in: flash

So either patents or not their code, if you got a good solution for that I'm sure Google would like to hear it.

I don't think you have to come up with that many conspiracy theories, Mozilla's "problem" is that they won. They broke Microsoft's monopoly, made HTML/CSS properly standardized and together with KHTML/WebKit/Blink some 80% use an open source renderer though many use it in a closed source binary. Microsoft would be laughed at if they tried any new proprietary extensions and for the rest the implementation details are all in the open.

Their problem can be summed up in two words: "Now what?" and it turns out they didn't really have any other goal in common than slaying the dragon and now the dragon's dead. Some UX designers get to make an art project. Some cowboy coders thinks more releases is better. Some will do anything to get away from the reliance on their biggest competitor. Some security nuts get to go overboard. Some want to go after Android/Chrome OS with Firefox OS, but this time they're not competing against proprietary and neglected shovelware and barking up a tree Ubuntu has made essentially no progress on.

Let's face it, Mozilla mainly won because Microsoft was trying to keep the web from competing with local applications so they could sell Windows licenses, they got to the head of the pack and grinded it to a halt. They didn't want to compete, they wanted to put a spanner in the works for as long as possible. It annoyed many and gave Firefox enormous amounts of goodwill even when it didn't work properly, out of spite for Microsoft people kept using it and pushing for sites to support it. They don't have a clue on how to compete with someone that puts up a fight, which is their second biggest problem.

Isn't that argument a bit like "I plan to live forever, so far so good"? After all, if it did wipe out all life well then we'd be dead so obviously it hasn't happened yet. Some large extinction event seem to happen once every 50-100 million years, what does a once in a billion year event look like? Ceres, the biggest object in the asteroid belt is about a million times bigger (10^20 kg vs 10^14 kg) than the dino killer. That one isn't going anywhere, but there's clearly quite a few potential total extinction candidates if they came to intersect with Earth's orbit.

Excessive hyperbole is silly, yes...

Global warming is a sloooooooooooooooooow process and even if you burned every bit of coal and oil you wouldn't make Canada into Sahara, it's hardly an extinction level event. A modern day pandemic could presumably kill millions, but it's hardly an existential threat to the human race. Same goes for total thermonuclear war, there's be a lot of direct deaths and many more indirects deads from nuclear winter and starvation but not enough to wipe us out.

Tsar Bomba (most powerful nuke): 50 MT
Chicxulub asteroid (dino killer): 100,000,000 MT

We're not even remotely in the same league. The odds are small that it happens tomorrow but in terms of "worst case" asteroids have everything us humans can come up with beat by far.

This. It seems sexual preferences, age and location is rather essential for the service they provide and email, well how else are they going to notify you that someone has taken an interest in you or that you got a reply? You can't ask a doctor to not work with medical data, there's of course good and poor security but at the end of the day if there's a total system compromise you're screwed.

Best practice seems to be as follows:
1. Public facing server makes web service call to locked down proxy server.
2. Proxy server validates every request thoroughly, everything that looks even remotely funny is rejected.
3. Proxy server queries stored procedure in locked down database, no SELECT * for you.
4. The results are serialized back to XML and sent to the public facing server for display.

A lot of work if you want to do it right, but you get a fairly good barrier to a total breach from the outside. Of course they could compromise your web server and start harvesting data, but you should have some sort of tripwire system for that with audits and logs checking for abnormal activity.

The other way in is of course from your network, if they can compromise someone on the inside with database access or developers to plant vulnerabilities that'll go into the production system. But that's usually a much tougher route and really no different from breaking into any other secure network.

If that were the case, the mountains would actually need to displace less of the heavier mantel material than they otherwise would (because part of the load would be absorbed by the crust around), so a hypothetical observer standing on a mountain would still observe more mass beneath him than his colleague standing in a plain.

The only way it could work is if actually the plains were "supported" by the mountains rather than the other way round, but that somehow sounds unlikely...

So, in a way, it would behave light an iceberg floating on water. However, what I don't get is why there's less mass beneath, rather than equal amount. Indeed Archimedes stated:

Formally, you could be right. Informally, both the team leader and manager hat usually end up on the same person, even if he lacks one title or the other. If you haven't got a team lead it's pretty obvious, if you do have a team lead then in my experience the manager does the HR/administrative bits and leave the actual work management to the team lead or the project manager if you work on a project.

For example, with no formal title I basically had the responsibility to:
1) Execute the actual project
2) Delegate as possible to the two juniors
3) Support the two juniors
4) Train the two juniors

Sure, there was a project manager dealing with the contract and formal contact with the client. There was a manager dealing with formal HR bits. But I felt I was a bit project manager, a bit team lead, a bit manager and a bit mentor all at once. It was a constant prioritization between:

1) What must I do to get the project done?
2) What can I delegate to free up my time?
3) What should I delegate to teach them?
4) What should we walk through together?

When you're in practice managing 100% of their time, you get all the hats whether you want to or not.

It's a callback to the original movies, as are the crash zooms onto the faces of people in the cars and so on. It's a stylistic choice.

"... isn't this completely unrelated to what slashdot is about?"

Please don't post comments to stories that don't interest you.

The sociology of technology is something I must deal with every day. It's interesting to me to read stories about that.

Why would you expect toString() to work on a InputStream?

There is no general safe way to create a String from an InputStream, because mapping from a byte stream(Which is what a InputStream is) to a string is not 1:1.

That is: The same string can be encoded as different bytes, depending on the encoding such as UTF-8, UTF-16 iso-8859-1).

The funny thing is that Sun did not think about this when they first created Java, so there are a bunch of deprecated methods which create strings from bytes, trying to guess the encoding or reading in from the systems default locale.