Path: not-for-mail
From: DFS <nospam@dfs.com>
Newsgroups: comp.os.linux.advocacy
Subject: Re: Does Dimdows Know What Time It Is?
Date: Sun, 13 Oct 2024 00:00:35 -0400
Organization: A noiseless patient Spider
Lines: 60
Message-Id: <vefgl1$hb32$1@dont-email.me>
References: <t41LO.34727$rIH3.25125@fx40.iad> <vdje0h$37qau$3@dont-email.me> <gfbLO.276631$FzW1.145242@fx14.iad> <vdjgsm$37qau$9@dont-email.me> <xLbLO.69482$2nv5.49161@fx39.iad> <vdm399$3nim2$1@dont-email.me> <lm84ndFlrc3U6@mid.individual.net> <vdmp8s$3r1an$3@dont-email.me> <lm9ccbFrnk8U5@mid.individual.net> <vdo3rs$4q92$5@dont-email.me> <vdorab$7tam$1@dont-email.me> <vdpk92$bgk6$15@dont-email.me> <vdrm8u$pveo$4@dont-email.me> <vecabb$3r6ms$4@dont-email.me> <vef22n$bn0e$3@dont-email.me> <v73mgj1qml41ci4os5c2dcttdngbo8qpm1@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 13 Oct 2024 06:00:34 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="1daa06f0a2d44444791022deae0f7c58"; logging-data="568418"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1979RinBCQbNFssf4KxuLoM"
User-Agent: Betterbird (Windows)
Cancel-Lock: sha1:sd/6/sn6fhPC6NHpljw+0JTDSsk=
Content-Language: en-US
In-Reply-To: <v73mgj1qml41ci4os5c2dcttdngbo8qpm1@4ax.com>

On 10/12/2024 8:01 PM, Joel wrote:
> DFS <nospam@dfs.com> wrote:
>> On 10/11/2024 6:54 PM, Lawrence D'Oliveiro wrote:
>>
>>> Question to ponder: Why did Microsoft feel the need to add the feature to
>>> PowerShell to be able to browse the Registry as though it were a
>>> filesystem?
>>
>> Not sure what your point is.
>>
>> You've been able to read the Registry since the beginning with VB/A or
>> C# or C++.
>>
>> I was manipulating the Windows Registry nearly 20 years ago with Access VBA.
> 
> 
> All of this garbage is conforming to M$'s standards, failing to have a
> rational setup, this is why I call it "Winblows", it's bloated, hefty,
> it's a drag on a computer.  It's a jack of all trades that I just
> don't relate to.


An editable central registry of app and OS configuration entries isn't a 
bad thing, but the MS implementation is fubar.

Look at the complexity they created:

https://learn.microsoft.com/en-us/windows/win32/sysinfo/registry-functions


In practice, a user rarely sees or knows anything about the Registry. 
But sometimes you have to edit/delete/create a key to fix a MS bug or do 
something else.  Then you notice the mess.

Here's a stupid key name:
Computer\HKEY_CLASSES_ROOT\AppX4jbzrhvphxte25e0gxha6bq555nrgqzy

And here's a stupid subkey named 'FriendlyTypeName':
@{Microsoft.XboxGameCallableUI_1000.22621.1.0_neutral_neutral_cw5n1h2txyewy?ms-resource://Microsoft.XboxGameCallableUI/resources/PkgDisplayName}

The CLASSES_ROOT hive stores file extension associations (and a bunch of 
other shit):

https://imgur.com/a/DCeUerw

Look at that!  There's so much bullshit in there that I'm going to 
reinstall Win11 soon, just to clean it out.  I HATE HATE HATE this kind 
of mess being on my computer, but I just can't abide the GuhNoo 
hobby-crapware you're forced to use with Linux.  So I'll have to stick 
with Windows.


MS says the max Registry size for an x64 system is "50 percent of 
physical memory, up to 1.5 GB."  1.5GB for what should be a few text 
entries, but instead becomes an impenetrable, unreadable, 
little-documented monstrosity.


If anyone cares:
https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/windows-registry-advanced-users