4 ms·
I don't share your evaluations here, but a question: > no major OS seems to be picking up Rust as a first class citizen, What would this mean to you?
by steveklabnik 10y ago
I don't share your evaluations here, but a question:
> no major OS seems to be picking up Rust as a first class citizen,
What would this mean to you?
- klab_yourself 10y agoRust is a bigger failure than you ever thought it would, Stevey-pie. Remember like a year ago when I told you that Rust was on its way downhill if ANSI standardization wasn't pursued? Crazy how I'm always right, and how anti-capitalist deviant weirdos like you are always wrong. Mozilla is going down as well. Give it another year or two, Firefox will crumble, funding will dry up, they'll probably want to hang on to "earners" like you that will work for nothing because they don't know any better but big corps will probably pick up some of the more sane talent in the meantime. Things we've learned from Rust will either be used to make gcc better, or create a new systems language that people actually want to use, that is S T A N D A R D I Z E D, and developed by a more ethical group of people. Adios, maricón
- wcummings 10y agoAll the real elite programmers are wobblies.
- antod 10y agoYeah not really sure what that was supposed to mean in relation to Rust. To me that statement would only make sense for languages that require some sort of runtime/interpreter installed rather than natively compiled. eg Python and Perl get shipped by default in most Linux distros base image, whereas Java or Ruby don't tend to be. Whereas C doesn't have a compiler shipped in some/most base images - despite C being about as first class as languages get on Unix.
- steveklabnik 10y agoYeah. I was also wondering if they meant "available through my distro's package manager", in which case, that's been happening a lot lately. Debian and Fedora will both have initial packages in their next releases, and work is ongoing with a number of linuxes.
- rkangel 10y agoI was composing a much longer answer before I realised that this is actually a really interesting question. While I try and think through that, this is my immediate reaction. It comes down to one thing: the ABI. Only C (and therefore to some extent C++) is the first class citizen in all the major OS families we care about, because the C ABI is the standard for compiled objects (whether executable or library).
- the_why_of_y 10y agoYes, that's it. To keep things maintainable, OS interfaces are available to applications in the form of shared libraries, and that requires a well-defined and stable language ABI. It's regrettable that C++ currently has an advantage over Rust in this regard...
- steveklabnik 10y agoOnly barely though, C++ is still notoriously hard to link to.
- UtherII 10y agoC++ has no advantage over Rust in this regard : C++ and Rust does not have stable ABI. But both can use the C ABI when a stable ABI is needed.
- the_why_of_y 10y agoC++ is not just boost and ICU - there are a handful of C++ libraries with a good ABI compatibility track record, for example Qt and the KDE stack. The C++ ABI of Microsoft Visual Studio is stable since practically forever, albeit with a severe restriction: the language ABI is stable, but not the C++ (or even C) standard library ABI - every Visual Studio release comes with a new incompatible msvcrNNN.dll. But you can load as many different runtime libraries into a process as you like, the big practical restriction is that you can't pass standard library objects allocated by one runtime to a different one. The C++ ABI of GCC is stable since version 3.2, released in 2002, on x86 platforms (there were numerous fixes in later releases for other platforms). They even managed to retrofit new incompatible C++11 requirements on std::string with some preprocessor hackery and namespace mangling, without bumping the libstdc++ SONAME. As usual, on macOS the situation isn't as good because they threw out libstdc++ for some clang reinvention of the wheel.