4 ms·
> Well, Debian Bullseye, a distro that hasn't even been released yet, already has a rustc that's so out of date (ie, ~5 months, 1.48) that it can't compile code
by jen20 5y ago
> Well, Debian Bullseye, a distro that hasn't even been released yet, already has a rustc that's so out of date (ie, ~5 months, 1.48) that it can't compile code written today using today's features.
This sounds more like an argument against Debian’s packaging practices than Rust. Debian is full of out-of-date tools, and that and CentOS doing the same are the reason non-system package managers are so popular.
- gspr 5y agoIt's not a problem with mature languages though.
- jen20 5y agoDepending on what you consider “mature”, sure. Here is a short list of programming languages where I have had to install an up-to-date version on recent Debian, Ubuntu or RHEL derivatives in just the last month: - Node.js - Python - Go - Rust - C++ - .NET Core - Java None had an up-to-date version in the distribution repositories. It’s a problem - and for those who defend it as otherwise while lamenting the rise of Docker, perhaps it’s worth some careful introspection about what a majority of people actually want from an operating system distribution, and whether the concept is in fact a relic of the days when software was distributed on CDs via the mail.
- gspr 5y agoReally? For what reason did you have to install a newer Python, a newer C++ compiler, or a newer Java runtime? > None had an up-to-date version in the distribution repositories. Of course not. A Debian release is meant to not change – except for security fixes – for the duration of its 2 year cycle. That's a feature, not a bug.
- jen20 5y agoTo run software written using them. Operating systems are servant of their applications, not vice versa.
- Xylakant 5y agoWhat’s a mature language then? I’ve encountered this issue with rust, php, ruby, nodejs, python , java.