3 ms·
Go 1.1 performance improvements, part 3
- f2f 13y agoi like green.
- stcredzero 13y agoNice 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)
- millstone 13y agoHave you tried libdispatch (http://en.wikipedia.org/wiki/Grand_Central_Dispatch http://en.wikipedia.org/wiki/Grand_Central_Dispatch)? It’s pretty darn powerful.
- stcredzero 13y agoI'd like to see a side by side comparison of this to Go.
- pjmlp 13y agoIf you are on Objective-C, https://developer.apple.com/library/ios/#documentation/General/Conceptual/ConcurrencyProgrammingGuide/Introduction/Introduction.html#//apple_ref/doc/uid/TP40008091 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
- stcredzero 13y ago"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.
- pjmlp 13y agoDon't get it. Please note I do have Go experience.
- stcredzero 13y agoYou can write entire concurrent systems in Go without writing callbacks.
- pjmlp 13y agoYou can do the same in other language frameworks as well.
- stcredzero 13y agoOn iOS? Is there a one-stop tutorial that covers this?
- 501 13y agoXPC services implemented in golang would be very handy - here's hoping iOS 7 gains full XPC support.