News for hackers. Stuff that matters.
Re:Why the Windows Registry sucks technically (2010) by int_19h on Friday July 29, 2022 @08:18PM (#32283142)
It should be noted that putting configuration into files rather than registry has been the standing recommendation on Windows for a very long time now. For example, .NET 2.0 (2005) added a standard facility for application settings, and it was implemented on top of XML .config files.
Re:Why the Windows Registry sucks technically (2010) by nikau on Saturday July 30, 2022 @02:35AM (#32284806)
Good to see MS practising what they preach on newly written applications:

https://docs.microsoft.com/en-us/deployedge/configure-micros...

> You can also use REGEDIT.exe on a target computer to view the registry settings that store group policy settings. These policy settings are located at this registry path: HKLM\SOFTWARE\Policies\Microsoft\Edge.

Re:Why the Windows Registry sucks technically (2010) by int_19h on Saturday July 30, 2022 @05:16AM (#32285408)
This is a group policy, not a setting. That makes a big difference in the right context - policies are meant for things that are typically centrally managed in enterprise environments, so the ability for the admin to remotely control every setting individually is important, and requires some kind of central system registry for OS tooling to work with.
Re:Why the Windows Registry sucks technically (2010) by nikau on Monday August 01, 2022 @03:26AM (#32303116)
Yep, but it still sucks if you are a user trying to figure out how a setting is applied, first delve into some seemingly proprietary config db for edge, and then realise its actually configured via a registry gpo.