3 ms·
Likewise... I'm more and more finding myself either either looking for less-popular and more minimal crates (that don't need Async, or tens of other further de
by berkut 5y ago
Likewise...
I'm more and more finding myself either either looking for less-popular and more minimal crates (that don't need Async, or tens of other further deps), and even writing my own things for certain simple stuff (the latter often reinforced by wanted to experiment and learn).
I'm more concerned about many 'critical' (because there's nothing like them in the standard library, i.e. 'rand', 'chrono') and well-recommended crates are still not at version 1.0.0, so technically they could change the API... (they won't/can't, but seems a very odd situation to me).
- jacobmischka 5y agoWhat makes you say they can't?
- berkut 5y agoWell, I'm assuming it would break a lot of code...
- jacobmischka 5y agoThat's what semantic versioning is for?
- berkut 5y agohttps://semver.org/#how-do-i-know-when-to-release-100 https://semver.org/#how-do-i-know-when-to-release-100 Pretty much everyone's using chrono and rand, as there's not really anything else...
- jacobmischka 5y agoI'm not sure what that link is supposed to mean in this context. Yes, they should have released 1.0 sooner. That doesn't change the fact that they may want to make a breaking change in the future and bump the major version number. Tokio is the de facto async runtime, used by many (though not as many as rand and chrono surely, but still), and they've bumped major versions. Some projects still use old versions, which is actually much more problematic since multiple async runtimes usually can't exist simultaneously, but things are still mostly fine overall.