Again, nvidia don't have the console market today, AMD have it, so if game developers will use MANTLE in the consoles, the PC market should follow.
If the performance is as claimed, game developers will for sure try to use it, specially if its supported in all systems the same (all consoles, windows, mac, linux)

Don't forget that all new consoles today are using AMD cards, so the game developers are using mantle for those, they would also can do that to PC with little change

1- i don't imagine how the video card drivers can affect a browser, can't MS blacklist that driver? does everyone have this problem?
2- why use IE?
3- why even use windows!?

call it whatever you want... CISC AND RISC? can be also small-CISC AND small-CISC and small-CISC AND small-CISC... but that start to translate to a plain RISC

If you would take out that translation layer and use all available micro-ops, you would call that CPU a RISC like, not a CISC like... Even if sometime you can only execute one operation, other times you CAN execute several operations, being further way from a CISC design and close to a RISC design.

anyway, that layer takes out performance, consume resources and really not needed if you change architecture... so going away saved money

You are also forgetting that a x86 or a amd64 is a RISC cpu with a layer od CISC hidding the RISC. That layer takes cpu space, power and resources (both designing and working). Going to a simples CPU design saves silicon wafers, increasing the number of cpu per wafers and so increasing the profit. Also, a simpler cpu saved internal resources developing the cpu.

So AMD building ARM cpus is a way to reduce costs, increase potential profit per cpu and of course, being ready and testing the market demand for ARM CPUs

No, its a river in india... AMD uses river names for APU/CPUs families and GPUs are islands (where the type and location of the island is used as family grouping)

and the graphic card is free for you?

the divisibility of bitcoins is set on the current version of the protocol and can be increased any time with a update version. the protocol already had several updates, one of then a mandatory update to solve a large block fork issue

You can choose to save the wifi for the system (and so not saved in user kwallet) or for user (stored in the user kwallet)... so you can choose what fits tou best

to understand kwallet think that you store your credit card in it and you have your computer on a public place. The login is just the first way to protect you, even if someone can see your password, to use your CC, you still have to lose your kwallet password, that is only rarely used an so harder to be stolen. It's the samething for firefox master password, kiskis, keepass(x) or the apple keychain... another layer to protect your passwords.

If do not want to have 2 layers of security, just set a empty password for kwallet.

because you should have multiple levels of security...
the password for login should be different from the kwallet... and you should even use several kwallets, one for websites, other for local access machines, vpn or more secured data (bank info and other logins).

a true wallet will auto-close after some minutes unused and require new auth to open (to prove that you are still the correct owner and not a random user trying to steal some data

it's the same for executing superuser commands... it asks a password as a security layer... you can also disable it if you want, but is very recommended to confirm that you are really allowed to do that

it's up to you, but look at windows and how the the "easy to use" and "do not ask anything, assume it's OK" have broken the security several times and helped hackers and virus to take over the systems.

Remember, there is no "one size fits all" security, but having as much security layers as possible help a little every time

Hitler alone could not do anything...he needed the people support.
German people fall in to the nazi hate talk due to the instability of world crisis and specially by the huge and stupid "war compensation" from WW1. Crisis make people to want to believe on new solutions, specially if the current available ones don't really solve anything... just look at Greece economical crisis and how a both a fascist party and a alternative popular party gained popularity in last elections. Extended crisis and greed are the seeds for wars. Mutual help, support and sharing helps avoid wars. It's up to the people to decide what path they want to follow (what that could do to others).

All Wars are STUPID

There! FIFY

There is always one side that think it is better, it is correct, it have some kind of right. Worst wars happen when both sides think that. Then there is all the lies, illusions and blindness that fuel some kind of hate that didn't existed in the past. Everyone have reasons to both LOVE and HATE the next guy, just press the right buttons to increase one over the other.

+10^32 :)

Use iptables rules in the router to allow/disallow traffic at some hours of day, see this. You can totally block the traffic, or QoS it to oblivion on hot hours and increase it traffic later (join the iptables rules by hours to set the classid and then apply different QoS to then)

Finally, a caching transparent proxy might help, specially if everyone uses the same sites... it helps the normal browsing (by caching images, css, js, etc) and the updates (local copy if already downloaded). You just need a old computer with some HD and you are done.

For harder to filter services, you can usually block DNS for then... but if you allow it for some time, it might be cached by the clients on peak hours and still work.

Of course, if you control the clients, you can also configure most of then to only download off hours

Finally, you can be a BOFH, permit only allowed traffic and block the rest... or redirect it to some backdoor installer and enjoy the chaos generated

I'm not saying that OpenBSD is useless, but that in the cover of security, have many limitation and performance issues that other OS don't have.

For the NIH, is always the same... everyone have one excuse for the NIH and build a new one instead of fixing the existent one... that is why there are so many NIH cases (not limit to OpenBSD, every team with intelligent people think they can always do better than the next guy/team... sometime they do it, sometimes they don't)

Finally, i'm not saying that OpenBSD don't do useful things, they do and others should use then too!! what i'm saying is that OpenBSD have people that understand security, yet they very rarely help other with their security problems. They only bash other developers and apps and point how superior OpenBSD is... but this don't help solve the problem. For many of then. the world outside OpenBSD simply doesn't exists.