Comment by pjmlp
3 months ago
He would vouch as great as he might be, he has a bias, and Mono GC was never a great implementation.
Also here is how great his new Swift love performs in reality against modern tracing GCs,
3 months ago
He would vouch as great as he might be, he has a bias, and Mono GC was never a great implementation.
Also here is how great his new Swift love performs in reality against modern tracing GCs,
Interesting link, but that's a nearly 7 year old version of Swift (4.2) running on Linux.
I wonder how the performance would be with Swift 6.1 which has improved support for Linux.
Probably much better, given the improvements on the Swift optimizer, but just goes to show "tracing GC" bad, "reference counting GC" good isn't as straighforward as people make it to be, even if they are renowned developers.
It's a cherry picked, out-of-date counter-example. Swift isn't designed for building drivers.
In reality, a lot of Swift apps are delegating to C code. My own app (in development) does a lot of processing, almost none of which happens in Swift, despite the fact I spend the vast majority of my time writing Swift.
Swift an excellent C glue language, which Java isn't. This is why Swift will probably become an excellent game language eventually.
5 replies →