IMO Swift is pretty great as a language and should evolve in a measured way going forward. The investments we need now are in the areas of tooling and developer experience. SwiftPM could be so much better (binary dependencies), github package repo support, artefact caching etc.
On the road to Swift 6:https://forums.swift.org/t/on-the-road-to-swift-6/32862 …
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I don’t know how quickly the changes will come and how dramatic the impact will be, but after several years of swift with hundreds of engineers, I am glad to see that list matches ours almost exactly.pic.twitter.com/7vTMOHgRzv
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
It deviates more and more away from OOP. Like with SwiftUI, based on value types. All structs and tons of protocol dependencies. I think Swift on the wrong track, as seen in the perspective of true reference based design and programming. The constant obsessed fear of mutability?
-
The more states your code can be in, the harder it is to reason about. It’s not a bad idea to nudge you away from too much mutation. It’s also not friendly to multi threading and cache locality.
- Još 1 odgovor
Novi razgovor -
-
-
excited to see the future IDEs that people start producing when LSP is finalized.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.