threading

Making no promises about timing simply means that threading is either a non concept in the language (see C++ before 11) or the language declares everything to do with threading unspecified or undefined.

If your application must be multi-threaded, it does make sense to write it in a language with proper multi-threading support.

Also some other things aren't really written out, like threading or some kind of Akka stuff.

During years this was a big issue in Java, and why it really needed multi-threading.

Once they add annotations and shared state and threading (and that's coming), the party will be over and the earth salted.

That being said, i think the nature of go routines and how go handles threading could be very important for mobile.

If Python can't get this threading thing worked out, isn't the language going to get left behind as parallel architecture marches onward?

Re: your [1], Clojure's threading macros came to mind first for me as well.

There are many ways to exploit multi-cores, multi-threading is just one of them.

I'd love to see it become more of a mainstream technique in Python than `import threading', etc.

There also tend to be fewer comments (it's easy to see who is replying to who) so threading is typically not necessary on FB.

Much like the threading macros, the result even appears to be doing a kind of mutation, even though it's actually doing nothing of the sort.

Twitter would be easier to use if they reverted the recent "improvements" to the tweet threading UI.

A single Gambit instance is a single process - its "threading" is implemented using continuations - and so (unlike Erlang) it cannot automatically use a dual core.

Threading with locks isn't going to go away any time soon no matter how religiously one states their opposition to it.

> The CPU was overclocked from its default clockspeed of 4000MHz to 6531MHz without deactivating any cores or the Intel Hyper-Threading feature.