Re: Microsoft Linux Distro

On 12/7/24 8:53 PM, vallor wrote:

On Sat, 7 Dec 2024 17:48:59 -0800, Alan <nuh-uh@nope.com> wrote in
<vj2tub$3dvrg$1@dont-email.me>:
 

On 2024-12-07 17:43, Joel wrote:

Alan <nuh-uh@nope.com> wrote:
>

I installed Linux *at the time*
that the time had come.  I got my 2 1/2 years with Winblows.

>
So you're both claiming it was a good purchase (implicitly)...
>
...AND calling it "Winblows".
>
Interesting.

>
Yeah, it ran fantastically for a couple years, then I moved on.

>
That doesn't jibe with calling it "Winblows".
>
I mean... ...it didn't change, right?

>
>
It *did* change, genius, what do you think those "cumulative updates"
are doing?

>
Really?
>
Is that what you're blaming this time?
>

   This
is probably common, among savvy computer users, who know that
Microsoft supports new hardware, but even the slightest aging makes
Linux the better choice.  And lo and behold, that's what I did.

As one who supports users of Windows (10, 11, and to a much lesser
extent, earlier versions), I can tell you that the problem is NOT
aging hardware.
>
But you in your technical incompetence wouldn't have figured that out.

>
>
Maybe you're tolerant of hard drives and slow SSDs booting modern
Winblows, I don't know, that's your headache.  I'm going to keep being
a pioneer of great computing, proudly showing how Linux makes a machine
worth something.

>
Nope.
>
I know how to SOLVE those issues.
>
I make my living solving those issues.

 Have you ever booted the Microsoft Linux distribution?
 (fu2: cola)

What's interesting is that the hardware that I'm currently running Windows on is now just over two years old and ... should I be jealous of Joel because even with MS's updates, I've not noticed any slowdown?
Do I have to wait until its 2.5 years or something?  Or is it that by being totally on auto-pilot that I'm preventing Windows OS from getting mucked up by the meddling of little l33t fingers?
Ob Linux:
Been spending time today with verifying auto-updates to de-risk some zero day vulnerabilities on my linuxen boxes.  While doing so, found an anomaly in their email self-reporting alert system (one's working, another's not).  Looks solvable, but haven't quite gotten to it yet; need to sort out an expired Certificate issue too to probably do so.
-hh