Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: DFS <nospam@dfs.com>
Newsgroups: comp.os.linux.advocacy
Subject: Re: Does Dimdows Know What Time It Is?
Date: Tue, 15 Oct 2024 11:27:02 -0400
Organization: A noiseless patient Spider
Lines: 64
Message-ID: <vem1k3$1oip5$1@dont-email.me>
References: <vda0ko$1e457$1@dont-email.me> <vdc82s$1rmvl$1@dont-email.me>
 <hwmKO.36384$afc4.11514@fx42.iad> <vddgqf$24oap$1@dont-email.me>
 <bfyKO.37639$afc4.24519@fx42.iad> <vdg0pn$2k2ps$1@dont-email.me>
 <bmSKO.243830$v8v2.80772@fx18.iad>
 <pan$c95bb$cbe518b0$39a1d215$2736670b@linux.rocks>
 <vdhmn3$2sase$2@dont-email.me> <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>
 <vefqv3$j3k2$4@dont-email.me> <vegirs$mqnt$1@dont-email.me>
 <vekulr$1jctr$4@dont-email.me> <NItPO.213882$1m96.98964@fx15.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 15 Oct 2024 17:26:59 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="7687e8f1c66d535999c161cfa22e1e83";
	logging-data="1854245"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/KhI2swJThnw6Hv2Jsek05"
User-Agent: Betterbird (Windows)
Cancel-Lock: sha1:7UAyk0gndbT2SGBSMUucYAOqGtQ=
Content-Language: en-US
In-Reply-To: <NItPO.213882$1m96.98964@fx15.iad>
Bytes: 4436

On 10/15/2024 9:01 AM, CrudeSausage wrote:
> Le 2024-10-15 à 01 h 30, Lawrence D'Oliveiro a écrit :
>> On Sun, 13 Oct 2024 09:44:27 -0400, DFS wrote:
>>
>>> On 10/13/2024 2:56 AM, Lawrence D'Oliveiro wrote:
>>>>
>>>> On Sat, 12 Oct 2024 19:51:52 -0400, DFS wrote:
>>>>
>>>>> You've been able to read the Registry since the beginning with VB/A or
>>>>> C# or C++.
>>>>
>>>> With special APIs. Normal file-manipulation commands cannot be used
>>>> with the Registry.
>>>
>>> No duh.  It's not a normal file.
>>
>> Funny, weren’t you trying to claim earlier that the Registry could indeed
>> be manipulated as easily as Linux config files?
> 
> That claim would be erroneous. 

I never made that claim, or anything like it.

Larry Duh's lie about me is erroneous.  He said it was impossible to 
compare the current Registry settings to previous ones, or make comments 
in the Registry about changes you made.  Both are possible, so I 
corrected him.  Now he's lying about what I said.

I expect nothing less than such Snittish behavior from Linux lusers.



> The mere fact that you have no idea where 
> to go in the registry to find the configuration of a particular setting 
> speaks volumes. 

You very very rarely have to visit the crazed monstrosity MS calls the 
Registry.  Your app settings are almost always made via a GUI, which is 
a superior way to configure software.

Example: open SumatraPDF.  Go to menu | Settings | Advanced Options. 
It's a joke (like the slrn config file).  It tells you to go to a 
website for documentation.  Every one of those settings should be on a 
GUI with checkboxes, dropdowns and textboxes, grouped together 
logically, with onscreen documentation and/or a mouse tip that shows up 
when you hover.

GUI config screens should, and usually do, read a configuration text 
file when they open, and write it when you click Save.



> They purposefully made the registry difficult to 
> navigate with entries like fff34sSFD2232--11 that there is no denying 
> Linux is much easier.

Google Generative AI says "The Windows Registry sometimes uses seemingly 
obfuscated names for keys as a security measure to make it harder for 
malicious actors to easily locate and manipulate sensitive data stored 
within the registry, especially when combined with techniques like using 
null characters to hide entries from standard registry editors, 
effectively creating a layer of obscurity that requires more advanced 
tools to access and modify."