Skip to content

Comment on Concurrency in Swift: One possible approachparent

Comments

Well, multicore isn't going away; concurrency (if not parallelism) is necessary for responsive UIs.

Did you have any specific improvements? The big requirements for distributed programming are mostly protobuf serialization and tcp/http; swift has both already.

I was thinking more in terms of first class support for distributed actors, with global addressing, message routing, etc. Not designing for multicore performance first, the way Pony did.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.