“read the changes before installing a major update”

Obviously I dont think people need to read every change log for every piece of software. I do think its a good idea to read the release notes for a major update of your DE thought, since its the piece of software that is going to effect you the most.

And once it is no longer on and has become a setting, they can just remove the setting and force people to drop gsettings and then remove it completely.

What reason do they possibly have to do this? The setting already exists and is feature complete. It doesnt require maintenance. They also noted in the merge request that many RHEL users use it, so RedHat has a financial incentive not to remove it.

They could also instead ask people on first launch. Some people enable telemetry, so they will find out how many people prefer to keep it, which I bet will be most.

They could also just make it a setting. I really dont think it makes a big difference. They can also still use telemetry to see how many users enable it. Based on this thread, I really doubt it will be most.

The first time startup wizard should be kept relatively short and minimal. This just seems like a very unnecessary thing to include.

This is AI generated garbage with no sources.

This sub has been full of shitty clickbait headlines from this site.

It will break their workflow for a few seconds before they change the setting back. Or they could read the changes before installing a major update and change it before even doing anything.

Maybe in the future it will be added to the initial setup guide along with stuff like choosing if you want mouse acceleration, but I really dont think its that big a deal.

Do any DEs still have 1 click folder opening by default?

If you add the shortcut at the DE level it definitely should work in every program. Idk if Gnome actually let’s you bind copy and paste though.

It already is configurable, theyre just defaulting it to off. You will be able to turn it back on.

It’s very easy for a user to accidentally paste private or sensitive information somewhere dangerous if theyre unaware of this feature.

The FreeDesktop specification refers to this feature as an “easter egg”, and something like this should absolutely not be an easter egg.

This change would mean disabling it by default and adding a settings entry that actually explains it, making sure users are informed before they can accidentally use it.

And that is the exact reason that was given in the gnome merge request. A user being able to accidentally paste a bunch of text they didnt even know they’d copied incredibly design.

It’d be so easy for them to just add “by default” to the end of the title.

The project already has some paid options with more features: https://xpipe.io/pricing

AFAIK some HDMI to DP converters can be used to work around this. Since the converter is handling the VRR management in its own code, then converting it to DP, there’s no need for a FOSS implementation

deleted by creator

Duh, but now that this has replaced SDDM as the main login manager for plasma, Cachy will likely replace SDDM with it by default.

Yeah, I wasn’t trying to say SQLite is universally better. I shouldn’t have said best option, I really meant best default. I don’t think the majority of users are running a central db, most will just spin-up docker compose files for each service and end up with multiple SQL versions running.

I’ve had a lot of problems in the past from software crashes that left sqlite files in a corrupt state

I have had this issue, but it was always easily recoverable. I haven’t had the same issues with backups, although a lot of the software I use that’s running SQLite has a builtin backup feature, then I just backup that directory to a cloud service.

Besides that SQLite really doesn’t play nice with NFS, which is the basis for quite a few cloud storage providers. Also a good point, I just don’t think the majority of users are using NFS for their DBs.

When an app is using an ORM already, I think they might as well make sure it supports both SQLite and a hosted DB like Postgres

GNOME has plenty of features that are off by default and still exist. The merge request also mentions that redhat would 100% recieve complaints from paying customers if it was removed. Theyre very clearly aware that people still want this feature. You’re just assuming the worst.

They explicitly mention the plan to add a toggle in gnome settings in the merge request.

Idk how you could look at GNOME and say its trying to act more like Windows. They have their own particular idea of what a desktop should be, and that might not include middle mouse pasting. Defaults shouldnt stay the default just because they’ve always been. Devs should be able to have discussions about changing things without people accusing them of trying to destroy Linux.

Edit: I also want to point out that a huge number of Linux users dont even know this is a feature (some of which you can see in this thread). This change will add an entry in the settings for it, which very well might lead to MORE people using it. I think disabled is the correct default for something as potentially dangerous as dumping your most recently highlighted text.

This article is dogshit. Its clearly written to make it sound like theyre completely getting rid of it to get people pissed off at GNOME and Mozilla. The GNOME merge request has “by default” in the title, so its pretty damn obvious they’re not getting rid of it completely.

They are making it an option