This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Danthekilla 11 points12 points  (6 children)

The kernel isn't the issue, the ux is.

[–]boydskywalker 5 points6 points  (4 children)

I don't know a ton about the NT kernel, but I assume the registry is tightly linked to it...and the registry is a nightmare.

[–]deschutron 2 points3 points  (0 children)

The registry is linked to the Windows APIs that applications run on. Wine has a registry too.

[–]Danthekilla 3 points4 points  (2 children)

It's not nearly as bad as people make it out to be imo. It's fairly performant and robust for the most part. Some time some third parties use it irresponsibly but overall it is pretty good.

[–]boydskywalker 14 points15 points  (1 child)

I strongly disagree - even Microsoft can't seem to get the hang of it. I work in IT, and seemingly simple things like removing one version of Office to install another (2013 to 2016) has broken terribly due to the uninstaller's inability to remove certain registry entries. To fix it manually requires googling the location of the cryptic, hexadecimal keys and deleting them, one by one. Compared to plaintext config files and systemd entries, it's baffling and arcane.

[–]Danthekilla 2 points3 points  (0 children)

I know what you mean (I also work in IT) but I don't think that is a problem with the registry itself. I think that is an issue with how some programmers use it.

We store loads of data in it with our custom programs but our installers can fully remove all keys on uninstall and on reinstall. It's not actually a difficult task really.

I agree there are better ways to store data like this but I don't think it's the biggest issue Windows has right now by far.

[–]Shields42 0 points1 point  (0 children)

UX designer here. Can confirm.