simonask

15 ms·

361.
by simonask 11mo ago
I disagree very strongly that a suggestion to change something is also a personal attack on the author of the original code. That’s not a professional or constructive attitude.
362.
by simonask 11mo ago
Source-to-source translation will be very hard to get right, because lots of things are UB in C that aren’t in Rust, and obviously vice versa. Rust has unwinding (panics), C doesn’t.
363.
by simonask 11mo ago
What are you talking about? Rust’s function signature and type declaration syntaxes are extremely vanilla, unless you venture into some really extreme use cases with lots of lifetime annotations and generic bounds. I seriously don’t get it.
364.
by simonask 11mo ago
Be real for a second. People are arguing against Rust because it supports fewer target architectures than GCC. Which of the target architectures do you believe if important enough that it should decide the future development of apt?
365.
by simonask 11mo ago
That’s also not something anybody has actually said.
366.
by simonask 11mo ago
And just like vegans, their detractors are far more vocal in reality.
367.
by simonask 11mo ago
The assumption here is that there exists an unambiguous C representation for all LLVM IR bitcode emitted by the Rust compiler. To my knowledge, this isn’t the case.
368.
by simonask 11mo ago
There’s definitely holes, but I’m wondering what you are referring to here.
369.
by simonask 11mo ago
I fail to see that there is any material difference. Whether you catch-unwind within a single thread or in a separate thread such that the panic can be resumed on join makes zero difference. Heck, you can have Drop impls observing the state
370.
by simonask 11mo ago
From TFA: > C++ is often described as complex, hard to learn, and unsafe. That reputation is undeserved. The language itself is not unsafe. On the contrary: it is precise, honest, and consistent. What is unsafe is how it is used if it is
371.
by simonask 11mo ago
Mutex doesn't promise to uphold any more invariants than `&mut T` does. If the state can be corrupted by a panic while holding `&mut T`, I don't think there's any good reason to expect that obtaining it through `Mutex
372.
by simonask 11mo ago
It's interesting to read this from someone who more at a more advanced stage of life, but I also wonder if there is a built-in assumption around diagnoses and treatments being potentially negative. I think people seek out these diagnos
373.
by simonask 11mo ago
Dynamic rendering, timeline semaphores, upcoming guaranteed optimality of general image layouts, just to name a few. The last one has profound effects for concurrency, because it means you don’t have to serialize texture reads between SAMPL
374.
by simonask 11mo ago
`wgpu` in Rust is an excellent middle ground, matching the abstraction level of WebGPU. More capable than OpenGL, but you don’t have to deal with things like resource barriers and layout transitions. The reason you don’t is that it does an
375.
by simonask 11mo ago
I stopped reading when he compared the Rust compiler to his angry ex. Like, what are we doing. This “article” is flame bait.
376.
by simonask 11mo ago
I hate this take. It's myopic. Centered on, and informed by, a political culture that is quite unique to the US, and to a limited extent the UK. Lots of politics the world over does not work like that, and is in fact rooted in collabor
377.
by simonask 11mo ago
I think it's both arrogant and ignorant to make assumptions like that.
378.
by simonask 11mo ago
If you don’t work in the industry, you have zero chance of accurately evaluating whether or not, or how, it will be impacted by any new technology. The fact that it “seems easy” is a great flag that it probably isn’t.
379.
by simonask 11mo ago
I don't know man, Rust's borrowing semantics are pretty new under the sun, and actually do change the way you think about software. It's a pretty momentous paradigm shift. Zig is nice too, but it's not that.
380.
by simonask 11mo ago
That's valid, even sensible, but you have now left significant performance on the table.
381.
by simonask 11mo ago
Finally someone who actually gets it. Many Rust proponents are experienced C and C++ developers who have dealt with this situation for decades. Given the language, it's understandable that compilers make the choices that they do. It&#x
382.
by simonask 11mo ago
Rust's borrow checker is unique in the sense that it is production-ready. Cyclone is indeed prior art, but it's not as if it ever got beyond the research project stage.
383.
by simonask 11mo ago
I think it’s pretty unfair to characterize new, helpful lints as “breaking changes”. There’s plenty of options to not have to deal with that (unless you want to of course).
384.
by simonask 11mo ago
> Rust actually causes far more code churn - there's virtually a monthly cycle of some Rust compiler update requiring changes to existing code. This is really surprising to me. Which changes have you had to deal with here? The only
385.
by simonask 11mo ago
Because every problem detected by Fil-C is already a serious problem in the existing code. As a mitigation strategy, that becomes less interesting as the quality of that code increases, but you still pay the full cost regardless of whether
386.
by simonask 11mo ago
So I don’t want to come off as dismissive of the effort - it’s certainly impressive! The reason I’m not super excited is based on the widely publicized findings from Google and Microsoft (IIRC) about memory safety issues in their code: The
387.
by simonask 11mo ago
Setting up any of that is well outside the reasonable expectations of the average user.
388.
by simonask 11mo ago
Sure, that makes sense. The point I’m making is just that from an engineering perspective, that also implies that there is no longer any reason for that software you’re running to be written in C at all.
389.
by simonask 11mo ago
Unsafe Rust actually has a great runtime analyzer: Miri. It's very easy to just run `cargo +nightly miri test` in your project to get some confidence in the more questionable choices along the way.
390.
by simonask 11mo ago
If that's all you need, the state of the art is very available already through the JVM and the .NET CLR, as well as a handful others depending on your use case. Most of those also come with decent languages, and great facilities to lev

More ›