ceteia

6 ms·

1.
by ceteia 7mo ago
But can't you then set up a system such that if a person only picks one source or a few sources, and that turns out to be bad, that it primarily impacts negatively only themselves? Letting it be their own responsibility?
2.
by ceteia 7mo ago
Nitpicking: https://github.com/thelowsunoverthemoon/mahler.c/blob/4ebfe8... Should that type have been mah_acci instead of int? mah_acci doesn't seem to be used anywhere. Also, have you considered using
3.
by ceteia 7mo ago
Would educating people instead and giving them more options for information, not be better than banning access to information?
4.
by ceteia 7mo ago
Enum matching is one of the better aspects of Rust.
5.
by ceteia 7mo ago
> When I update the rust compiler, I do so with very little fear. My code will still work. The rust stdlib backwards compatible story has been very solid. This is not always true, as seen with rustc 1.80 and the time crate. While it only
6.
by ceteia 7mo ago
Indeed, unsafe Rust is overall more difficult than C++, like one speaker at a Rust conference claimed: https://lucumr.pocoo.org/2022/1/30/unsafe-rust/ And you are not being honest nor accurate here.
7.
by ceteia 7mo ago
Not Firefox, but Servo has quite a lot of unsafe, even though some of the results are false positives. https://grep.app/search?f.repo=servo%2Fservo&f.repo.pattern=... So Servo at the very least cannot be said to be &#x2
8.
by ceteia 7mo ago
Wasn't the F-35 budget "explosion", or overruns, caused in general by mismanagement? But I will not argue that C++ is perfect. Instead, the ttps://en.wikipedia.org/wiki/Ariane_flight_V88 , where US$370 mil
9.
by ceteia 7mo ago
People made similar arguments regarding C++ versus Ada. The US military and defense industry even got something like a mandate in the 1990s to only write in Ada. And then there was https://en.wikipedia.org/wiki/Ariane_f
10.
by ceteia 7mo ago
How can you be sure? When I looked at for instance sudo-rs, it proclaimed loudly that it is memory safe, but its code has lots of unsafe. https://github.com/trifectatechfoundation/sudo-rs https://grep.app&#x
11.
by ceteia 7mo ago
> No, we don't. All of the ones we have are heavily leveraged in Chromium or were outright developed at Google for similar projects. 10s of billions are spent to try to get Chromium to not have these vulnerabilities, using those too
12.
by ceteia 7mo ago
https://materialize.com/blog/rust-concurrency-bug-unbounded-... Edit: Replying to ghusbands: 'unsafe' is a core part of Rust itself, not a separate language. And it occurs often in some types of Rust projects
13.
by ceteia 7mo ago
People also write Rust code that is not memory-safe. https://materialize.com/blog/rust-concurrency-bug-unbounded-...
14.
by ceteia 7mo ago
Does the Rust implementation not use any unsafe and does not use libraries using unsafe?
15.
by ceteia 7mo ago
Are you really OK with runtime "expression patterns"? match (0, 1, 2) { case (F(), 0, G()) => ... } > Here (F(), 0, G()) is not an expression, but three separate expressions in a tuple pattern. As a result
16.
by ceteia 7mo ago
Do you know of a good way to measure market share? I know of GitHub's and StackOverflow's surveys, but I'm not sure how well they reflect reality. There is also Redmonk. GitHub's survey did not say much about Rust I thin
17.
by ceteia 7mo ago
What concerns me is that the design of Carbon in aspects seem to have serious issues already now. In case that you are well familiar with for instance pattern matching, might you have any opinions on the pattern matching that is currently p
18.
by ceteia 7mo ago
Rust projects generally use licenses like MIT instead of GPL, and thus some major corporations support Rust a lot, and thus Rust will continue getting popular.
19.
by ceteia 7mo ago
The GitHub project has some activity at least, and they might be coming with some announcement later this year. https://github.com/carbon-language/carbon-lang/
20.
by ceteia 7mo ago
I am not sure how Carbon will go. The Carbon compiler is not ready to be used yet by the public as I understand it, and the roadmap has not been updated for some time now, it seems. https://docs.carbon-lang.dev/docs/pro
21.
by ceteia 7mo ago
That means that, even if a C developer used or added C bindings to DRM when wanting to write a new driver, they would be forced to write their new driver in Rust regardless. That seems to run counter to the promises made by Linus.
22.
by ceteia 7mo ago
> When an all-new driver is written in Rust, then working on that driver will require knowing Rust. But that is not what the claim is about, it is about any new driver, not a specific one.
23.
by ceteia 7mo ago
I don't believe that I am. Especially given the other arguments and claims in the email.
24.
by ceteia 7mo ago
But, is this true or false? > If any C developer developed drivers in C previously for the DRM subsystem, they might in the future be forced to learn Rust.
25.
by ceteia 7mo ago
But what about this statement that Linus wrote: > That's been made clear pretty much from the very beginning, that nobody is forced to suddenly have to learn a new language, and that people who want to work purely on the C side can
26.
by ceteia 7mo ago
Weren't the old Linux kernel developers promised the opposite by Linus Torvalds? That they would be able to continue writing in C? https://lkml.org/lkml/2025/2/20/2066 > The document claims no su
27.
by ceteia 7mo ago
But why then did arcadia_leak imply as far as I understood him that C is needed for performance in D? But D is not included in the benchmarks game at debian.net, which isn't fair to D either as far as I can tell.
28.
by ceteia 7mo ago
Interesting. That might fit the bill, though I am not completely sure. Do you happen to know why D has not been accepted into the benchmarks games at debian.net? I heard that D developers contributed D code, but that D was never accepted.
29.
by ceteia 7mo ago
> A refcounting algorithm, like that found in Rust's (and C++'s) runtime is such a classic GC that not calling it a GC is just confusing. But is it not easy to opt out of in C, C++, Zig and Rust, by simply not using the types t
30.
by ceteia 7mo ago
> Weka have a realtime distributed filesystem written in D, used for ML/HPC workloads. This https://github.com/weka ? Most of the D repositories appear to have very little activity. The Go repositories seem to have

More ›