Go 1.1 performance improvements, part 3(dave.cheney.net)
dave.cheney.net
Go 1.1 performance improvements, part 3
http://dave.cheney.net/2013/05/28/go-11-performance-improvements-part-3
2 comments
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)
Have you tried libdispatch (http://en.wikipedia.org/wiki/Grand_Central_Dispatch)? It’s pretty darn powerful.
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
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
"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.
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.
You can write entire concurrent systems in Go without writing callbacks.
You can do the same in other language frameworks as well.
On iOS? Is there a one-stop tutorial that covers this?
XPC services implemented in golang would be very handy - here's hoping iOS 7 gains full XPC support.
i like green.