moltonel3x

9 ms·

1.
by moltonel3x 1y ago
According to SlashData "size of programming language communities, Q1 2025": 28.0M JS+TS ... 5.6M Swift 5.1M Rust 5.0M Go They have measured Rust growing faster than Go over the years, with the overtake finally
2.
by moltonel3x 2y ago
That's very subjective, I find the Google style barely usable compared to OSM carto. No experience with Apple.
3.
by moltonel3x 3y ago
Rust does support adding deps using git urls, alternate repositories, filesystem paths, and even multiple sources for one dep. https://doc.rust-lang.org/cargo/reference/specifying-depende...
4.
by moltonel3x 3y ago
D, Ada, and Modula don't have enough traction. Go's runtime can be a showstopper, especially for multi-language projects. C++ may be better than C, but many people feel that Rust is even better. Rust is already available in almost
5.
by moltonel3x 3y ago
You'd need a few different ones, just like curl itself uses a lot of 3rd-party libraries to provide its full feature set. Some likely first choices would be hyper (http client/server), rustls (encryption), tokio (async scheduling)
6.
by moltonel3x 3y ago
Why would you think that nobody has ever used Rust there ? Somebody has obviously put in the work to support that platform, rustc doesn't just blindly inherits the list of target triples from llvm. While it's safe to assume that C
7.
by moltonel3x 3y ago
People often point this out, silently implying that Rust is not really supported/usable on the lower tiers and that therefore those platform should stick to C. But that's ignoring that the situation is the same with gcc/clang
8.
by moltonel3x 3y ago
> Replacing parts of curl with Rust will not be possible. It's not just possible, it's been done. You can compile curl with rustls, you could for a time compile it with quiche, and work is ongoing to compile it with hyper. Curl
9.
by moltonel3x 3y ago
You need to have someone, or a group of people, willing to write the code to implement support for modern tooling on their platform. Until then, old harder-to-secure codebases is what these platforms have. I know reversing the burden of imp
10.
by moltonel3x 3y ago
GPL doesn't force upstreaming, just making the sources available. Plenty of small vendors are not upstreaming their gcc patches. It's more a question of man-hours than of license.
11.
by moltonel3x 3y ago
Loongarch is at tier3 as well: https://doc.rust-lang.org/nightly/rustc/platform-support/loo...
12.
by moltonel3x 4y ago
A Go version wouldn't improve anything upon the Rust version either. At this scale, Go's simplicity would be a hindrance more than a help, development velocity would suffer compared to Rust. Integration would only be possible in t
13.
by moltonel3x 4y ago
So ? The fact that rustc compiler uses a component written in C++ doesn't mean that even pure Rust projects have a C++ dependency. Follow any language's bootstrap chain and you'll find C somewhere (or a bootstrapping purists
14.
by moltonel3x 4y ago
On single C file, 159 lines compared to 83000 lines of Rust. It's used to generate a cert for unittests, not sure why that's not done in Rust.
15.
by moltonel3x 4y ago
Having C or C++ somewhere in the lower levels of your stack doesn't make them the primary language for your domain. Other wise CPU microcode would be the primary language of every domain.
16.
by moltonel3x 4y ago
Yes, public github repos, stackoverflow survey respondents, devjobscanner offers, google searches, etc are all skewed in some way. It's very hard to qualify the effect of those biases though: for example how does the public/privat
17.
by moltonel3x 4y ago
Different metrics tell a different story. For example GitHub pull requests [1] are C++: 2.60%, Rust: 2.09%, C: 1.43%, with a clear trend showing Rust ahead of C++ next year. Or you could look at the Stackoverflow survey of languages used am
18.
by moltonel3x 5y ago
SWC (by the same author as this tentative tsc port) is a part of more and more people's typescript toolchain, and is written in Rust. Having all your ecosystem in a single language feels nice, but pragmatically different tools might be
19.
by moltonel3x 5y ago
> Afaict, none of them requires multiple mutable references to the same objects They ask to store objects ("turtles") into a single Vec. Two turtles from that Vec can breed to create a child turtle stored in that same vec. Pare
20.
by moltonel3x 5y ago
There are a lot of Rust GC approaches here, makes me wonder why the study author didn't use one (or more) of the existing sound GCs. Remove a glaring flaw of the study, and spend less time writing throw-away code.
21.
by moltonel3x 5y ago
Sorry, bad mischaracterisation on my part, annoyingly it's too late to edit my post. Looking at the Ada docs again, it considers manual deallocation an unsafe operation and suggests avoiding it altogether (IIUC, by restricting yourself
22.
by moltonel3x 5y ago
He (and other prominent kernel developers) has manifested his interest many times, but is taking a strict "wait and see" approach (as you would expect from any big project manager). Whether it happens or not, Rust has gotten close
23.
by moltonel3x 5y ago
The coreutils rewrite is essentially a hobby project, which nobody is going to switch to until it can boast 100% compatibility. So of course it's slow coming, it's not a fair comparison. There's also the issue that writing a
24.
by moltonel3x 5y ago
Userland is worth fighting for too. https://imgs.xkcd.com/comics/authorization.png But as bawolff said, the main issue is moving towards safer tech. If Ada had good enough momentum, we'd be discussing Ada in the k
25.
by moltonel3x 5y ago
A lot of those guarantees are only available in the alloc-free subset of Ada, which make them much less attractive. The devil is in the details, making Ada guarantees not always better than Rust ones.
26.
by moltonel3x 5y ago
D and Ada both use a GC in many contexts, and are not half as interesting in their GC-less contexts. They both initially only had a proprietary compiler, which durably harmed adoption. They both seem to cater to fewer domains than C/C+
27.
by moltonel3x 5y ago
Rust isn't only nibbling at the C/C++ niches: thanks to its correctness and productivity aspects it also attracts people coming for example from Go/Python/Javascript. In some way, you could say that Zig is pulling system
28.
by moltonel3x 5y ago
This points to the larger perception issue that "anybody who advocates for Rust is part of the Rust community and/or knows Rust well". But there are many Rust evangelists who obviously don't know much about Rust (this is
29.
by moltonel3x 5y ago
Adding Rust complicates things, but Rust makes writing correct code easier, which is no small feat in the kernel world. The added complexity may be big, but it's a one-time cost compared to the stream of Rust code that one can hope for
30.
by moltonel3x 5y ago
"opt.ok_or(err)?" is a pretty neat way of returning early with the error "err" if opt is empty. This is pretty idiomatic Rust you should get familiar with before comparing the readability with a language you know better.

More ›