C has not aged well, despite its popularity in many applications. I’m grateful for the incredible body of work that kernel developers have assembled over the decades, but there are some very useful aspects of rust that might help alleviate some of the hurdles that aspiring contributors face. This was not a push by rust evangelists, but an attempt to enable modernization efforts at least for new driver development. If it doesn’t work out, that’s fair enough but I’m grateful for the willingness - especially of Linus - to try something new.

That’s not entirely accurate. Google’s influence on the web has grown even beyond the web browser engine majority share (which is bad enough in itself). They offer one of the most popular web frameworks and run several of the most popular websites. There is almost no way to compete when the market leader is simultaneously the developer and the major user of new features. Of course everyone else is going to switch to using your browser engine. What else are they gonna do? There are even websites now that just check the user agent string and refuse service if you don’t use a chromium based browser. Shit’s fucked.

Maybe a fixed line-height?

The only thing that’s slow is dnf’s repository check and some migration scripts in certain fedora packages. If that’s the price I need to pay to get seamless updates and upgrades across major versions for nearly a decade, then I can live with that.

I tried using connman to setup a wireguard connection once. It was not a good experience and ultimately led nowhere, due to missing feature support.

If anything, he gets most of his inspiration from MacOS.

Fuck Creative. Letigious patent troll is the whole reason why 3D audio in games was stuck in the dark ages technologically for the longest time.

The joke in the OP stops at the beginning of the joke explanation. If you just share your honest opinion like that in a shitposting community, you can’t expect everyone to “play along” with your “joke”.

It will probably just work, even if not officially. If any weird Windows issues crop up, Microsoft may or may not fix them. I think AMD even provided workarounds and special drivers for Windows 7, just without any official support. They may not do that this time around though, since a lot of things have changed.

Try to imagine that argument but coming from some government you really dislike. I can think of a lot of different media that might inspire violence and instability, but which would be really important for people to see or at least know about. Frankly, anyone who doesn’t see that as a potential problem is being shortsighted and really needs some historical perspective, in my opinion.

Always men never women but that might have been cause the high-school was all male.

???

I have a very slight suspicion that might be the reason. Not willing to call it just yet, though.

There are two ways to save your work in either program. You can save your actual work, so you can continue editing at some point and not lose stuff like layers, image quality and other information or you can export your work into some kind of image file, optionally compressing it and discarding extra information about the project. I think GIMP even offers a shortcut for this called “Overwrite …”. How is this an issue?

wayland doesn’t seem to support nvidia as well as X does, just due to development focus

Ymmv with Nvidia, but that has nothing to do with development focus and everything to do with Nvidia’s refusal to use the same interfaces Intel and AMD use. Most of the way Nvidia works or doesn’t work with X or Wayland is down to Nvidia’s driver stack. Personally I’ve not had much positive experiences with Nvidia on X.

Like yes major releases and distros are moving to wayland now, that just means they find it stable enough to start doing development on it.

That happened literal years ago. The reason you’re only noticing now, might be because KDE has gotten their Wayland implementation to a reasonably stable point. Gnome has supported Wayland for some time now and other DEs probably don’t have the resources to move on from X. I don’t see the distros that are only switching over now as major contributors to any development specific to Wayland.

I don’t take issue with your preferences. Maybe you’re better off with X for now, that’s fine, but you make it sound like Wayland is just full of issues and has barely even entered some kind of pre-release state for software masochists.

Except when X doesn’t fucking work ™ and hasn’t properly worked in literal decades. I don’t think I’ve ever managed to get rid of horizontal tearing with X. Calling X feature complete is pretty funny, but it isn’t. So many things were never fully implemented, because it’s just an impossible amount of work or would require some major rearchitecting. You don’t have to deal with updates because literally no one wants to develop it any further or even maintain it. The devs have moved on to Wayland or other things.

It’s fine if it works for you, but I’m getting tired of Linux conservatives projecting their own experiences on everyone else and declaring Wayland as “not ready yet” and handwaving all of X’s obvious problems away because they’re used to dealing with them. I’ve used Wayland as a default for all my machines for years. After a rough beginning where major features were still in development, now it works. XWayland works. Native Wayland apps work. I don’t have tearing anymore. I’m not going to pretend that that’s the universal experience, but a lot of people are using it just fine right now.

Then trying to nag you into saving it to some unknown unused bizarre gimp extension.

You mean saving a project file? The same way you’d save a PSD file in PS, so you can actually save all your layers and go back to make an edit? It’s been a while since I’ve used Photoshop, but I’m pretty sure both GIMP and PS offer two different workflows of saving/exporting your work and they are just named differently and have different keybinds. I have no idea how you can act like you actually tried to use GIMP as something other than a drop-in replacement for PS, but then call the default GIMP project file format “unknown, unused and bizarre”…

I want to do that, but not because of Flatpak. That’s incredibly far down the list of things I find offensive in my professional life. At the very least it does fulfill some sort of purpose and also doesn’t cost any money to use.

Website scanning for malware or other undesirable content is extremely unreliable and prone to false positives. None of the three vendors are very well known (except for a few other reports of false positives). If anything that’s a pretty low hitrate on virustotal all things considered. Don’t put too much stock in the heuristics of companies whose business model revolves around scaring their customers and exploiting computer illiteracy.

Big news (from 2017): debian held back software features because someone doesn’t like the new way of doing things. Let’s blame systemd for this unprecedented case.

What’s wrong with giving access to the specific sudo command, as suggested in the other answers?

You could not have worded that more condescendingly. The issue here is that Rust is singled out for no more apparent reason than making for a clickbaity headline. The underlying Windows API function requires undocumented escaping to prevent this exploit, Microsoft won’t fix that because it breaks compatibility, pretty much every programming language with a standard library that provides access to it is affected - Java won’t even fix it, others have updated their documentation. Rust is the first to actually implement a fix for a vulnerability that’s ultimately caused by Windows and gets called out for it for some reason. Of course people are going to get defensive about it. As they do every time a stupid headline gets published.

Having really dry skin does not help with grip.