Re:The road to Dart 3: A fully sound, null safe language
by hajile on Thursday December 08, 2022 @11:19AM
(#33909620)
One step at a time. They don't want a Python 2/3 situation.
[ Parent
| on HN ]
Re:The road to Dart 3: A fully sound, null safe language
by jnwatson on Thursday December 08, 2022 @11:57AM
(#33910159)
Why? Swift has never worried about it, and Dart’s target market is a lot closer to Swift.
Swift has made large backwards-incompatible changes 3 times now.
Re:The road to Dart 3: A fully sound, null safe language
by pianoben on Thursday December 08, 2022 @12:58PM
(#33910915)
I've been a mobile dev for many years now. Every team I've been on either largely avoided Swift for the first 3-5 years, or was burned hard due to the constant churn.
It's much more stable these days, but personally I'm still wary of the team's (past?) proclivity to make sweeping incompatible changes.
Re:The road to Dart 3: A fully sound, null safe language
by Apocryphon on Thursday December 08, 2022 @07:25PM
(#33915812)
I feel the same way towards SwiftUI, which seems to have an even more rockier upgrade path than Swift.
Re:The road to Dart 3: A fully sound, null safe language
by alwaysbeconsing on Thursday December 08, 2022 @12:25PM
(#33910530)
How many Swift users consider that a good thing though? Swift is on railroad tracks: you have to upgrade on Apple's schedule or eventually you won't be able push your product to the store. Also, 2 to 3 was a nightmare and the Swift team itself is actually pretty chary about doing anything like that again.
Re:The road to Dart 3: A fully sound, null safe language
by faizmokhtar on Thursday December 08, 2022 @09:06PM
(#33916496)
Not being able to run project that's using older Swift version on the latest Xcode is a terrible experience tho.