Because Spain has no choice!
As soon as an EU directive is passed, each member state of the EU has only a set time to implement that directive into local law. Otherwise the parties disadvantaged can sue the government that has not implemented the directive for damages.
EU is not a democracy, but a modern form of aristocratic absolutism!
Why ask someone who isn't even a gamer where the gaming market is?
Because gamers don't reply to me, except to tell me to quit whining about console makers' entry barriers and just accept them.
You want to put a FPS in the Debian repositories? Write a FPS that is compatible with the DFSG and don't expect to get paid for it because that capability just isn't there.
How do I make money from free software if it's in a genre that historically doesn't need the sort of support on which companies like Red Hat build their business?
You make a couple of good points. I completely agree that the slippery slope that Google has to tread carefully on is not one of censorship, but one of liability. Many people seem to think that Google has a moral imperative to objectively reflect the "reality" of the web. They don't. Anyone who feels that Google does or should act in way that is not in their best interest is going to be disappointed.
Google does what they must in each country to remain the dominant search engine. That means abide by local censorship laws, bow to public opinion and avoid becoming liable for search results. Google will always do what will funnel the most money into their coffers but so far they have been very clever to recognize that neutrality and openness can accomplish that goal very well. The debate of "should Google censor results?" hinges on only one criterion: profitability. That goal, in turn, depends on what will preserve the largest possible ad revenue while mitigating liability.
Google is not a public service, it is a publicly traded corporation.
If Microsoft really cared about devs, then the next version of IIS would allow Classic ASP and ASP.NET to share session state.
Nothing like releasing ASP.NET and obsoleting millions of lines of code.
Unlike VB6 to VB.NET there is no migration path from Classic ASP to ASP.NET other than a complete rewrite.
Still no support for foreign keys in partitioned tables. Makes partitioning pretty much worthless in most real world deployments.
"If you can, help others. If you can't, at least don't hurt others." -- the Dalai Lama