Or you can write rust with nostd, and no allocator (bring your own). But what would you do anyway if you `vec.push(x)` and somehow there isn't enough ram? How would you signal the error in a way that makes sense to the caller of `push`?
-
-
Admittedly lots of programmers want products not languages. It's good for short-term promotion, bad for long-term health.
-
I don't agree with that. Having official package manager is not a problem (actually the opposite), having it tightly coupled with the lang and the build system is.
-
Well that's probably closer to what I should have said.
End of conversation
New conversation -
-
-
Not every language has the luxury of being the official language of OS, like C on linux. I find package managers incredibly useful, because my community doesn't have the workpower to package every lib for every OS under the sun.
-
You don't have to. Whoever is packaging apps for the dist will also package dependency libs or static link them, & devs can just grab & build the source for libs they want.
-
Overall though apps should be using very few libs. Stdlib should cover most basic data structure needs. Without huge resources it's impossible to assess correctness of more than a handful of libs.
-
That's a value judgement, not an objective one. Rust's stdlib covers basic data structure needs and there's still enormous value in fine-grained packaging (though I would never go as far as what happens in npm, or admittedly, in some domains in Rust, too.)
End of conversation
New conversation -
-
-
That's a pretty fundamental point of disagreement., which we're unlikely to bridge. I think the usability improvements we've seen across *all* the languages with package managers have been positive. And yeah, I think a product approach is good.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.