News for hackers. Stuff that matters.

tmc2

Re:Reasons for Python async/await on Thursday May 21, 2015 @12:14AM (#9580926)
> nobody gave much of a fuck

I don't at all mind your saying so, but it might be frowned on around here.

> Mainstream is not a "moving goalpost fallacy".

Why can't you read?

Re:Reasons for Python async/await on Wednesday May 20, 2015 @09:01PM (#9580401)
That's a loaded question, in that it's notoriously difficult to measure, and you already know the answer, but here:

http://www.tiobe.com/index.php/content/paperinfo/tpci/index....

Surprised?

Re:Reasons for Python async/await on Wednesday May 20, 2015 @05:40PM (#9579509)
I didn't realize factual corrections need to be cleared by a committee that decides which languages matter.

("More mainstream" is a moving goalpost fallacy.)

Re:Reasons for Python async/await on Wednesday May 20, 2015 @04:57PM (#9579249)
> the first mainstream imperative scripting language to have these async/await concepts built-in

Hi. https://www.dartlang.org/articles/beyond-async/

That's fascinating. I grew up on Sierra logic, and (so?) I take it for granted. Of course I shouldn't eat the pie; I might need it later.

The real world follows this rule, too. Economists call it "time preference."

http://en.wikipedia.org/wiki/Stanford_marshmallow_experiment