• Re: Thanks Microsoft!

    From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Mon Nov 2 23:30:22 2026
    From Newsgroup: comp.os.linux.advocacy

    On Mon, 02 Nov 2026 17:49:12 +0000, Nick Charles wrote:

    Microsoft ... are desperate to get as many people running Windows 11
    as possible.

    If that were true, why do they let the quality of Windows updates keep deteriorating so badly? Seems every other month some rCLfixrCY for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    If you look at their last financials, theyrCOve regrouped things so the
    whole Windows business is now lumped together in a division that
    includes Xbox, search and advertising -- in other words, the also-rans
    -- that in total account for only 17% of the companyrCOs total revenues.
    The outlook for Windows revenue, according to the CFO, is to keep
    falling for the next year.

    WhererCOs the rest of the money coming from? Cloud, mainly. The Azure
    business alone is over twice the size of the above Windows-including
    division. And MicrosoftrCOs cloud business is primarily built on Linux.

    The conclusion is inescapable: Linux is now more important to
    Microsoft than Windows.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rod Speed@rod.speed.aaa@gmail.com to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Tue Nov 3 15:57:01 2026
    From Newsgroup: comp.os.linux.advocacy

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote
    Nick Charles wrote
    Microsoft ... are desperate to get as many people running Windows 11
    as possible.
    If that were true, why do they let the quality of Windows updates keep> deteriorating so badly? Seems every other month some rCLfixrCY for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.
    Never seen that, let alone every other month
    If you look at their last financials, theyrCOve regrouped things so the
    whole Windows business is now lumped together in a division that
    includes Xbox, search and advertising -- in other words, the also-rans> -- that in total account for only 17% of the companyrCOs total revenues.
    The outlook for Windows revenue, according to the CFO, is to keep
    falling for the next year.
    WhererCOs the rest of the money coming from? Cloud, mainly. The Azure business alone is over twice the size of the above Windows-including division. And MicrosoftrCOs cloud business is primarily built on Linux.
    The conclusion is inescapable: Linux is now more important to
    Microsoft than Windows.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsQ==?=@winstonmvp@gmail.com to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Tue Nov 3 02:27:57 2026
    From Newsgroup: comp.os.linux.advocacy

    On 11/02/26 9:57 PM, Rod Speed wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote
    Nick Charles wrote

    Microsoft ... are desperate to get as many people running Windows 11
    as possible.

    If that were true, why do they let the quality of Windows updates keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Never seen that, let alone every other month

    If you look at their last financials, theyrCOve regrouped things so the
    whole Windows business is now lumped together in a division that
    includes Xbox, search and advertising -- in other words, the also-rans
    -- that in total account for only 17% of the companyrCOs total revenues.

    The outlook for Windows revenue, according to the CFO, is to keep
    falling for the next year.

    WhererCOs the rest of the money coming from? Cloud, mainly. The Azure
    business alone is over twice the size of the above Windows-including
    division. And MicrosoftrCOs cloud business is primarily built on Linux.

    The conclusion is inescapable: Linux is now more important to
    Microsoft than Windows.

    Microsoft Azure's 'Cloud business'(i.e. infrastructure) Azure powering 60%(latest estimate) of its virtual machine cores is run on Linux.
    ...but it's Microsoft's own built open-source Linux distro.
    - doing so was smart providing support for Microsoft products and all
    major 3rd-party Linux distros.
    --
    ...w-i|#-o-#-n|#
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Tue Nov 3 20:05:14 2026
    From Newsgroup: comp.os.linux.advocacy

    On 11/3/2026 7:30 AM, Lawrence DrCOOliveiro wrote:
    On Mon, 02 Nov 2026 17:49:12 +0000, Nick Charles wrote:

    Microsoft ... are desperate to get as many people running Windows 11
    as possible.

    If that were true, why do they let the quality of Windows updates keep deteriorating so badly? Seems every other month some rCLfixrCY for some problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    If you look at their last financials, theyrCOve regrouped things so the
    whole Windows business is now lumped together in a division that
    includes Xbox, search and advertising -- in other words, the also-rans
    -- that in total account for only 17% of the companyrCOs total revenues.
    The outlook for Windows revenue, according to the CFO, is to keep
    falling for the next year.

    WhererCOs the rest of the money coming from? Cloud, mainly. The Azure business alone is over twice the size of the above Windows-including division. And MicrosoftrCOs cloud business is primarily built on Linux.

    The conclusion is inescapable: Linux is now more important to
    Microsoft than Windows.

    Isn't that a good reason to ditch Linux?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From CrudeSausage@crude@sausa.ge to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Tue Nov 3 12:03:37 2026
    From Newsgroup: comp.os.linux.advocacy

    On 2026-11-03 7:05 a.m., Johann 'Myrkraverk' Oskarsson wrote:
    On 11/3/2026 7:30 AM, Lawrence DrCOOliveiro wrote:
    On Mon, 02 Nov 2026 17:49:12 +0000, Nick Charles wrote:

    Microsoft ... are desperate to get as many people running Windows 11
    as possible.

    If that were true, why do they let the quality of Windows updates keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    If you look at their last financials, theyrCOve regrouped things so the
    whole Windows business is now lumped together in a division that
    includes Xbox, search and advertising -- in other words, the also-rans
    -- that in total account for only 17% of the companyrCOs total revenues.
    The outlook for Windows revenue, according to the CFO, is to keep
    falling for the next year.

    WhererCOs the rest of the money coming from? Cloud, mainly. The Azure
    business alone is over twice the size of the above Windows-including
    division. And MicrosoftrCOs cloud business is primarily built on Linux.

    The conclusion is inescapable: Linux is now more important to
    Microsoft than Windows.

    Isn't that a good reason to ditch Linux?

    The best reason to ditch Linux would be the fact that embracing and propagating idiotic, woke ideas is more important than producing a
    decent product to its main developers.
    --
    CrudeSausage
    MacBook Air M4 Sky Blue
    iPhone 13
    Friendly Apple zealot
    Microsoft encourages its employees to transition their children <https://shorturl.at/wb5wM>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From JJ@jj4public@gmail.com to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 09:53:33 2026
    From Newsgroup: comp.os.linux.advocacy

    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence D Oliveiro wrote:

    If that were true, why do they let the quality of Windows updates keep deteriorating so badly? Seems every other month some |fixi for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't. Because without bugs, there won't be updates except for new features which they're reluctantly giving. Without updates, the OS won't look "fresh", "maintained", and "supported". They intentionally add more bugs to keep that status.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsQ==?=@winstonmvp@gmail.com to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Tue Nov 3 22:01:56 2026
    From Newsgroup: comp.os.linux.advocacy

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If that were true, why do they let the quality of Windows updates keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't. Because without bugs, there won't be updates except for new features which they're reluctantly giving. Without updates, the OS won't look "fresh", "maintained", and "supported". They intentionally add more bugs to keep that status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities.
    --
    ...w-i|#-o-#-n|#
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 00:32:29 2026
    From Newsgroup: comp.os.linux.advocacy

    On Wed, 11/4/2026 12:01 AM, ...w-i|#-o-#-n|# wrote:
    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If that were true, why do they let the quality of Windows updates keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't.
    Because without bugs, there won't be updates except for new features which >> they're reluctantly giving. Without updates, the OS won't look "fresh",
    "maintained", and "supported". They intentionally add more bugs to keep that >> status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to existing or new code for functionality, features or vulnerabilities.



    The W11 OS, may have on the order of 50-60 million lines of code.
    If you scanned for everything, at one defect per thousand lines of
    code, that would be "50,000 bugs of all types".

    The current machine scans are looking for exploits, of which
    1400 or so were patched in the last Patch Tuesday. The machine
    scans were not being done for "ordinary bugs". Bugs have to be
    separated via P.R analysis, as Feature Requests, Actual Bugs,
    Exploits, and WONTFIX as examples. Then people work on those
    according to the priority of them. At my work, as a hardware
    engineer, I sat in on a few P.R. sorting meetings, and I was
    shocked to learn how they treated that stuff (cavalier, is an
    understatement). But this is all part of the business, sorting
    the things that matter most, from the things that were merely
    submitted to annoy.

    And a lot of things are handled in the OS in two steps. That
    can include an Emergency Patch to stop an instantaneous problem,
    plus a "followup patch" that fixes the rest of it properly.
    You should not assume when they fix 1400 things, that each
    one of those was a one-and-done. On purpose, there could be
    multiple steps involved.

    Software always has "hot spots". There are modules in Windows,
    that when you open them, breaking something is almost guaranteed
    (File Explorer). The Kernel is a hot spot, in terms of exploits
    or performance issues. Practically every month that file needs a patch,
    just the same as Linux needs patching for its kernel stream.
    One other thing on Windows, was a GDI module (something associated
    with graphics). The current graphics stack has more component parts,
    than previous stacks. The people on the WSUSOffline site studied
    this stuff, as they had a set of patches intended to accelerate
    the process of tipping an OS upright (so it could patch itself
    faster). And that's why they, back in the day, had certain
    patches to be installed in a certain order. That's how, one day,
    I repaired Windows Update on a Vista install. Without that, I never
    could have figured that out on my own. At least today, the Windows Update subsystem works most of the time (using Cumulatives), whereas on
    older OSes the odds were not quite as good. On Vista, the busy icon
    on Windows Update, could basically spin forever. Unless you fixed it.

    By supporting only an x64 OS, now the machine has enough space
    that Windows Update is unlikely to run out of RAM.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 07:18:09 2026
    From Newsgroup: comp.os.linux.advocacy

    On Wed, 4 Nov 2026 00:32:29 -0500, Paul wrote:

    And a lot of things are handled in the [Windows] OS in two steps.
    That can include an Emergency Patch to stop an instantaneous
    problem, plus a "followup patch" that fixes the rest of it properly.
    You should not assume when they fix 1400 things, that each one of
    those was a one-and-done. On purpose, there could be multiple steps
    involved.

    That doesnrCOt really jibe with the reality that quite a few of those
    initial patches actually make things worse in some way. And this seems
    to be happening increasingly often.

    Software always has "hot spots". There are modules in Windows, that
    when you open them, breaking something is almost guaranteed (File
    Explorer). The Kernel is a hot spot, in terms of exploits or
    performance issues. Practically every month that file needs a patch,
    just the same as Linux needs patching for its kernel stream.

    The difference is, Linux is cleanly modularized, so you can fix
    problems in one area with minimal chance of causing unexpected
    problems in some seemingly unrelated place.

    By comparison, Windows is a crawling can of worms.

    One other thing on Windows, was a GDI module (something associated
    with graphics). The current graphics stack has more component parts,
    than previous stacks.

    The GUI shouldnrCOt be in the kernel. Even the graphics engine shouldnrCOt
    be in the kernel. All Linux has graphics-related in there is the
    lowest-level drivers and the rCLDirect Rendering ManagerrCY.

    All the rest is in userland. This is why it is easy to switch between
    an X11 server and a Wayland server -- you donrCOt need different kernels
    to do that.

    By supporting only an x64 OS, now the machine has enough space that
    Windows Update is unlikely to run out of RAM.

    Where was there another OS in the history of the world that could run
    out of RAM just doing an OS update??
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 02:52:21 2026
    From Newsgroup: comp.os.linux.advocacy

    On Wed, 11/4/2026 2:18 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 4 Nov 2026 00:32:29 -0500, Paul wrote:

    And a lot of things are handled in the [Windows] OS in two steps.
    That can include an Emergency Patch to stop an instantaneous
    problem, plus a "followup patch" that fixes the rest of it properly.
    You should not assume when they fix 1400 things, that each one of
    those was a one-and-done. On purpose, there could be multiple steps
    involved.

    That doesnrCOt really jibe with the reality that quite a few of those
    initial patches actually make things worse in some way. And this seems
    to be happening increasingly often.

    Software always has "hot spots". There are modules in Windows, that
    when you open them, breaking something is almost guaranteed (File
    Explorer). The Kernel is a hot spot, in terms of exploits or
    performance issues. Practically every month that file needs a patch,
    just the same as Linux needs patching for its kernel stream.

    The difference is, Linux is cleanly modularized, so you can fix
    problems in one area with minimal chance of causing unexpected
    problems in some seemingly unrelated place.

    By comparison, Windows is a crawling can of worms.

    One other thing on Windows, was a GDI module (something associated
    with graphics). The current graphics stack has more component parts,
    than previous stacks.

    The GUI shouldnrCOt be in the kernel. Even the graphics engine shouldnrCOt
    be in the kernel. All Linux has graphics-related in there is the
    lowest-level drivers and the rCLDirect Rendering ManagerrCY.

    All the rest is in userland. This is why it is easy to switch between
    an X11 server and a Wayland server -- you donrCOt need different kernels
    to do that.

    By supporting only an x64 OS, now the machine has enough space that
    Windows Update is unlikely to run out of RAM.

    Where was there another OS in the history of the world that could run
    out of RAM just doing an OS update??


    The supersedence calculation unpacks into RAM. What I see here, is
    the speed of processing it, may depend to some extent, on the size of
    L3 cache. That is part of ensuring a Cumulative, that can have
    a lot of packages in it, only the patches needed are installed.
    The install logic could have conditional statements of some sort
    in it.

    I found some discussion threads, where IT people in Enterprise setups,
    were getting help line calls from staff using Win7 SP1 on 2GB machines.
    That's all the RAM that the business, put in those PCs. When Windows Update scanner would run, it would use up all the RAM and the person sitting
    in front of the machine could not start a program at that point. The solution Microsoft came up with was clever -- they compressed the in-memory structures, then unpacked them on an as-needed basis. And this allows enough memory to be freed up, so user and WU could live in harmony.

    If you install 150 patches on a 32 bit machine, there is some RAM usage by WU, but each patch, as it installs, there is no particularly aggressive RAM
    cleanup between patches, and then, even with 3.25GB of memory available on
    the machine, it cannot finish all 150 of them. You can do them in smaller batches, to get past that. Running an older Win10 32-bit installation then, normally there would be few items to install. It's only if you do a clean install,
    you can (by being careless), schedule too many patches to be injected,
    for the available RAM. A 64 bit setup, does not have those sorts of issues.
    On 64-bit, you can "click something and walk away".

    The NVidia graphics driver, and the RealTek NIC driver, are containerized.
    And presumably run "close" to the kernel, but they are isolated. For
    some limited class of faults, you can see the Nvidia driver failing and
    placing a log entry on the machine, and this happens without affecting
    what is displayed on the machine. (That's because the driver instance,
    it's running, but the card it is controlling, might not be there
    any more.) Some other VPU recover operations (perhaps triggered
    by a Watchdog timeout), those do affect the display. While a normal
    recovery might be 1 second or so, when the OS "nearly died" it took
    a whole minute for the GPU driver to recover. I was pretty impressed
    by that, because it had that "it's dead Jim" look to it, but I just
    sat there, there was some flickering and it came back. I couldn't
    believe it really, as most of the time, activities like that end
    in a permanent black screen in only a few seconds. What it was doing
    for that minute, it's hard to guess.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 08:26:34 2026
    From Newsgroup: comp.os.linux.advocacy

    On Wed, 4 Nov 2026 02:52:21 -0500, Paul wrote:

    If you install 150 patches on a 32 bit machine, there is some RAM
    usage by WU, but each patch, as it installs, there is no
    particularly aggressive RAM cleanup between patches, and then, even
    with 3.25GB of memory available on the machine, it cannot finish all
    150 of them.

    That is a really stupid design.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Ahlstrom@OFeem1987@teleworm.us to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 06:50:28 2026
    From Newsgroup: comp.os.linux.advocacy

    w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If that were true, why do they let the quality of Windows updates keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't.
    Because without bugs, there won't be updates except for new features which >> they're reluctantly giving. Without updates, the OS won't look "fresh",
    "maintained", and "supported". They intentionally add more bugs to keep that >> status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities.

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995
    --
    Dr. McCoy:

    "I'm a doctor, not a mechanic."
    -- "The Doomsday Machine", when asked if he had heard of
    the idea of a doomsday machine.
    "I'm a doctor, not an escalator."
    -- "Friday's Child", when asked to help the very pregnant
    Ellen up a steep incline.
    "I'm a doctor, not a bricklayer."
    -- Devil in the Dark", when asked to patch up the Horta.
    "I'm a doctor, not an engineer."
    -- "Mirror, Mirror", when asked by Scotty for help in
    Engineering aboard the ISS Enterprise.
    "I'm a doctor, not a coalminer."
    -- "The Empath", on being beneath the surface of Minara 2.
    "I'm a surgeon, not a psychiatrist."
    -- "City on the Edge of Forever", on Edith Keeler's remark
    that Kirk talked strangely.
    "I'm no magician, Spock, just an old country doctor."
    -- "The Deadly Years", to Spock while trying to cure the
    aging effects of the rogue comet near Gamma Hydra 4.
    "What am I, a doctor or a moonshuttle conductor?"
    -- "The Corbomite Maneuver", when Kirk rushed off from a
    physical exam to answer the alert.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 20:07:49 2026
    From Newsgroup: comp.os.linux.advocacy

    On 11/4/2026 7:50 PM, Chris Ahlstrom wrote:
    w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If that were true, why do they let the quality of Windows updates keep >>>> deteriorating so badly? Seems every other month some rCLfixrCY for some >>>> problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't. >>> Because without bugs, there won't be updates except for new features which >>> they're reluctantly giving. Without updates, the OS won't look "fresh",
    "maintained", and "supported". They intentionally add more bugs to keep that
    status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more
    bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities.

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995


    I remember having a link to this interview, but I'm not looking it up.

    The world has moved on, and in 2026, there are indeed people who pay for stability. I am one of them. Possibly the one other person is Jack
    Yan, who writes about WordPerfect.


    https://jackyan.com/blog/2026/02/where-wordperfect-continues-to-hold-its-own-against-word-and-other-upstarts/

    So there are at least two of us.

    Yes, yes, stability means different things to different people, but at
    least he is happy with WordPerfect, and so am I. Probably both of us
    for different reasons.

    So the question is, is there enough /market/ -- whatever that means --
    for conservative [1] software packages? I think the answer is "yes" and
    so do a lot of other people.


    Best wishes, and happy software conservation!

    [1] Not in the political sense. And I don't even have a license to vote
    in the United States.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 09:50:31 2026
    From Newsgroup: comp.os.linux.advocacy

    On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
    w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If that were true, why do they let the quality of Windows updates keep >>>> deteriorating so badly? Seems every other month some rCLfixrCY for some >>>> problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't. >>> Because without bugs, there won't be updates except for new features which >>> they're reluctantly giving. Without updates, the OS won't look "fresh",
    "maintained", and "supported". They intentionally add more bugs to keep that
    status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more
    bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities.

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    This must be from the "Book of 640K clever things Bill said".

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.
    They didn't have to crash :-) The OSes went downhill after that.
    It seems all we could do after that, was add deck chairs.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?8J+HtfCfh7FKYWNlayBNYXJjaW4gSmF3b3Jza2nwn4e18J+HsQ==?=@jmj@energokod.gda.pl to comp.os.linux.advocacy on Wed Nov 4 19:30:15 2026
    From Newsgroup: comp.os.linux.advocacy

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.

    Then we have "modern office OS-es". Forget real time progs. The office OS-es
    are too slow even for games.

    BTW: Don't forget about AmigaOS, which
    has preemptive multitasking in 1985y., but no root and no process memory
    protection.
    --
    Z totaliztycznym salutem!
    Jacek Marcin Jaworski, Pruszcz Gd., woj. Pomorskie, Polska Efc|Efc#, UE Efc-Efc|;
    Pryw. s. WWW: <https://energokod.gda.pl>; Pryw. tel.: +48-609-170-742; Netykieta: <https://energokod.gda.pl/Netykieta.html>.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?8J+HtfCfh7FKYWNlayBNYXJjaW4gSmF3b3Jza2nwn4e18J+HsQ==?=@jmj@energokod.gda.pl to comp.os.linux.advocacy on Wed Nov 4 19:37:07 2026
    From Newsgroup: comp.os.linux.advocacy

    BTW: I quote Paul, here:

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nick Charles@none@none.none to comp.os.linux.advocacy,comp.sys.mac.advocacy,alt.comp.os.windows-11 on Wed Nov 4 21:55:14 2026
    From Newsgroup: comp.os.linux.advocacy

    Paul <nospam@needed.invalid> wrote:
    On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
    w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>
    If that were true, why do they let the quality of Windows updates keep >>>>> deteriorating so badly? Seems every other month some rCLfixrCY for some >>>>> problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't. >>>> Because without bugs, there won't be updates except for new features which >>>> they're reluctantly giving. Without updates, the OS won't look "fresh", >>>> "maintained", and "supported". They intentionally add more bugs to keep that
    status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more
    bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities.

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    This must be from the "Book of 640K clever things Bill said".

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.
    They didn't have to crash :-) The OSes went downhill after that.

    This is more to life than Microsoft OSes. MacOS and Linux do not crash on
    app updates. In fact, both MacOS and Linux have gone WAY uphill since
    1995.

    It seems all we could do after that, was add deck chairs.

    ThatrCOs all Microsoft could do. Because thatrCOs all they CAN do with Windows.




    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From CrudeSausage@crude@sausa.ge to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 17:12:44 2026
    From Newsgroup: comp.os.linux.advocacy

    On 2026-11-03 9:53 p.m., JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If that were true, why do they let the quality of Windows updates keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't. Because without bugs, there won't be updates except for new features which they're reluctantly giving. Without updates, the OS won't look "fresh", "maintained", and "supported". They intentionally add more bugs to keep that status.

    The worst part is that the operating system itself is not the only
    issue. Hardware manufacturers also produce buggy software that you are
    more or less forced to use with their machines. ASUS's Armoury Crate is
    an excellent example. In other cases, the problems are at the BIOS
    level, and these manufacturers are routinely unwilling to bother
    updating it. MSI is particularly bad in this area whereas ASUS is pretty
    good at updating theirs.
    --
    CrudeSausage
    MacBook Air M4 Sky Blue
    iPhone 13
    Friendly Apple zealot
    Microsoft encourages its employees to transition their children <https://shorturl.at/wb5wM>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 22:13:26 2026
    From Newsgroup: comp.os.linux.advocacy

    On Wed, 4 Nov 2026 09:50:31 -0500, Paul wrote:

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.

    Real OSes existed long before that. They required real hardware to run.

    They didn't have to crash :-)

    First, the operating system should not crash. UNIX systems
    generally have a good, though not impeccable, record for software
    reliability. The typical period between software crashes
    (depending somewhat on how much tinkering with the system has been
    going on recently) is well over a fortnight of continuous
    operation.
    -- Dennis Ritchie, rCLThe UNIX Time-Sharing System rCo A RetrospectiverCY
    (1977)

    The OSes went downhill after that.

    You mean, rCLMicrosoft Windows became dominant after thatrCY. Other OSes didnrCOt rCLgo downhillrCY ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From CrudeSausage@crude@sausa.ge to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 17:15:15 2026
    From Newsgroup: comp.os.linux.advocacy

    On 2026-11-04 3:26 a.m., Lawrence DrCOOliveiro wrote:
    On Wed, 4 Nov 2026 02:52:21 -0500, Paul wrote:

    If you install 150 patches on a 32 bit machine, there is some RAM
    usage by WU, but each patch, as it installs, there is no
    particularly aggressive RAM cleanup between patches, and then, even
    with 3.25GB of memory available on the machine, it cannot finish all
    150 of them.

    That is a really stupid design.

    Admittedly, that is bad.
    --
    CrudeSausage
    MacBook Air M4 Sky Blue
    iPhone 13
    Friendly Apple zealot
    Microsoft encourages its employees to transition their children <https://shorturl.at/wb5wM>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From CrudeSausage@crude@sausa.ge to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 17:18:19 2026
    From Newsgroup: comp.os.linux.advocacy

    On 2026-11-04 6:50 a.m., Chris Ahlstrom wrote:
    w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If that were true, why do they let the quality of Windows updates keep >>>> deteriorating so badly? Seems every other month some rCLfixrCY for some >>>> problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't. >>> Because without bugs, there won't be updates except for new features which >>> they're reluctantly giving. Without updates, the OS won't look "fresh",
    "maintained", and "supported". They intentionally add more bugs to keep that
    status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more
    bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities.

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    His statement is not all that crazy. After all, you won't bother buying
    a new operating system if the only benefit it provides is greater
    stability. After all, most of us will get used to how unstable a system
    is, and we might even find some workarounds. However, if everyone is
    clamoring for a built-in tool made the same company a the one producing
    the operating system itself, there is a good chance that we will be
    willing to part with our money.

    Fortunately, Microsoft's built-in software is usually so awful that
    nobody would pay for it.
    --
    CrudeSausage
    MacBook Air M4 Sky Blue
    iPhone 13
    Friendly Apple zealot
    Microsoft encourages its employees to transition their children <https://shorturl.at/wb5wM>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Wed Nov 4 21:17:18 2026
    From Newsgroup: comp.os.linux.advocacy

    On Wed, 11/4/2026 5:12 PM, CrudeSausage wrote:
    On 2026-11-03 9:53 p.m., JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If that were true, why do they let the quality of Windows updates keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some
    problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they won't.
    Because without bugs, there won't be updates except for new features which >> they're reluctantly giving. Without updates, the OS won't look "fresh",
    "maintained", and "supported". They intentionally add more bugs to keep that >> status.

    The worst part is that the operating system itself is not the only issue. Hardware manufacturers also produce buggy software that you are more or less forced to use with their machines. ASUS's Armoury Crate is an excellent example. In other cases, the problems are at the BIOS level, and these manufacturers are routinely unwilling to bother updating it. MSI is particularly bad in this area whereas ASUS is pretty good at updating theirs.


    Since the Secure Boot issues came up, there have been more updates
    on MSI. I got something for black Lotus on this MSI motherboard.
    The Asus motherboard (for the same era and platform) also had
    an update like that.

    I think there is a switch to switch Armoury Crate off.
    And I had Windows Defender complain about an exploitable Asus
    file (for AiSuite hardware monitor stuff) which I removed.
    I didn't have the package installed, and the item was something
    the uninstaller did not remove. It was a leftover file.

    The NVidia driver solution, is a moderate nuisance on both platforms.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rod Speed@rod.speed.aaa@gmail.com to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Thu Nov 5 17:10:09 2026
    From Newsgroup: comp.os.linux.advocacy

    On Thu, 05 Nov 2026 01:50:31 +1100, Paul <nospam@needed.invalid> wrote:
    On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
    w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>
    If that were true, why do they let the quality of Windows updates >>>>> keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some >>>>> problem ends up creating another, or not even fixing the original
    problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they >>>> won't.
    Because without bugs, there won't be updates except for new features >>>> which
    they're reluctantly giving. Without updates, the OS won't look >>>> "fresh",
    "maintained", and "supported". They intentionally add more bugs to >>>> keep that
    status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more
    bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities.>>
    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    This must be from the "Book of 640K clever things Bill said".

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.
    They didn't have to crash :-) The OSes went downhill after that.
    That's bullshit with networking and the internet alone and the UI
    It seems all we could do after that, was add deck chairs.
    More bullshit
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rod Speed@rod.speed.aaa@gmail.com to comp.os.linux.advocacy,comp.sys.mac.advocacy,alt.comp.os.windows-11 on Thu Nov 5 17:12:35 2026
    From Newsgroup: comp.os.linux.advocacy

    On Thu, 05 Nov 2026 08:55:14 +1100, Nick Charles <none@none.none> wrote:> Paul <nospam@needed.invalid> wrote:
    On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
    w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>>
    If that were true, why do they let the quality of Windows updates >>>>>> keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some >>>>>> problem ends up creating another, or not even fixing the original>>>>>> problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they >>>>> won't.
    Because without bugs, there won't be updates except for new features >>>>> which
    they're reluctantly giving. Without updates, the OS won't look >>>>> "fresh",
    "maintained", and "supported". They intentionally add more bugs to >>>>> keep that
    status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more
    bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities.

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    This must be from the "Book of 640K clever things Bill said".

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.
    They didn't have to crash :-) The OSes went downhill after that.

    This is more to life than Microsoft OSes. MacOS and Linux do not crash > on
    app updates. In fact, both MacOS and Linux have gone WAY uphill since
    1995.
    Yep
    It seems all we could do after that, was add deck chairs.
    ThatrCOs all Microsoft could do. Because thatrCOs all they CAN do with Windows.
    Bullshit with networking alone
    And the UI isnt deckchairs
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Frank Slootweg@this@ddress.is.invalid to comp.os.linux.advocacy,comp.sys.mac.advocacy,alt.comp.os.windows-11 on Thu Nov 5 16:38:49 2026
    From Newsgroup: comp.os.linux.advocacy

    Nick Charles <none@none.none> wrote:
    Paul <nospam@needed.invalid> wrote:
    On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
    [...]

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    This must be from the "Book of 640K clever things Bill said".

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.
    They didn't have to crash :-) The OSes went downhill after that.

    This is more to life than Microsoft OSes. MacOS and Linux do not crash on app updates. In fact, both MacOS and Linux have gone WAY uphill since
    1995.

    As mentioned by Lawrence, the 1995 date is rather silly, because there
    were reliable preemptive multitasking/multiprogramming systems long,
    long before that. My experience with them goes back to the early 70s for pre-UNIX systems and the early 80s for UNIX systems.

    That said, I am sorry to rain on your parade, but ever since the
    NT-family of Windows systems, i.e. Windows NT to 11, I have never had
    Windows crash "on app updates" or any other 'app' related crash for that matter.

    [...]
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Joel W. Crump@joelcrump@gmail.com to comp.os.linux.advocacy,comp.sys.mac.advocacy,alt.comp.os.windows-11 on Thu Nov 5 13:19:40 2026
    From Newsgroup: comp.os.linux.advocacy

    On 11/5/2026 11:38 AM, Frank Slootweg wrote:

    That said, I am sorry to rain on your parade, but ever since the
    NT-family of Windows systems, i.e. Windows NT to 11, I have never had
    Windows crash "on app updates" or any other 'app' related crash for that matter.


    Having seen Windows 2000 on a PC, when it was still a new release, I can definitely say there were certain things Microsoft was "first" on. But
    A Linux system of the time was impressive, already. And Macs were
    getting "OS X" or macOS in the same time frame.
    --
    Joel W. Crump
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Brock McNuggets@brock.mcnuggets@gmail.com to comp.os.linux.advocacy,comp.sys.mac.advocacy,alt.comp.os.windows-11 on Thu Nov 5 11:26:00 2026
    From Newsgroup: comp.os.linux.advocacy

    On 5 Nov 2026, Joel W. Crump wrote in
    <11cihbu$1s52f$1@dont-email.me>:
    On 11/5/2026 11:38 AM, Frank Slootweg wrote:

    That said, I am sorry to rain on your parade, but ever since the
    NT-family of Windows systems, i.e. Windows NT to 11, I have never
    had Windows crash "on app updates" or any other 'app' related
    crash for that matter.


    Having seen Windows 2000 on a PC, when it was still a new release,
    I can definitely say there were certain things Microsoft was
    "first" on. But A Linux system of the time was impressive,
    already. And Macs were getting "OS X" or macOS in the same time
    frame.

    At one point, many moons ago, I was looking for "firsts". My Mac
    list is far more complete. Would love items to add to the list:

    * Double clicking
    * Trash can (or the like)
    * Graying out inactive items
    * Checkmarks next to menu items
    * Keyboard shortcuts for menu items
    * Drag and drop
    * Full file system in GUI (as icons)
    * GUI based hierarchical folder structure
    * Editing documents with direct mouse manipulation
    * The clipboard (and later one with multiple versions of the same
    data so you can paste plain text or formatted text, etc.)
    * Control panel to set system settings
    * Pull down menus
    * Desktop accessories (now known as widgets or gadgets)
    * Meta-data associations with icons (data about the data being
    associated with the file)
    * Self-redrawing windows (at Apple) and later windows where the
    image was still held in memory even when not visible, making the
    redraw be instantaneous from the perspective of a user (called
    double buffering and done at NeXT)
    * X to close a window (this is from NeXT - I was surprised by that)

    MS did also add some ideas that have stuck around:

    * Contextual (right click) menus
    * Drag indicators (to show copying, moving, making a shortcut /
    alias)
    * The Start button

    Sure I am missing a lot.
    --
    You can't find peace with someone at war with themselves.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nick Charles@none@none.none to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Thu Nov 5 20:20:16 2026
    From Newsgroup: comp.os.linux.advocacy

    Frank Slootweg <this@ddress.is.invalid> wrote:
    Nick Charles <none@none.none> wrote:
    Paul <nospam@needed.invalid> wrote:
    On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
    [...]

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    This must be from the "Book of 640K clever things Bill said".

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.
    They didn't have to crash :-) The OSes went downhill after that.

    This is more to life than Microsoft OSes. MacOS and Linux do not crash on >> app updates. In fact, both MacOS and Linux have gone WAY uphill since
    1995.

    As mentioned by Lawrence, the 1995 date is rather silly, because there
    were reliable preemptive multitasking/multiprogramming systems long,
    long before that. My experience with them goes back to the early 70s for pre-UNIX systems and the early 80s for UNIX systems.

    My experience also. But those were computers that were not available to consumers.

    That said, I am sorry to rain on your parade, but ever since the
    NT-family of Windows systems, i.e. Windows NT to 11, I have never had
    Windows crash "on app updates" or any other 'app' related crash for that matter.

    Then you need to get out more. In the last year or so there were screens
    in airports around the world with crashed Windows Blue Screens due to a
    broken non-OS update.

    Just because you have never personally seen Windows crash and burn does not mean it never happens. Windows is far too easy to crash.







    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nick Charles@none@none.none to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Thu Nov 5 20:20:16 2026
    From Newsgroup: comp.os.linux.advocacy

    Rod Speed <rod.speed.aaa@gmail.com> wrote:
    On Thu, 05 Nov 2026 08:55:14 +1100, Nick Charles <none@none.none> wrote:

    Paul <nospam@needed.invalid> wrote:
    On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
    w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>>>
    If that were true, why do they let the quality of Windows updates >>>>>>> keep
    deteriorating so badly? Seems every other month some rCLfixrCY for some >>>>>>> problem ends up creating another, or not even fixing the original >>>>>>> problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they >>>>>> won't.
    Because without bugs, there won't be updates except for new features >>>>>> which
    they're reluctantly giving. Without updates, the OS won't look
    "fresh",
    "maintained", and "supported". They intentionally add more bugs to >>>>>> keep that
    status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more
    bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities.

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    This must be from the "Book of 640K clever things Bill said".

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.
    They didn't have to crash :-) The OSes went downhill after that.

    This is more to life than Microsoft OSes. MacOS and Linux do not crash >> on
    app updates. In fact, both MacOS and Linux have gone WAY uphill since
    1995.

    Yep

    It seems all we could do after that, was add deck chairs.

    ThatrCOs all Microsoft could do. Because thatrCOs all they CAN do with
    Windows.

    Bullshit with networking alone

    ThatrCOs twice you have said rCLbullshit with networkingrCY. What does that mean?




    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Thu Nov 5 17:34:20 2026
    From Newsgroup: comp.os.linux.advocacy

    On Thu, 11/5/2026 3:20 PM, Nick Charles wrote:
    Frank Slootweg <this@ddress.is.invalid> wrote:

    That said, I am sorry to rain on your parade, but ever since the
    NT-family of Windows systems, i.e. Windows NT to 11, I have never had
    Windows crash "on app updates" or any other 'app' related crash for that
    matter.

    Then you need to get out more. In the last year or so there were screens
    in airports around the world with crashed Windows Blue Screens due to a broken non-OS update.

    Just because you have never personally seen Windows crash and burn does not mean it never happens. Windows is far too easy to crash.

    Well, first of all, we have to be careful to label the things
    that happen on the computer, properly.

    Not everything is a conventional crash.

    If you can find a technical analysis of what happened,
    we can attempt to classify it for you. It's too complicated
    to just write a book, in response to such a claim.

    The partitioning on preemptive multitasking systems, with
    Ring separation between Ring0 kernel and drivers and Ring3 application
    space, is why Frank is making that claim. He has UNIX experience
    as do I, and there, the reliability demonstrated, is exceptional.
    The basic ideas in the design, are sound.

    Back in the WinXP era or so, someone at Microsoft noted that
    30% of all crashes, were in the NVidia driver. Today, the NVidia
    driver is containerized and isolated from the kernel. There are a
    couple watchdogs down there, checking for a hooped driver. The driver
    is capable of automatic recovery -- for simple/obvious failure cases,
    the recovery works well. For more complicated case, it doesn't always work,
    or it can take some amount of time (a whole minute) before it recovers.
    Since there is no updated architecture drawing for the OS, we cannot
    always comment about what is going on down there. It's an inverted
    hypervisor, the OS itself is virtualized, and down there is the
    NVidia container, VirbualBox, VMWare, WSL2/WSLg and so on. Oh, and
    that proprietary AV you installed, is down there interfering with
    how things work. A work item for Microsoft, is booting them the
    hell out of there.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rod Speed@rod.speed.aaa@gmail.com to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Fri Nov 6 09:59:54 2026
    From Newsgroup: comp.os.linux.advocacy

    On Fri, 06 Nov 2026 07:20:16 +1100, Nick Charles <none@none.none> wrote:> Rod Speed <rod.speed.aaa@gmail.com> wrote:
    On Thu, 05 Nov 2026 08:55:14 +1100, Nick Charles <none@none.none> wrote:

    Paul <nospam@needed.invalid> wrote:
    On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
    w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):

    On 11/03/26 7:53 PM, JJ wrote:
    On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>>>>
    If that were true, why do they let the quality of Windows updates >>>>>>>> keep
    deteriorating so badly? Seems every other month some rCLfixrCY for >>>>>>>> some
    problem ends up creating another, or not even fixing the original >>>>>>>> problem properly in the first place.

    Bugs are Microsoft's life. They can fix all of the bugs, but they >>>>>>> won't.
    Because without bugs, there won't be updates except for new >>>>>>> features
    which
    they're reluctantly giving. Without updates, the OS won't look
    "fresh",
    "maintained", and "supported". They intentionally add more bugs to >>>>>>> keep that
    status.

    That's not an accurate assessment.
    Not a single operating system development intentionally adds more>>>>>> bugs(Windows, MacOS, Android, iOs, Linux, etc.).
    Nor does any operating system exist that doesn't need patches to
    existing or new code for functionality, features or vulnerabilities. >>>>>
    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    This must be from the "Book of 640K clever things Bill said".

    It wasn't that many years after 1995, that cooperative multitasking>>>> got changed to preemptive multitasking, and we had real OSes then.
    They didn't have to crash :-) The OSes went downhill after that.

    This is more to life than Microsoft OSes. MacOS and Linux do not >>> crash
    on
    app updates. In fact, both MacOS and Linux have gone WAY uphill since
    1995.

    Yep

    It seems all we could do after that, was add deck chairs.

    ThatrCOs all Microsoft could do. Because thatrCOs all they CAN do with
    Windows.

    Bullshit with networking alone

    ThatrCOs twice you have said rCLbullshit with networkingrCY. What does that mean?
    What MS did with networking was nothing even remotely like deck chairs
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Thu Nov 5 23:13:45 2026
    From Newsgroup: comp.os.linux.advocacy

    On Thu, 05 Nov 2026 20:20:16 +0000, Nick Charles wrote:

    But those [big machines] were computers that were not available to
    consumers.

    There were rCLcomputing bureausrCY where you could get an account on a
    large time-shared machine.

    Some even offered low-cost or free services <https://en.wikipedia.org/wiki/Community_Memory>.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsQ==?=@winstonmvp@gmail.com to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Fri Nov 6 02:15:27 2026
    From Newsgroup: comp.os.linux.advocacy

    On 11/05/26 1:20 PM, Nick Charles wrote:
    Frank Slootweg <this@ddress.is.invalid> wrote:
    That said, I am sorry to rain on your parade, but ever since the
    NT-family of Windows systems, i.e. Windows NT to 11, I have never had
    Windows crash "on app updates" or any other 'app' related crash for that
    matter.

    Then you need to get out more. In the last year or so there were screens
    in airports around the world with crashed Windows Blue Screens due to a broken non-OS update.

    Just because you have never personally seen Windows crash and burn does not mean it never happens. Windows is far too easy to crash.

    Yes, the global airport screens and system failures were caused by a
    software app update.

    That update was provided, not by Microsoft, but Crowdstrike.
    Microsoft updates do not include updates from Crowdstrike.
    - Crowdstrike updates are managed and delivered independently from
    Windows Updates - pulling their own signature/channel def updates automatically via their 'own' cloud infrastructure.
    - updates are pushed down by Crowdstrike, not Microsoft.

    Two months prior to the Crowdstrike update impacting Windows,
    Crowdstrike pushed down an app update for Debian Linux causing server
    crashes and looped booting.
    - i.e. your earlier point that app updates don't crash on Linux is incorrect. In this from the exact same source => Crowdstrike

    There was one particular point you made that could be somewhat true.
    - Your comment that the airport screen crashing in the last year or so
    could be accurate if liberty was given to the 'or so' timeframe.
    - nothing of the above happened in this year or last year(2025) thus
    'or so' would be 2.5 years ago for Windows and 2.75 years ago for Linux.
    --
    ...w-i|#-o-#-n|#
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Frank Slootweg@this@ddress.is.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Fri Nov 6 15:07:51 2026
    From Newsgroup: comp.os.linux.advocacy

    ...wi+o#n+ <winstonmvp@gmail.com> wrote:
    On 11/05/26 1:20 PM, Nick Charles wrote:
    Frank Slootweg <this@ddress.is.invalid> wrote:
    That said, I am sorry to rain on your parade, but ever since the
    NT-family of Windows systems, i.e. Windows NT to 11, I have never had
    Windows crash "on app updates" or any other 'app' related crash for that >> matter.

    Then you need to get out more. In the last year or so there were screens in airports around the world with crashed Windows Blue Screens due to a broken non-OS update.

    Just because you have never personally seen Windows crash and burn does not mean it never happens. Windows is far too easy to crash.

    Yes, the global airport screens and system failures were caused by a software app update.

    Was this *really* caused by a software 'app' update, or did the
    (Crowdstrike) 'app' also include low-level components - such as drivers,
    etc. - and were on or more of these these low-level components, the
    cause?

    That update was provided, not by Microsoft, but Crowdstrike.
    Microsoft updates do not include updates from Crowdstrike.
    - Crowdstrike updates are managed and delivered independently from
    Windows Updates - pulling their own signature/channel def updates automatically via their 'own' cloud infrastructure.
    - updates are pushed down by Crowdstrike, not Microsoft.

    Two months prior to the Crowdstrike update impacting Windows,
    Crowdstrike pushed down an app update for Debian Linux causing server crashes and looped booting.
    - i.e. your earlier point that app updates don't crash on Linux is incorrect. In this from the exact same source => Crowdstrike

    There was one particular point you made that could be somewhat true.
    - Your comment that the airport screen crashing in the last year or so could be accurate if liberty was given to the 'or so' timeframe.
    - nothing of the above happened in this year or last year(2025) thus
    'or so' would be 2.5 years ago for Windows and 2.75 years ago for Linux.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Frank Slootweg@this@ddress.is.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Fri Nov 6 15:19:58 2026
    From Newsgroup: comp.os.linux.advocacy

    Nick Charles <none@none.none> wrote:
    Frank Slootweg <this@ddress.is.invalid> wrote:
    Nick Charles <none@none.none> wrote:
    Paul <nospam@needed.invalid> wrote:
    On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
    [...]

    "The reason we come up with new versions is not to fix bugs.
    It's absolutely not. It's the stupidest reason to buy a new
    version I ever heard. When we do a new version we put in lots
    of new things that people are asking for. And so, in no sense,
    is stability a reason to move to a new version. It's never a
    reason."
    -- Bill Gates circa 1995

    This must be from the "Book of 640K clever things Bill said".

    It wasn't that many years after 1995, that cooperative multitasking
    got changed to preemptive multitasking, and we had real OSes then.
    They didn't have to crash :-) The OSes went downhill after that.

    This is more to life than Microsoft OSes. MacOS and Linux do not crash on
    app updates. In fact, both MacOS and Linux have gone WAY uphill since
    1995.

    As mentioned by Lawrence, the 1995 date is rather silly, because there were reliable preemptive multitasking/multiprogramming systems long,
    long before that. My experience with them goes back to the early 70s for pre-UNIX systems and the early 80s for UNIX systems.

    My experience also. But those were computers that were not available to consumers.

    Well, I *did* own some of them, but I digress! :-)

    That said, I am sorry to rain on your parade, but ever since the NT-family of Windows systems, i.e. Windows NT to 11, I have never had Windows crash "on app updates" or any other 'app' related crash for that matter.

    Then you need to get out more. In the last year or so there were screens
    in airports around the world with crashed Windows Blue Screens due to a broken non-OS update.

    I thought we were tallking about consumers!? :-)

    [BTW, yesterday there was a story on the news about US airports still
    using Windows 95 systems with diskettes for some purpose and having
    trouble replacing these by something better/newer. (Was on TV, so I
    don't have a URL.)]

    Just because you have never personally seen Windows crash and burn does not mean it never happens. Windows is far too easy to crash.

    Yes, easier than Linux and Macs, but "far too easy"? I don't think so
    for Joe Consumer.

    As said before, I'm a Five Nines kind of guy, but I can still see
    things in perspective.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsQ==?=@winstonmvp@gmail.com to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Fri Nov 6 09:27:27 2026
    From Newsgroup: comp.os.linux.advocacy

    On 11/06/26 8:07 AM, Frank Slootweg wrote:
    ...w-i|#-o-#-n|# <winstonmvp@gmail.com> wrote:
    Yes, the global airport screens and system failures were caused by a
    software app update.

    Was this *really* caused by a software 'app' update, or did the (Crowdstrike) 'app' also include low-level components - such as drivers,
    etc. - and were on or more of these these low-level components, the
    cause?

    The Crowdstrike update was for its own cybersecurity cloud software
    model which operates on one, single, agent(aka/branded as Falcon Sensor Platform).
    => a flawed channel file update for the agent's configuration


    That update was provided, not by Microsoft, but Crowdstrike.
    Microsoft updates do not include updates from Crowdstrike.
    - Crowdstrike updates are managed and delivered independently from
    Windows Updates - pulling their own signature/channel def updates
    automatically via their 'own' cloud infrastructure.
    - updates are pushed down by Crowdstrike, not Microsoft.

    Two months prior to the Crowdstrike update impacting Windows,
    Crowdstrike pushed down an app update for Debian Linux causing server
    crashes and looped booting.
    - i.e. your earlier point that app updates don't crash on Linux is
    incorrect. In this from the exact same source => Crowdstrike

    There was one particular point you made that could be somewhat true.
    - Your comment that the airport screen crashing in the last year or so
    could be accurate if liberty was given to the 'or so' timeframe.
    - nothing of the above happened in this year or last year(2025) thus
    'or so' would be 2.5 years ago for Windows and 2.75 years ago for Linux.
    --
    ...w-i|#-o-#-n|#
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Fri Nov 6 14:45:56 2026
    From Newsgroup: comp.os.linux.advocacy

    On Fri, 11/6/2026 10:07 AM, Frank Slootweg wrote:
    ...w-i|#-o-#-n|# <winstonmvp@gmail.com> wrote:
    On 11/05/26 1:20 PM, Nick Charles wrote:
    Frank Slootweg <this@ddress.is.invalid> wrote:
    That said, I am sorry to rain on your parade, but ever since the
    NT-family of Windows systems, i.e. Windows NT to 11, I have never had
    Windows crash "on app updates" or any other 'app' related crash for that >>>> matter.

    Then you need to get out more. In the last year or so there were screens >>> in airports around the world with crashed Windows Blue Screens due to a
    broken non-OS update.

    Just because you have never personally seen Windows crash and burn does not >>> mean it never happens. Windows is far too easy to crash.

    Yes, the global airport screens and system failures were caused by a
    software app update.

    Was this *really* caused by a software 'app' update, or did the (Crowdstrike) 'app' also include low-level components - such as drivers,
    etc. - and were on or more of these these low-level components, the
    cause?


    https://www.computerweekly.com/opinion/One-year-on-from-the-CrowdStrike-outageWhat-have-we-learned

    "The underlying nature of its Windows operating system, to which it provided
    Ring 0 equivalent kernel access to CrowdStrike making the issue possible
    in the first instance, was also a contributing factor."

    This is one reason Microsoft wants to chase AV products out of Ring0.

    https://www.ghacks.net/2025/06/27/microsoft-is-moving-antivirus-programs-from-running-at-kernel-level/

    Paul

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Frank Slootweg@this@ddress.is.invalid to comp.sys.mac.advocacy,comp.os.linux.advocacy,alt.comp.os.windows-11 on Sat Nov 7 11:05:02 2026
    From Newsgroup: comp.os.linux.advocacy

    Paul <nospam@needed.invalid> wrote:
    On Fri, 11/6/2026 10:07 AM, Frank Slootweg wrote:
    ...wi+o#n+ <winstonmvp@gmail.com> wrote:
    On 11/05/26 1:20 PM, Nick Charles wrote:
    Frank Slootweg <this@ddress.is.invalid> wrote:
    That said, I am sorry to rain on your parade, but ever since the
    NT-family of Windows systems, i.e. Windows NT to 11, I have never had >>>> Windows crash "on app updates" or any other 'app' related crash for that >>>> matter.

    Then you need to get out more. In the last year or so there were screens >>> in airports around the world with crashed Windows Blue Screens due to a >>> broken non-OS update.

    Just because you have never personally seen Windows crash and burn
    does not mean it never happens. Windows is far too easy to
    crash.

    Yes, the global airport screens and system failures were caused by a
    software app update.

    Was this *really* caused by a software 'app' update, or did the (Crowdstrike) 'app' also include low-level components - such as drivers, etc. - and were on or more of these these low-level components, the
    cause?

    https://www.computerweekly.com/opinion/One-year-on-from-the-CrowdStrike-outageWhat-have-we-learned

    "The underlying nature of its Windows operating system, to which
    it provided Ring 0 equivalent kernel access to CrowdStrike making
    the issue possible in the first instance, was also a contributing
    factor."

    So the cause *was* indeed a low-level component with Ring 0 equivalent
    kernel access. Such a component can crash *any* OS and - as Winston
    mentioned -, CrowdStrike updates, did not only crash these Windows
    systems, but also Linux systems.

    So Nick Charles' argument "Windows is far too easy to crash." is not supported by his (CrowdStrike) evidence.

    This is one reason Microsoft wants to chase AV products out of Ring0.

    https://www.ghacks.net/2025/06/27/microsoft-is-moving-antivirus-programs-from-running-at-kernel-level/
    --- Synchronet 3.22a-Linux NewsLink 1.2