Sorry for butting in, but is there a way to flag comments? I'm being called a name in https://news.ycombinator.com/item?id=43029816
[dead]
Your whole comment basically says that I'm right and that you were wrong, while portraying it as the opposite. It's really weird.
>In fact, that's basically the underlying argument surrounding R4L right now: the Rust people want to write nice Rust bindings that let the borrow checker do the work, while the C people[0] want Rust to just call C…
[flagged]
>In that sense, Rust is indeed specifically designed to play well in C codebases as the rest of the C code can basically pretend it's only working with C code. Do the semantics of the borrow checker play nicely with C…
>rowdy maintainers calling people "cancer" Where was this done? In the recent mailing list, the maintainer never called people cancer, he said https://lore.kernel.org/lkml/20250128092334.GA28548@lst.de/ >And I also do…
archive.ph/rESxe >Thinking of literally starting a Linux maintainer hall of shame. Not for public consumption, but to help new kernel contributors know what to expect. >Every experienced kernel submitter has this in…
Sorry for butting in, but is there a way to flag comments? I'm being called a name in https://news.ycombinator.com/item?id=43029816
[dead]
Your whole comment basically says that I'm right and that you were wrong, while portraying it as the opposite. It's really weird.
>In fact, that's basically the underlying argument surrounding R4L right now: the Rust people want to write nice Rust bindings that let the borrow checker do the work, while the C people[0] want Rust to just call C…
[flagged]
[dead]
>In that sense, Rust is indeed specifically designed to play well in C codebases as the rest of the C code can basically pretend it's only working with C code. Do the semantics of the borrow checker play nicely with C…
[flagged]
[flagged]
>rowdy maintainers calling people "cancer" Where was this done? In the recent mailing list, the maintainer never called people cancer, he said https://lore.kernel.org/lkml/20250128092334.GA28548@lst.de/ >And I also do…
archive.ph/rESxe >Thinking of literally starting a Linux maintainer hall of shame. Not for public consumption, but to help new kernel contributors know what to expect. >Every experienced kernel submitter has this in…