The ecosystem is small and immature. This results in sparse documentation, and a wealth of small beta-level interesting libraries but few stable choices.
It is a bit awkward because Rust as a language is seen as safe and fast, yet most libraries out there will put a big warning saying something like "This works most of the time, but it might break or we might make some big changes at anytime." But i know this will get better with time.
By "Break" they mean stop compiling, not stop working or crash at runtime. But also note that as long as you sensibly specify your dependencies, that will not affect you until you want to upgrade that dependency. Almost everyone is correctly following semver, so breaking changes won't occur on a minor point release.
Is it too cynical to suggest that when you get a mature, pretty complete and stable tool set (e.g. Rails) then it stops becoming fashionably cutting edge, and the kool kidz want to use something else instead?
Hmm, interesting. I could see that being a factor...but is Rails no longer considered "Kool"? I didn't realize it had already fallen from grace, at least around me it's a widely used tech, seems to be going strong.
I'm pretty sure that it has matured to the stage where its only use is as a productive tool for creating useful products. I don't think that that feels like fun to everyone.
OK, a bit cynical.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It is a bit awkward because Rust as a language is seen as safe and fast, yet most libraries out there will put a big warning saying something like "This works most of the time, but it might break or we might make some big changes at anytime." But i know this will get better with time.
By "Break" they mean stop compiling, not stop working or crash at runtime. But also note that as long as you sensibly specify your dependencies, that will not affect you until you want to upgrade that dependency. Almost everyone is correctly following semver, so breaking changes won't occur on a minor point release.
Well, safe and fast at the language level is a different concern than at the library level.
It's more à concern around the breaking changes that might occurs rather than safety.
Is it too cynical to suggest that when you get a mature, pretty complete and stable tool set (e.g. Rails) then it stops becoming fashionably cutting edge, and the kool kidz want to use something else instead?
Hmm, interesting. I could see that being a factor...but is Rails no longer considered "Kool"? I didn't realize it had already fallen from grace, at least around me it's a widely used tech, seems to be going strong.
I'm pretty sure that it has matured to the stage where its only use is as a productive tool for creating useful products. I don't think that that feels like fun to everyone.
OK, a bit cynical.