Hacker News Reader

Comment by bitcharmer | Hacker News Reader

I've been a very faithful Ubuntu user for 12 years now but if there's no easy way to disable this abomination then my current one (18.04) will be the last. Whose idea was it to replicate one of the worst features of Windows?

View on HN

Gnome has been replicating the worst parts of windows (the registry comes instantly to mind) since the release of Gnome 3.

gconf is like the windows registry how? is it just because its a centralized config store? how evil is an annotated, easy to use, non archaic file that some apps put their settings into?

it must be evil because Microsoft did it. Weird that they copied everything else Windows did and people didn't mind.

There's way more evil things about Windows, like click to raise and menu bars.

Evil, huh?

A centralized location for GNOME config has always been present since GNOME 2 (maybe earlier, but 2 was when I started with GNOME). See, for example, this page https://www.linuxtopia.org/online_books/linux_desktop_guides...

dconf is now a binary format though.

I think gconf and macOS's plist have proven that Microsoft is at least somewhat right with registry, or at least the idea is. I don't know why people didn't like it and honestly I don't have a strong opinion on it, but I have a feeling in some ways Microsoft didn't have much of choice given that they need to have backwards compatibility.

I was warned far more than necessary about corrupting The Holy Windows Registry Hive, I think that’s the entirety of the problem with it.

it's handy for config, sure. but it has several downsides. very opaque compared to a config file.. keys can't have comments. the average user has no idea what a "dword" is. some registry paths are obscenely long. you can accidentally break one program or windows trying to edit another's settings. and i'm not sure currently, but a big problem in the past was uninstallers didn't remove registry keys reliably.

personally, i think XDG_CONFIG_HOME + a robust config file framework with a standardized format (yaml/toml, whatever) would work as well. being able to specify a schema could be extremely useful, too, to prevent borked configs. as you've said, we've seen a lot of tools/OS's go this direction. and it doesn't have to be perfect, the 80% case would be a huge improvement.

i'm also sure the registry made a lot of sense at the time. it was probably way quicker than reading and parsing files. we didn't care so much about sandboxing/isolation and backing up. people probably had less application installed.

18.04 is supported for three more years. Maybe that will be my Ubuntu countdown.

18.04 has a ten year extended security maintenance life AFAIK, so you could stretch to 2028.

Wow, that's seriously impressive if true.

As many others I haven't liked vanilla Ubuntu since they swapped Gnome 2 for a (what I think is a) clone of the Mac OS interface, but my desktop still uses the Ubuntu 18.04 base system under the hood so this might come in handy for a number of people like me.

Ubuntu security updates do not cover the universe repository, which contains the largest number of packages. The universe repo is 'community-supported', which means that a lot of CVEs are not fixed in practice.

https://people.canonical.com/~ubuntu-security/cve/universe.h...

So, Ubuntu's LTS support is only relevant security-wise if you mostly stick to the main repository.

Anyone have any idea what Debian's LTS security posture looks like? Is it also restricted to 'main' and does it also ignore 'contrib' and 'non-free'?

However most packages in Debian are in main. AFAIK contrib is for FLOSS packages that somehow depend on packages that are not FLOSS.

Reply on news.ycombinator.com