With the 1.1.3 patch included just a new sexy engine.
Especially those of us who got outleveled by their friends.
You have 10 years to cash in on your ideas. You want to screw the whole world over in a fit of selfish "VIEW ME AS THE ARTIST I AM!" tantrum, enjoy your 10 years, but the government should not support you after a decade of your decadence.
The number of people who earn enough money through their patents to be considered decadent is quite small. Patents are supposed to protect people like you, who come up with a great idea, from companies like Microsoft who can steal it and cost-lead your product until you go out of business.
Also, you're living in some sort of fantasy land where you think that all projects can go from early prototypes to final polish release in 10 years. I've worked on projects where the earliest (patented protected) prototype is more than 10 years old, and it's worth hundreds upon hundreds of millions of dollars and your argument is (apparently) "tough shit you should have sold it sooner!"
The real problem with patency isn't that it protects the inventors monopoly. It's that it's possible to patent practically anything, including ideas. Patency should protect the method of creation, not a concept.
Is it just me or isn't that very impressive? If global power consumption continues growing at 7% p/a then in just 50 years we'll the wind power that we're talking about here will be almost tapped out.
Everything that is in a program is stored in memory. Some bits of information must be allocated and stored for a long time. One common error is that programmers forget to free that memory when they no longer need it. The outcome of this is called a memory leak. Garbage collection is basically a process where the demigods of java inspect every group of memory that it can find and checks to see if anything needs it. If nothing is looking at that block of memory it frees that memory for other purposes.
The bonus for programmers is that it simplifies the use of memory dramatically. However, it does this at the cost of speed because some part of Java is going through and checking this memory. A common response is "why don't programmers just clean up there own memory?", well we would, but it's just not that easy to catch all of the memory. Almost all applications that you use today use an event model (e.g. you click the mouse and it fires a mouse event), so it's hard to understand when who what part of the program is responsible for freeing memory. Even worse, many applications have multiple processes running simultaneously with each process responsible for different aspects of the program.
You can tune a piano, but you can't tuna fish. You can tune a filesystem, but you can't tuna fish. -- from the tunefs(8) man page