9 ms·
> Updating the minimum supported Rust version is a breaking change This is not the majority sentiment, for better or for worse. The project stopped releasing "
by steveklabnik 2y ago
> Updating the minimum supported Rust version is a breaking change
This is not the majority sentiment, for better or for worse. The project stopped releasing "what version of Rust do you use most" in the survey results in 2020 (which is a shame, imho) the vast, vast majority of folks use the latest stable, and very few use a previous version of stable. I have no real reason to believe this overall trend has changed since then.
This is especially true for an application, which this project seems to be. Libraries may have more of a reason to explicitly lag behind the latest, but there's not really a good reason to bother if nobody else is going to depend on your code.
- prophesi 2y agoThat makes sense to me. I usually use asdf to version Rust in personal projects, so I'm not always on the latest. But when I work on a new release I'll almost always update rust and any of my other dependencies, as I'd otherwise never keep them up-to-date. Or if a new language feature I want to try just came out. And God forbid you fall behind on React Native major releases in a project. I think the Expo project's solution to this is for all of the native configuration be done via plugins and cross-platform config[0]. Otherwise you'll be dealing with large diffs of native Android/iOS code that would have even native mobile devs tread carefully. [0] https://docs.expo.dev/workflow/prebuild/#sensible-upgrades https://docs.expo.dev/workflow/prebuild/#sensible-upgrades