I’ve used Linux for 25 years now and I remember every time when back then people needed help with windows it was always "go to the registry editor and add the key djrgegfbwkgisgktkwbthagnsfidjgnwhtjrtv in position god-knows-where to fix some stupid windows shit. that, apparently, made windows user ready
On Linux I’d have to edit an English language file and add an English word and that meant it wasn’t user ready
How was the gnome registry some how worse? Microsoft didn’t even have a document that could describe how theirs worked, much less an organizational structure. At least Gnomes was basically simple words and categories. And they built a settings manager for it too.
Not that I use gnome much, but still this is silly.
I know this is linuxmemes, but if you want a serious answer, I can provide, lol.
It’s worse because it is an amateurish attempt at recreating windows like registry (like most things Gn*me lol).
boring technical details
Let’s start from the top:
Microsoft didn’t even have a document that could describe how theirs worked
Oh, really, I remember reading enormous amounts of info on MSDN describing how the internal registry hives work in 1998 (yes, I am that old lol) Also, there were/are excellent books on the topic, i.e. “Windows Internals” by Mark Russinovich. Can you tell me where I can find more info on how dconf works, what about dconf internal structure and organization? I don’t want to read the source code.
At least Gnomes was basically simple words and categories
Right, can you tell me what this dconf dump is about:
You mean like simplified UI for poor man’s regedit?
Windows registry is horribly over-engineered very very high performance binary database (dconf is a Gvariant binary db also, lol) deeply integrated within the NT kernel and overall system, it supports access virtualization, transparent path override, robust ACLs, and more. IMO, M$’ biggest mistake was allowing 3rd party access to the hive in the early days. Then backwards compatibility kicked in and the rest is history.
Don’t get me wrong it sucks, massively, but this attempt of Gn*me/freedesktop INI db is a joke, like the OP’s argument
I couldnt use linux on my laptop 15 years ago because suspend never seemed to work. Just tried it again last week on my generic desktop, suspend still not working. So ya linux has come a long way. Still cant use it.
Just installed KDE neon on two HP laptops and I might be mistaken but I do think they’re both asleep right now. I’ll check back on that later but usually it’s a bad hardware issue that can be rectified with some kernel parameters.
Implying suspend works on Windows either. I’ve got like a 50/50 chance my monitor connected with DisplayPort actually gets signal after waking on Windows. This shit has been a problem for a long time.
Ive been using windows 30 years and linux for 20, Ive never seen windows fail at suspending on any system in that time. Linux on the other hand Ive never seen it reliably suspend on any system. Dont get me wrong I want to use linux at home very badly, but none of the fixes I have looked into have solved the problem. Its a 100% required feature for me.
I had to implement a GPO to disable suspend on windows 10 AND 11 for everyone at my company equipped with HP zbook laptops because it was requiring a hard reset every… Single… Time.
With our HP laptops they would work perfectly so long as you only ever used them with one brand of dock. If you mixed dock brands without doing a full restart (like say having one brand at home, suspending, and then using another brand’s dock at the office) Wi-Fi, suspend, and several other features would no longer work or work intermittently. We had HP and Targus working on it, even their engineers were puzzled.
An HP by any chance? These don’t handle suspend well and you need to add a parameter or three at boot via grub (or systemd too). Otherwise the system gets tied up filling the log endlessly with rapidly cycling pcie errors and you end up crashing or frozen pretty quickly. If this might be your problem, see
Where there’s a problem there’s usually a solution, you just might need to root around the web for answers.
Thats a huge problem for linux, average users are never going to do that. But as a long time linux user myself I have been trying to find solution to the suspend problem for a long time and I still cant find one. So Id say its a big problem.
I’ve used Linux for 25 years now and I remember every time when back then people needed help with windows it was always "go to the registry editor and add the key djrgegfbwkgisgktkwbthagnsfidjgnwhtjrtv in position god-knows-where to fix some stupid windows shit. that, apparently, made windows user ready
On Linux I’d have to edit an English language file and add an English word and that meant it wasn’t user ready
Yeah, Linux was ready long ago
Right, that’s the reason alright, lol. Remember dconf on Gn*me? It’s like registry on windows, but worse.
No, Linux is still not ready for desktop, and it has nothing to do with this fallacy of yours.
I used Linux desktop for 25 years now and I never used Gnome, what is your point?
How was the gnome registry some how worse? Microsoft didn’t even have a document that could describe how theirs worked, much less an organizational structure. At least Gnomes was basically simple words and categories. And they built a settings manager for it too.
Not that I use gnome much, but still this is silly.
I know this is linuxmemes, but if you want a serious answer, I can provide, lol. It’s worse because it is an amateurish attempt at recreating windows like registry (like most things Gn*me lol).
boring technical details
Let’s start from the top:
Oh, really, I remember reading enormous amounts of info on MSDN describing how the internal registry hives work in 1998 (yes, I am that old lol) Also, there were/are excellent books on the topic, i.e. “Windows Internals” by Mark Russinovich. Can you tell me where I can find more info on how dconf works, what about dconf internal structure and organization? I don’t want to read the source code.
Right, can you tell me what this dconf dump is about:
[org/gnome/nm-applet/eap/fea8b3cc-21a2-4a3d-a3bb-72b7459247b7] check-time=uint32 1742505110You mean like simplified UI for poor man’s regedit?
Windows registry is horribly over-engineered very very high performance binary database (dconf is a Gvariant binary db also, lol) deeply integrated within the NT kernel and overall system, it supports access virtualization, transparent path override, robust ACLs, and more. IMO, M$’ biggest mistake was allowing 3rd party access to the hive in the early days. Then backwards compatibility kicked in and the rest is history.
Don’t get me wrong it sucks, massively, but this attempt of Gn*me/freedesktop INI db is a joke, like the OP’s argument
I couldnt use linux on my laptop 15 years ago because suspend never seemed to work. Just tried it again last week on my generic desktop, suspend still not working. So ya linux has come a long way. Still cant use it.
Just installed KDE neon on two HP laptops and I might be mistaken but I do think they’re both asleep right now. I’ll check back on that later but usually it’s a bad hardware issue that can be rectified with some kernel parameters.
Implying suspend works on Windows either. I’ve got like a 50/50 chance my monitor connected with DisplayPort actually gets signal after waking on Windows. This shit has been a problem for a long time.
Ive been using windows 30 years and linux for 20, Ive never seen windows fail at suspending on any system in that time. Linux on the other hand Ive never seen it reliably suspend on any system. Dont get me wrong I want to use linux at home very badly, but none of the fixes I have looked into have solved the problem. Its a 100% required feature for me.
I had to implement a GPO to disable suspend on windows 10 AND 11 for everyone at my company equipped with HP zbook laptops because it was requiring a hard reset every… Single… Time.
No amount of bios upgrade ever fixed the issue.
With our HP laptops they would work perfectly so long as you only ever used them with one brand of dock. If you mixed dock brands without doing a full restart (like say having one brand at home, suspending, and then using another brand’s dock at the office) Wi-Fi, suspend, and several other features would no longer work or work intermittently. We had HP and Targus working on it, even their engineers were puzzled.
Problem was non-existent on Linux…
An HP by any chance? These don’t handle suspend well and you need to add a parameter or three at boot via grub (or systemd too). Otherwise the system gets tied up filling the log endlessly with rapidly cycling pcie errors and you end up crashing or frozen pretty quickly. If this might be your problem, see
https://askubuntu.com/questions/863150/pcie-bus-error-severity-corrected-type-physical-layer-id-00e5receiver-id
And
https://www.reddit.com/r/pop_os/comments/yh3nkw/freezing_issue_finally_solved_here_is_how/
Where there’s a problem there’s usually a solution, you just might need to root around the web for answers.
Thats a huge problem for linux, average users are never going to do that. But as a long time linux user myself I have been trying to find solution to the suspend problem for a long time and I still cant find one. So Id say its a big problem.