Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment: Re:Revolution (Score 1) 452

by shutdown -p now (#48645553) Attached to: What Happens To Society When Robots Replace Workers?

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).

Comment: Re:Why bother? (Score 1) 231

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.

Comment: Re:Why bother? (Score 3) 231

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.

Of late, .NET Native is an interesting piece of tech that precompiles .NET apps using VC++ compiler backend. So you get all optimizations in your .NET code that C++ normally gets. Of course, it's still slower due to the more deterministic but less memory-friendly sequencing and memory model, and all the extra runtime checks, but it's still faster than JIT (and, I strongly suspect, HotSpot, though I don't think anyone has profiled them yet).

Comment: Re:Hope they win this case. (Score 1) 464

by shutdown -p now (#48640635) Attached to: Colorado Sued By Neighboring States Over Legal Pot

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.

Comment: Re:PRIVATE encryption of everything just became... (Score 1) 379

if everyone does this

That is the weak point of the plan. We haven't even managed to get everyone to do email encryption, even though the standards and the easy-to-use tools have been there for almost two decades now. What makes you think you can switch them to a P2P darknet?

I think that a more realistic scenario will be 1% doing what you describe, and 99% being utterly clueless.

The tree of research must from time to time be refreshed with the blood of bean counters. -- Alan Kay

Working...