How is the Swift experience outside of the Apple ecosystem? And how does it compare to other languages like C# and Java?
Swift Distributed Actors
71–80 of 135 posts
Re: Swift Distributed Actors
#72Earlier quoted context omitted.
My experience is the opposite: using Swift for Apple ecosystem development basically removed all of the benefits that Swift the language offered. It’s clearly designed as a general purpose language, and its adoption mostly curtailed by this reputation.
I’ve been using Swift to develop Apple software since 2014. I’ve released quite a few apps, written with it. Before that, I used ObjC. I’m extremely happy with Swift. As far as adoption goes, many large codebases are likely still ObjC; simply because of hysteresis. Major architectural shifts take a lot of time, money and risk. That’s one reason I don’t feel that much urgency to jump on the SwiftUI/Async stuff (but I…
I am still writing Swift despite being retired but as part of my art generation work now.
Re: Swift Distributed Actors
#73Earlier quoted context omitted.
I’ve been using Swift to develop Apple software since 2014. I’ve released quite a few apps, written with it. Before that, I used ObjC. I’m extremely happy with Swift. As far as adoption goes, many large codebases are likely still ObjC; simply because of hysteresis. Major architectural shifts take a lot of time, money and risk. That’s one reason I don’t feel that much urgency to jump on the SwiftUI/Async stuff (but I…
In my last job until I retired this year, I spent 5.5 years writing only Swift at a large (not FAANG) company. It took the entire mobile team about that time to retire most of the Obj-C codebase(s). Swift is by far my favorite language despite having spent decades with C/C++/Java and Obj-C. I am still writing Swift despite being retired but as part of my art generation work now.
I've been "retired" for four years, and work more, every day, than I ever did, as a grunt.
I write Swift 7 days a week. I really like the language.
Re: Swift Distributed Actors
#74Earlier quoted context omitted.
I never liked X11, its API is much worse than any complaint one can imagine over Win32. It is no surprise that the only UNIX clones that had a good desktop user experience always did their own thing instead of pursuing the X11/Motif path.
The architects of IRIX would like a word with you.
Really curious what success story they are about to tell me.
Re: Swift Distributed Actors
#75So now we'll have Akka, Elixir, Erlang and Swift as options. Pretty exciting!
edit: Rust's Actix too!
edit2: jk Actix is only local.
Re: Swift Distributed Actors
#76This seems like a super interesting feature to have as part of a language. I hope Swift can eventually become more of a general purpose language, as its actually pretty nice and they're introducing features like this that clearly targets server-side programming. However it seems right now its tied to much to just iOS development and Xcode, which doesn't make for a great experience using it for other things.
Re: Swift Distributed Actors
#77Earlier quoted context omitted.
> Konrad Malawski is a member of a team developing foundational server-side Swift libraries at Apple, with focus on distributed systems and concurrency
If I am not wrong he also worked on Akka, the distributed actors library for Scala.
Re: Swift Distributed Actors
#78Where is the side to side comparison of features and to-do between this and existing distributed actor implementations, such as erlang + otp or java and whatever thing it uses? This approach of ignoring the rest of the world and explaining Swift concepts as if they exist in a vacuum is frustrating and counter-productive. Even if this were a totally new feature, I'd expect links to research papers. It is one thing to…
I skimmed through the blog post, and it seems to me that they are not claiming they invented something new, just that they are adding this to Swift language. (Distributed) actor model is nothing new, but I definitely wouldn't classify it as something that's common in other languages. To my knowledge Erlang/OTP is the only mainstream language where this is part of the standard library. There are implementations for ot…
I’d argue that this is because it’s a failed idea that conflates OO encapsulation, concurrency constraints, identity, serialization, and networking into a behemoth that does none of those things well.
Re: Swift Distributed Actors
#79This is awesome, I'm always looking for more competition in the distributed actor model/system space. So now we'll have Akka, Elixir, Erlang and Swift as options. Pretty exciting! edit: Rust's Actix too! edit2: jk Actix is only local.
Re: Swift Distributed Actors
#80I just don't understand the vision.