That's because you stuck to the rules. I once played it with a couple other, ahem, more creative players that turned it into an awesomely funny haggle game, by more or less inserting a "trading" round at the end of each turn in which they would offer money+estates for other player's assets that would offer them a strategic advantage. The face value of the offer would more often than not exceed the price of the haggled item. It was out-of-the-box, emotional and very entertaining.

You got everything right but ignored the fact that they ask for longer hours because they are paid peanuts. Since asking for a raise will get them sacked, all that is left for them to do is to enslave themselves to the enthroned employers.

Maybe they are better off working in a factory than in agriculture, but we shouldn't pretend we give them the freedom to decide for themselves what is best for them when we are pretty much holding a knife to their throats.

You might want to reconsider Jim Carrey. The Truman Show, Man On The Moon and Eternal Sunshine Of The Spottless Mind are quite good movies.

This happens in Germany as well. When we applied for a government grant we had to present a detailed project plan and describe the "deliverables" in ridiculous detail. The people in the review committee weren't idiots, they knew that the plan was bullocks, but you had to include it anyway. Back then I attributed the whole thing to the german obsession with planning.

I think you are rather confused with the meaning behind EEE.

The EEE strategy of MS was harmful, because MS used its monopoly to screw up widely used open standards, thus eliminating competition at birth. This was bad not only for startups, but for consumers as well. Remember IE6?

As the article that you linked to yourself describes, there are a lot of Android versions that are based on the open source version of the OS. Google is actually giving its competitors the Android code for free, thus enabling them to enter the market, rather than shutting them out of it. Lack of other Google services is actually a feature in many of these cases (like in Chinese implementations). If you weren't allowed to use Google as a search engine in such competitor Android implementations (as if, for example, by means of a malicious code license) then *that* would be EEE, because Google would be using its search monopoly as leverage to prevent a competitor from entering the mobile OS market (as in Embrace the mobile OS technology by open-sourcing Android, Extend it with the Google search feature, and Extinguish it by showing everyone how lame those other Android phones are that don't have the Google search feature). As far as I know, this is not the case. You can even get the closed-source Google apps to play on a Kindle Fire, for example. There is definitely some bad karma created at Google for abandoning the open-source projects, but this is not a case of EEE. And on the other hand, who said that Google was obliged to invest into the open-source projects indefinitely? I'm not familiar with the exact license of each piece of Android code, but, in general, once it has been open-sourced the community will decide when it's time for the software to die. If Google stops development of an open-source app and the app dies, then it is *our fault* for not picking up where Google left off.

Don't get me wrong, I'm not a Google fanboy or anything, but the EEE technique that MS pioneered is *very* harmful and evil. We have to make sure we don't cry "wolf" at every sign that might resemble it, even if open-source fans (like me) have to come to the defense of a multibillion corporation like Google. Otherwise we will get no reaction when shit does in fact hit the fan, like we had with the OOXML fiasco.

Humans will be necessary to make new machines and repair those that break down. Administration, supervision and similar tasks will create jobs. Also, the work that is left for humans to do can always be spread out to more humans, so that everyone works part-time. Instead of having 10% of the humans work full-time and the rest just sitting around, you can distribute that work to all humans and have them work only 10% of their time.

We'll make our own DNS!

With blackjack and hookers!

Wikimedia Commons comes close to the archive model you are describing. The very small amount of video meterial there is only an example of how carefull one has to be with copyright these days and how hard it is to get your hands on decent quality footage whose copyright has expired.

That's a pity, because chemical engineers usually leave the actual chemistry to the chemists. Chemical engineering is more about process design, process control, upscaling and debottlenecking. You mostly get the chemical process outlaid by the chemists and you "only" have to worry about everything around it. We have started to dabble with material design, but you can be a good chemical engineer without a profound understanding of chemistry. Chemistry is mostly about the basic "what" and "how" whereas chemical engineering is about "how fast" and "how much".

I'm an idiot with a pencil and I don't even know where to start!

I just knew that the Jocker was behind all this! It's about time we locked him back in Arkham and threw away the key!

Oh, wait...

http://tech.slashdot.org/comme...

care to comment?

If you had any balls you would install Hurd instead...

N00b...

It was present in XP (and probably even in Win98, but my memory may be playing tricks again), it just worked differently. You had to open two windows and select both of them with the mouse on the taskbar while holding ctrl pressed and then right click on any of them and choose "arrange side-by-side" or something like that.

Correct. The fact that the document was once in a letter does not make it private. As soon as the government does not snoop in the mails/emails while in transit, everything is fair game once it has reached its destination.