Yes, hello? Is this the Bryan Lunduke comment section?
Yes, hello? Is this the Bryan Lunduke comment section?


At some point one must have considered wearing the speakers on their head…


Why would a “pretty positive person” wake up and, for no reason at all, decide to be a massive fucking cunt for the day?
Do you communicate with all your friends on a level like that?
I can’t speak for the person you replied to, but I would be miserable if I had friends who behaved like this.
The more I scrolled through the comments, the more I longed for the familiar comfort of the braindead phoronix forums. It’s one thing to be convinced that C is the peak of programming language design (sometimes without having ever written a productive line of code), but it’s another thing entirely to be convinced that Rust is some sort of figurative (or even literal) trojan horse pushed by a global woke conspiracy and/or connected to the “planned release” of COVID-19.
His YT comment section is an experience. They’re breeding a unique kind of right-wing, tinfoil hat Linux extremist, whose software usage is determined solely by esoteric association and “suspicious timing” like seeing widespread adoption during the start of the COVID-19 pandemic. The phoronix comment section is a garden of rationality and level-headed thinking in comparison.


Linus Torvalds is the last person to extend an olive branch to anyone contributing kernel code. Anyway, big news: https://lwn.net/Articles/1049831/


Why would you rate service quality by SEO performance? There’s almost nothing you can do to make high quality information avilable to search engines while being drowned out by an infinite flood of garbage.


Putting aside the ideological discussion about software licenses, saying that “they” are forcing Rust into the Linux kernel is a bold claim when Linus Torvalds clearly doesn’t mind the inclusion and even encourages it for example in driver code, at least as an experiment.


The internet would be a much quieter place if people were forced to have a minimal amount of insight into the topic they’re posting about. I guess what really annoys me is when popular blogs like this one deliberately frame something they don’t like in a way that makes it look worse to people who don’t know any better. There are very few people calling this shit out, be it on lemmy or the comments of the article itself. They even lied about FL1 being “bullet-proof” and “unaffected” by this bug, when it clearly wasn’t, according to Cloudflare - the primary source of this shitstain of an article.


I swear some of these commenters will jerk each other off about how “Rust is bad, actually” even if the root cause of an issue was someone intentionally crashing their app. Where do you even get this kind of attitude from? I’ve been around when Rust was the popular topic in any programming-related discussions and while there was plenty of evangelism and CS-101 experts making wild claims, nothing warrants this kind of irrational hatred. I thought you need to go to the phoronix forums to find people who have such loud opinions with very little actual programming experience, but apparently I was wrong.


There are good reasons to have unwrap or at least expect. There is no reason to use it in the case that Cloudflare used it in.
I do think there are long-term benefits in many cases, it just depends on available resources. There are plenty of projects that desperately need a rewrite for maintenance reasons alone so you might as well examine if language switch is worth it. It’s not like there aren’t a lot of success stories, even if there’s projects like sudo-rs where we’re, at best, not sure if there’s tangible benefits.
At this point I think the “thoughtful” C programmer is a myth and I don’t mean this as an insult. Even the most careful and experienced C gurus still make mistakes that would be much harder to make, if not categorically prevented in something like Rust. A lot of very secure C software is small in footprint, has had stable requirements for years, experienced thousands of hours of real world testing by users and the scrutiny of security experts. What I’m saying is: it should be easier to write secure software, especially with complex requirements or large attack surfaces.
I disagree that C has a notably smaller footprint than Rust for most purposes and system integration is in some cases harder in Rust precisely because of the notorious upfront implementation cost that prevents a lot of potential bugs.
Mozilla, where Rust was originally conceived, have already talked about this risk factor ages ago when they were still working on Servo. Reimplementing battle-tested software in a different language can result in logic bugs being introduced, which no programming language can really prevent. Many times they will actually reintroduce bugs that have already been historically fixed in the original implementation. This doesn’t invalidate the benefits of moving to a very memory safe language, it just needs to be taken into consideration when determining whether it’s worth the risk or the effort.
Honestly I have no idea whether sudo-rs is a good idea or not, but I have my doubts that any of the other people (especially the very vocal kind) chiming in on this do. Any time Rust is involved in the Linux community, a lot of vocal critics with very little knowledge of the language or programming in general seem to appear.
Getting comfortable with legacy software is completely valid as long as you’re aware of the potential disadvantages. Shitposting online about it or worse being wrong on the internet are different stories.
That’s not the same thing as shitposting online about your grievances with Wayland.
Did you try it that with Gnome? I heard that some input methods suffered with the wayland transition because mutter makes some weird choices. From my personal experience, libinput works great with a wacom tablet, so I’m assuming you ran into an issue with a specific DE.
Let me rephrase that: it sounds like a niche problem to have for an end user. It also doesn’t sound like a fair complaint, because no long-term replacement to X was ever going to be drop-in the way you seem to expect.
Alright then, since everyone assumes I’m here to participate in this shitty flamewar instead of genuinely asking what someone is talking about: the article does a pretty good job of explaining what the idea is behind not giving applications absolute coordinates to position their windows in. If that isn’t enough and you’re one of those people who insist that it must be those evil Wayland devs pushing their security agenda down everyones throats, then you might consider how much of a pain this was for any WM that wanted to do something like scrollable workspaces or managing a device that doesn’t have a standard screen shape. If anything, giving apps access to global coordinates the way X did, just makes them less portable to other environments. There are trade-offs here and you might disagree with the compromise we landed on for now, but all of this has already been discussed for years so at this point I really don’t care for snarky commentary from people who aren’t willing to contribute towards the changes they want to see.
Depends heavily on what place you ask for help in. There are plenty of spaces explicitly meant for community tech support. In OPs case, I’ll say the title doesn’t help and asking an LLM for advice on a topic you’re unfamiliar with (and not second-guessing the commands you paste into the terminal) is such a bad idea that it really can’t be understated. I regularly catch some of my colleagues making AI-assisted mistakes and they’re professionals who genuinely know better. This shit shouldn’t ever be recommended as a learning tool for beginners without some kind of supervision or guard rails to ensure you’re not being gaslit.