RE: https://mastodon.social/@dimitribouniol/115763141801761373
Great to see new Swift FormatStyle tovbe so light seight. Little bit scary how costly the builder init pattern may be, but I guess not unreasonable still. However, with long lists, caching its creation might be nice.
This was an interesting read: https://danielchasehooper.com/posts/why-swift-is-slow/
Coupled with the generally terrible compile times in Xcode, this can make Swift dev a miserable experience sometimes - especially when using SwiftUI, which exacerbates the problem with its heavy reliance on inference and overloading
I think the Swift team maybe underestimates how big of a problem this is? From this thread it seems like it's been written off as unsolvable rather than being an area of active effort?
You might be familiar with Things, a delightful personal task manager that has won two Apple Design Awards and is available across Apple devices including iPhone, iPad, Mac, Apple Watch, and Apple Vision Pro. At Cultured Code, the team behind Things, we care about a great user experience across every aspect of the product. This extends to our server back end, and after a rewrite our Things Cloud service has transitioned entirely to Swift. Over the past year in production, Swift has consistently proven to be reliable, performant, and remarkably well-suited for our server-side need.