The countries as a whole may be the richest ones, but if you look at how those riches are distributed within those countries... most people in those kind tend to be worse off than the other kind.
But the rich will not recognize that until the mobs with pitchforks are breaking into their gated communities.
It only needs to happen in one place for others to recognize the urgency. Just like the communist revolution in the USSR prompted the rise of the welfare state in the West (and, with the collapse of the USSR, welfare state is also slowly evaporating).
That might not work out so well when it's proles building those robots.
So you can actually shoot them and hit? Sounds like a win-win!
This is subjective. But it certainly goes beyond "remembering whether to capitalize the first character of your methods and variables", at least if we're talking about idiomatic C# vs Java.
Granted, Java is catching up with lambdas and the associated library stuff in Java 8. But it is still hampered by type erasure, and libraries haven't picked up on their use yet, while in C# the patterns that only really make sense with lambdas have been idiomatic in libraries for a few years now.
This was true circa Java 1.4 / C# 1.0. Since then they've got rather different model for generics, lambdas, and a bunch of other stuff. C# has LINQ, dynamic and iterators on top of that. There are enough differences to matter.
Did you count the jobs that only listed C# or VB.NET in the
Perf of JVM vs CLR is a complicated topic. Generally speaking, JVM (HotSpot, specifically) has an edge when it comes to optimizing code, but CLR has an edge in that some of the language semantics generate more efficient code to begin with. User-defined value types (structs) and non-type-erased generics thereof make a big difference there.
HotSpot is better at optimization because it can afford to be slower - it can interpret the bytecode for rare code paths, and only kick in the full-fledged optimizer after it figures out that something is worth optimizing. CLR doesn't have a bytecode interpreter at all, it always JIT-compiles on first call - which means that the compiler has to be fast enough, and that in turn means shedding slow but effective optimizations.
10 years ago
Enterprises usually don't start using a new tech extensively until it has been out for a while.
Did you have the same indignation about the similarly authoritarian and brutal but non-communist regime that was in place in Cuba before Castro?
You know, the one that was not only tolerated, but actively supported by US?
If they do win, it will set a nice precedent for the Gun control states to force the neighboring lax gun control laws to clean up their act.
It will also set a nice precedent for anti-abortion states to force the neighboring lax abortion laws states to "clean up their act".
And it will set a nice precedent for states that ban gay marriage to force the neighboring states that have gay marriage to "clean up their act".
Careful what you wish for. You might just get it.
I used the phrase "thinkers", not "elites". Those groups I "give credit" to are huge. I don't hesitate for a moment that there are members of those groups who have the intelligence at hand and the foresight to see where things are going and to prepare for them. Lumping everyone in those groups as either/or doesn't make sense.
Regardless, you still give them way, way too much credit.
StartSSL.com is always over capacity, it's not possible to get anything.
Give me one free certification provider that doesn't require installing anything on the user's side.
- Cleanly separate content and presentation.
- Provide easy-to-edit templates.
- Allows all of the content to be stored in a VCS.
- Generates entirely static content, so none of its code is in the TCB for the site.
The one thing that it doesn't provide is a comment system, but I'd be quite happy for that to be provided by a separate package if I need one. In particular, it means that even if the comment system is hacked, it won't have access to the source for the site so it's easy to restore.