What's your evidence of this? Very curious.

Never heard of it. But no arguments from me for dropping 32 bit support. I kind of wished microsoft did that starting with windows 8 or earlier.

I'm trying to figure out if they proved that P != BQP (Bounded-error Quantum Polynomial Time)- the article is light on technical details...

NYSE owns a large share of coinbase already, actually.

Well I'll be damned... https://searchcode.com/codesea...

if (confused == true); killAllHumans(); // ^^ the bug which killed humanity

What about functional programmers?

Yeah I couldn't help think of FF or chrono trigger, or maybe the futurama episode with chronotons.

I don't think your break down is what this is really about, although perhaps I'm misunderstanding you. There are few concepts (cough...) at play here. One is whether the language itself supports a notion of duck typing or not. Java generally doesn't. You must explicitly implement an interface to adhere to it, and even if your class has methods which do implement it, the compiler still will generate an error or the runtime a class cast exceptions if you attempt to treat it as the desired interface.

If you were to implement concepts in java, I imagine it would have to be permitting a cast as mentioned above by the compiler, rather than treating the types as different. Note that both interfaces and concepts have same compositional power, except that concepts end up being more flexible, as you are generally only enforcing the type in the scope of a particular algorithm, not a class, even if many classes end up supporting the concept.

Back to C++ land. Templates in C++ incidentally fit into a duck typing oriented model, *unlike* Java. Thus, concepts almost existed to provide order to somewhat unwieldy compiler errors from the template system and provide explicit design clarity for those implicit utilizing concepts previously.

Finally, IMHO, modules (and module signatures) implement the idea of concepts quite elegantly (eg. in OCaml).

who still loves KDE and thinks this is great news?

I actually like ML style: "let foo = bar in zed".

I agree that curly braced languages should stay as curly braced languages, but it's myopic to assume it's the only choice for scoping when designing a new one.

In any event, you're right that what is broken about GO is not really the scoping mechanisms.

Except that android's audio api keeps going through drastic changes and/or deprecations. Quite annoying as I maintain a music visualizer which needs to sniff the audio signal.

C is still the most portable language in the universe. The only real language that works on all phones, in particuarl (ok, C++ does too but C is where you get all the amazing well written, optimized libraries you'd want on most devices).