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.
“read the changes before installing a major update”
As if people have the time to read the changelogs for every single package all the time… 🙄
This is pretty important on a server to avoid disruptions and outages, but people have other things to do.
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.
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.
“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.
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.
“read the changes before installing a major update”
As if people have the time to read the changelogs for every single package all the time… 🙄
This is pretty important on a server to avoid disruptions and outages, but people have other things to do.
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.
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.
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.
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 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.