Re:Go 1.1 performance improvements, part 3
by stcredzero on Tuesday May 28, 2013 @02:11AM
(#5778397)
Nice to see work on ARM. I wish we had something as powerful for dealing with concurrency in iOS as golang. Immutables and the SDK get you pretty far, but not quite as elegant. (If I am wrong please tell me)
[ Parent
| on HN ]
Have you tried libdispatch (http://en.wikipedia.org/wiki/Grand_Central_Dispatch)? Itβs pretty darn powerful.
Re:Go 1.1 performance improvements, part 3
by stcredzero on Tuesday May 28, 2013 @11:22AM
(#5780537)
I'd like to see a side by side comparison of this to Go.
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
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.
Don't get it. Please note I do have Go experience.
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.
You can do the same in other language frameworks as well.
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?