Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I’ve already banned the use of actors in my team for at least two years (the time it matures).

You are right, the bloat is there, and i have absolutely no idea how they’re going to reverse that trend.



It is weird. I think both actors and the upcoming ownership model (for Swift 6.0) are important. But they are huge to consume with (hard to understand, big foot-print in compiler).

Maybe at some point, we can have Swift 7.0 which demotes classes to a special type of struct (you cannot without ownership model) like Arc in Rust, and that can get rid of some bloats.

I see two issues when the language evolves: 1. the type system still needs some work, parameterized extensions and non-existential / existential type differences are the two major issue I have. 2. get rid of Foundation on non-Apple platforms. The community should really say Swift 7.0 is the "done" version like Go 1.0 (or Julia 1.0), and we will do fixes, small type system QoL improvements and improve standard libraries and have no plan for 8.0 any time soon.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: