News for hackers. Stuff that matters.

A comment on Go 1.1 performance improvements, part 3. Parent comment

Re:Go 1.1 performance improvements, part 3 by pjmlp on Tuesday May 28, 2013 @04:09AM (#5778818)
If you are on Objective-C,

https://developer.apple.com/library/ios/#documentation/Gener...

If using C++

std::async, std::future and respective std queues.

Intel TBB

If using C#

TPL and async/await

[ Parent | on HN ]
Re:Go 1.1 performance improvements, part 3 by stcredzero on Tuesday May 28, 2013 @05:11AM (#5778998)
"It important to note that queues are not a panacea for replacing threads."

Powerful, but not quite as good as Go. Seems to me you still end up writing callbacks.

[ Parent | on HN ]
Re:Go 1.1 performance improvements, part 3 by pjmlp on Tuesday May 28, 2013 @05:20AM (#5779031)
Don't get it. Please note I do have Go experience.
[ Parent | on HN ]
Re:Go 1.1 performance improvements, part 3 by stcredzero on Tuesday May 28, 2013 @11:20AM (#5780528)
You can write entire concurrent systems in Go without writing callbacks.
[ Parent | on HN ]
Re:Go 1.1 performance improvements, part 3 by pjmlp on Tuesday May 28, 2013 @11:29AM (#5780580)
You can do the same in other language frameworks as well.
[ Parent | on HN ]
Re:Go 1.1 performance improvements, part 3 by stcredzero on Tuesday May 28, 2013 @03:48PM (#5782259)
On iOS? Is there a one-stop tutorial that covers this?
[ Parent | on HN ]