• Is iOS really a monolith or not? And why does it matter (a lot!)

    From Maria Sophia@mariasophia@comprehension.com to misc.phone.mobile.iphone,comp.sys.mac.advocacy,comp.sys.mac.system on Fri Oct 30 00:17:17 2026
    From Newsgroup: comp.sys.mac.advocacy

    Is iOS really a monolith or not? And why does it matter (a lot!)

    To put this issue to rest, allow me to include a post just now.

    It explains that iOS is a monolith.
    But (some) people keep saying it's not.

    I don't know why they say that.
    But I think they only see the final delta.

    Not what actually gets released.

    The delta is meaningless in terms of WHY a monolith is so bad, that nobody
    but Apple delivers software that way (although RSRs are a recent feature).

    Only Apple ships the monolith.
    It's an outdated method which is a core reason iOS bugs are exploited.

    --- < cut here for the discussion about iOS being a monolith > ---

    Newsgroups: alt.comp.os.windows-10,comp.sys.mac.system,misc.phone.mobile.iphone Subject: Re: If you're used to the Windows WhatsApp SAVE PDF to device...
    Date: Thu, 29 Oct 2026 22:57:05 -0400
    Message-ID: <11c1120$284u$1@nnrp.usenet.blueworldhosting.com>

    Nick Charles wrote:
    Thinks that every iOS update is the ENTIRE 10GB (or whatever size) iOS, even if just a single line of code was changed. Because he thinks that iOS is monolithic. Nevermind that you can see the exact size of EVERY iOS update. Which explains why x.0.0 versions take more time to DL/install than x.x.1 versions.

    Regarding... -----------------------------------------------------------------------
    Thinks that every iOS update is the ENTIRE 10GB

    It's no longer surprising Apple owners have absolutely no idea that the iOS updates are monolithic from the factory and then delta updated on devices.

    When Apple ships an iOS update to an iPhone, it is packaged and delivered
    as a single, unified firmware image (an .ipsw file container). Apple cannot push a fragmented, a la carte bundle of separate, independent OS component packages to your phone the way Windows or Android can (outside of minor exceptions like the relatively new Rapid Security Responses). From the
    factory build pipeline to the end-user's download screen, it is treated, compiled, and deployed as a single block.

    If you think that's not true, then explain WHY you think it's not correct.
    (And notice the "delta" you "think" you understand, isn't the point here.)

    At Apple's engineering headquarters and build servers, iOS is compiled and packaged as a single, unified block of firmware (the .ipsw master image).
    Apple does not maintain modular, standalone OS package repositories like
    Linux distros or Android's Project Mainline. The master artifact built at
    the factory is a monolith.

    The Delivery Mechanism is a Delta Patch: When that monolith is pushed Over-The-Air (OTA) to an active device, Apple's update server dynamically generates a targeted, differential patch (a delta) tailored precisely to
    what is already sitting on that specific user's flash storage.

    Apple nutjobs confuse the delivery method with the operating system's architecture. But it's the architecture why iOS has so many exploits.

    Note this monolithic structure is IMPORTANT because it's a huge reason
    why Apple iOS software is so buggy. They have to COLLECT all the bugs! -----------------------------------------------------------------------

    I could go on, but the point is the Apple nutcases don't know anything
    about how Apple products work. They just hate that they work the way they
    do, and they are religious nutjobs that deny every fact about Apple.

    Using the first absurd excuse that they can think of.

    It's what Apple religious zealot nutcases do.
    1. None of them have any education
    2. All of them believe EVERYTHING Apple marketing told them
    3. And all defend Apple to the death, no matter what
    Even as not one of them understands a single thing about Apple products.
    --
    On Usenet, unfortunately, are those who couldn't get a high school diploma.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nick Charles@none@none.none to comp.sys.mac.advocacy,comp.sys.mac.system,misc.phone.mobile.iphone on Fri Oct 30 15:13:02 2026
    From Newsgroup: comp.sys.mac.advocacy

    On Oct 30, 2026 at 12:17:17rC>AM EDT, "Maria Sophia" <mariasophia@comprehension.com> wrote:

    Is iOS really a monolith or not? And why does it matter (a lot!)

    To put this issue to rest, allow me to include a post just now.

    It explains that iOS is a monolith.
    But (some) people keep saying it's not.

    You are not "explaining" anything. You are merely restating your ignorant claim.

    OF COURSE the full iOS (or whatever software) is fully rebuilt on ANY change.
    The build process is automated. Any file that is changed - even if it is
    just a text file for a help screen (no code at all) - can trigger a full rebuild.

    This happens so the QA people can always grab the latest builds to do regression testing. Since I am sure you have no idea what that is, I will explain. QA people are constantly testing the latest builds to verify that
    old bugs have not returned and to check that the latest changes did not cause any NEW isses.

    Always creating full builds on any change has nothing to do with "monolith" .
    You don't even know what the word means in this context. So again, I will explain. Unix was designed to be modular, portable and scalable. This means that no module is dependent on another module at the source code level. This
    is the main problem with the "design" of Windows. It has many circlular dependencies. Meaning, you can't remove module A without breaking modules B, F and M.

    So to "scale down" to run on a watch for example, if you want to remove module A because it is not needed, you now have to recode modules B, F and M. But changing these 3 can have downstream effects on OTHER parts of the system. Again, Circular Dependencies.

    Unix is NOT monolithic. It was designed for easy portability/scalabilty. Which explains why it runs on everything from mainframes to watches. Windows only runs well on Intel PCs. The Arm port is taking forever to perfect,
    because Windows IS monolithic.

    As for updating, your ORIGINAL claim was that Apple was sending out the ENTIRE iOS to every device. Now you have backtracked to admitting they use delta files. If iOS was monolithic, how would delta files even be possible?

    Congratulations. You have just contradicted yourself. AGAIN.

    The update servers NEED to have the full current version available for people who are updating from very old versions. For example, I completely skipped
    iOS 13 because it was so buggy. When I finally updated from 12.5.7, I went straight to 14.2.1. If the full current version of iOS 14 was not available I would have to install 14.0.0 and then every update since to get current.

    That would be stupid, right?

    So the update servers have the full current version available and generate custom delta files for every device that is updating. That is standard procedure for updates. It also has nothing to do with "monolithic software".
    This is why x.0.0 updates are 8GB or more and x.x.1 updates are 300MB or
    less.

    I have been in software development for longer than you have been alive. Which is not saying much since you act like you are 15. I know what I am talking about here. I used to maintain the automated build process and test
    the updates. You can trigger full builds on ANY source file change. Or if the software in question takes a long time to build you can do hourly builds or x number of builds a day. Whatever works best.

    So the QA people always have the latest full builds available.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Brock McNuggets@brock.mcnuggets@gmail.com to misc.phone.mobile.iphone,comp.sys.mac.advocacy,comp.sys.mac.system on Fri Oct 30 08:33:42 2026
    From Newsgroup: comp.sys.mac.advocacy

    On 29 Oct 2026, Maria Sophia wrote in <11c15od$1pbh$1@nnrp.usenet.blueworldhosting.com>:
    Is iOS really a monolith or not? And why does it matter (a lot!)

    Packaging is not architecture. You keep conflating the two.

    <snip>

    When Apple ships an iOS update to an iPhone, it is packaged and
    delivered as a single, unified firmware image (an .ipsw file
    container).

    True for a restore/DFU. Not true for OTA, which is what almost
    everyone uses. Apple's own platform security guide says OTA updates
    download only the components required to complete the update, not
    the entire OS:
    https://support.apple.com/guide/security/secf683e0b36/web


    Apple cannot push a fragmented, a la carte bundle of separate,
    independent OS component packages to your phone the way Windows or
    Android can (outside of minor exceptions like the relatively new
    Rapid Security Responses). From the factory build pipeline to the
    end-user's download screen, it is treated, compiled, and deployed
    as a single block.

    A single signed, versioned release artifact is just how you ship a
    release. Android factory images are whole-partition images too, with block-level OTA deltas:
    https://source.android.com/docs/core/ota

    If "ships as one signed image" means monolith, then Android is a
    monolith too, and so is every Windows ISO. That undercuts your own
    "only Apple" line.

    <snip>

    Note this monolithic structure is IMPORTANT because it's a huge
    reason why Apple iOS software is so buggy. They have to COLLECT
    all the bugs!

    Non sequitur. Release batching is a cadence choice, not a
    file-format property. Apple ships x.y.z security point releases all
    the time. Microsoft batches on Patch Tuesday. Same idea.

    <snip>
    --
    It's impossible for someone who is at war with themselves to be at peace with you.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to misc.phone.mobile.iphone,comp.sys.mac.advocacy,comp.sys.mac.system on Fri Oct 30 19:21:45 2026
    From Newsgroup: comp.sys.mac.advocacy

    Verbatim... (keeping this thread as a reference thread for current/future use)

    From: Nick Charles <none@none.none>
    Newsgroups: comp.sys.mac.advocacy,comp.sys.mac.system,misc.phone.mobile.iphone Subject: Re: Is Arlen REALLY a dumbass? The answer is obvious. AGAIN. (was: Is iOS really a monolith or not? And why does it matter (a lot!))
    References: <11c15od$1pbh$1@nnrp.usenet.blueworldhosting.com>
    Message-ID: <NMCdnQz8-rNjLnn3nZ2dnZfqn_qdnZ2d@supernews.com>
    Date: Fri, 30 Oct 2026 15:13:02 +0000

    On Oct 30, 2026 at 12:17:17rC>AM EDT, "Maria Sophia" <mariasophia@comprehension.com> wrote:

    Is iOS really a monolith or not? And why does it matter (a lot!)

    To put this issue to rest, allow me to include a post just now.

    It explains that iOS is a monolith.
    But (some) people keep saying it's not.

    You are not "explaining" anything. You are merely restating your ignorant claim.

    OF COURSE the full iOS (or whatever software) is fully rebuilt on ANY change.
    The build process is automated. Any file that is changed - even if it is
    just a text file for a help screen (no code at all) - can trigger a full rebuild.

    This happens so the QA people can always grab the latest builds to do regression testing. Since I am sure you have no idea what that is, I will explain. QA people are constantly testing the latest builds to verify that
    old bugs have not returned and to check that the latest changes did not cause any NEW isses.

    Always creating full builds on any change has nothing to do with "monolith" .
    You don't even know what the word means in this context. So again, I will explain. Unix was designed to be modular, portable and scalable. This means that no module is dependent on another module at the source code level. This
    is the main problem with the "design" of Windows. It has many circlular dependencies. Meaning, you can't remove module A without breaking modules B, F and M.

    So to "scale down" to run on a watch for example, if you want to remove module A because it is not needed, you now have to recode modules B, F and M. But changing these 3 can have downstream effects on OTHER parts of the system. Again, Circular Dependencies.

    Unix is NOT monolithic. It was designed for easy portability/scalabilty. Which explains why it runs on everything from mainframes to watches. Windows only runs well on Intel PCs. The Arm port is taking forever to perfect,
    because Windows IS monolithic.

    As for updating, your ORIGINAL claim was that Apple was sending out the ENTIRE iOS to every device. Now you have backtracked to admitting they use delta files. If iOS was monolithic, how would delta files even be possible?

    Congratulations. You have just contradicted yourself. AGAIN.

    The update servers NEED to have the full current version available for people who are updating from very old versions. For example, I completely skipped
    iOS 13 because it was so buggy. When I finally updated from 12.5.7, I went straight to 14.2.1. If the full current version of iOS 14 was not available I would have to install 14.0.0 and then every update since to get current.

    That would be stupid, right?

    So the update servers have the full current version available and generate custom delta files for every device that is updating. That is standard procedure for updates. It also has nothing to do with "monolithic software".
    This is why x.0.0 updates are 8GB or more and x.x.1 updates are 300MB or
    less.

    I have been in software development for longer than you have been alive. Which is not saying much since you act like you are 15. I know what I am talking about here. I used to maintain the automated build process and test
    the updates. You can trigger full builds on ANY source file change. Or if the software in question takes a long time to build you can do hourly builds or x number of builds a day. Whatever works best.

    So the QA people always have the latest full builds available.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to misc.phone.mobile.iphone,comp.sys.mac.advocacy,comp.sys.mac.system on Fri Oct 30 20:39:08 2026
    From Newsgroup: comp.sys.mac.advocacy

    HINT: Why do you think Apple calls the new RSR mechanism ... "rapid"?

    Typical iOS updates require bundling hundreds of security patches,
    framework changes and operating system updates into a single monolithic
    package that goes through an excrutiatingly slow, coordinated rollout.

    Outside the relatively recent RSR mechanism, what iOS can't do is deliver
    an arbitrary iOS component as its own independently installable, routine
    update the way every other common consumer operating system does things.

    For example, Android Project Mainline (since renamed to Google Play sys tem updates) can update selected modules outside a normal Android release
    cycle, and, in fact, updates two score of modules *forever* for all
    Android10+ devices on the Internet (yes, there is no end-of-life date).

    Outside Apple's modern and relatively recent Rapid Security Responses or Apple's newer background security mechanisms, a system fix was always
    delivered through a coordinated iOS update, which slowed things down.

    When you slow down the update, you give more time to the bad guys.
    Which is maybe why Apple's CISA KEV results are so atrociously heinous.

    If a fix has to wait for that coordinated update and rollout, users will
    remain exposed longer than if the affected component could be patched and delivered independently.

    Because standard iOS architecture historically treated the OS as a rigid, monolithic block, patching a single vulnerability in WebKit or the kernel
    meant forcing users to download an entire gigabyte-plus software update, go through a lengthy installation reboot, and wait for Apple's servers to
    gatekeep and sign the release.

    By contrast to the primitive monolithic method, the Rapid Security Response (RSR) mechanism bypasses that monolithic bottleneck. It allows Apple to
    push out isolated patches-like hot-fixing a zero-day exploit in Safari's rendering engine-independently of a full OS release, dramatically shrinking
    the window of exposure that bad guys rely on.

    In summary, Apple historically lacked an Android Mainline-equivalent general-purpose mechanism for independently updating a broad set of OS
    modules outside normal OS releases. But RSR is not that equivalent. It is a restricted mechanism for rapidly delivering eligible security improvements between regular releases.

    Prove me wrong.
    a. But just saying it's wrong isn't what intelligent people do.
    b. That's what Apple religious zealots do.

    And don't say I said the code itself is monolithic.
    b. Again, that's what Apple religious zealots do.
    c. Because they can't understand how the process really works.

    Nobody said the code is monolithic. The process is what's monolithic.
    *The components are modular. But the update pipeline isn't.*
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nick Charles@none@none.none to comp.sys.mac.system,misc.phone.mobile.iphone,comp.sys.mac.advocacy on Sat Oct 31 00:47:53 2026
    From Newsgroup: comp.sys.mac.advocacy

    Brock McNuggets <brock.mcnuggets@gmail.com> wrote:
    On 29 Oct 2026, Maria Sophia wrote in <11c15od$1pbh$1@nnrp.usenet.blueworldhosting.com>:
    Is iOS really a monolith or not? And why does it matter (a lot!)

    Packaging is not architecture. You keep conflating the two.

    <snip>

    When Apple ships an iOS update to an iPhone, it is packaged and
    delivered as a single, unified firmware image (an .ipsw file
    container).

    True for a restore/DFU. Not true for OTA, which is what almost
    everyone uses. Apple's own platform security guide says OTA updates
    download only the components required to complete the update, not
    the entire OS:
    https://support.apple.com/guide/security/secf683e0b36/web


    Apple cannot push a fragmented, a la carte bundle of separate,
    independent OS component packages to your phone the way Windows or
    Android can (outside of minor exceptions like the relatively new
    Rapid Security Responses). From the factory build pipeline to the
    end-user's download screen, it is treated, compiled, and deployed
    as a single block.

    A single signed, versioned release artifact is just how you ship a
    release. Android factory images are whole-partition images too, with block-level OTA deltas:
    https://source.android.com/docs/core/ota

    If "ships as one signed image" means monolith, then Android is a
    monolith too, and so is every Windows ISO. That undercuts your own
    "only Apple" line.

    <snip>

    Note this monolithic structure is IMPORTANT because it's a huge
    reason why Apple iOS software is so buggy. They have to COLLECT
    all the bugs!

    Non sequitur. Release batching is a cadence choice, not a
    file-format property. Apple ships x.y.z security point releases all
    the time. Microsoft batches on Patch Tuesday. Same idea.

    As always, IT is utterly clueless.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Brock McNuggets@brock.mcnuggets@gmail.com to comp.sys.mac.system,misc.phone.mobile.iphone,comp.sys.mac.advocacy on Fri Oct 30 17:49:29 2026
    From Newsgroup: comp.sys.mac.advocacy

    On 30 Oct 2026, Nick Charles wrote in <ejCdnROYK7okp3j3nZ2dnZfqnPWdnZ2d@supernews.com>:
    Brock McNuggets <brock.mcnuggets@gmail.com> wrote:
    On 29 Oct 2026, Maria Sophia wrote in
    <11c15od$1pbh$1@nnrp.usenet.blueworldhosting.com>:
    Is iOS really a monolith or not? And why does it matter (a lot!)

    Packaging is not architecture. You keep conflating the two.

    <snip>

    When Apple ships an iOS update to an iPhone, it is packaged and
    delivered as a single, unified firmware image (an .ipsw file
    container).

    True for a restore/DFU. Not true for OTA, which is what almost
    everyone uses. Apple's own platform security guide says OTA
    updates download only the components required to complete the
    update, not the entire OS:
    https://support.apple.com/guide/security/secf683e0b36/web


    Apple cannot push a fragmented, a la carte bundle of separate,
    independent OS component packages to your phone the way Windows
    or Android can (outside of minor exceptions like the relatively
    new Rapid Security Responses). From the factory build pipeline
    to the end-user's download screen, it is treated, compiled, and
    deployed as a single block.

    A single signed, versioned release artifact is just how you ship
    a release. Android factory images are whole-partition images too,
    with block-level OTA deltas:
    https://source.android.com/docs/core/ota

    If "ships as one signed image" means monolith, then Android is a
    monolith too, and so is every Windows ISO. That undercuts your
    own "only Apple" line.

    <snip>

    Note this monolithic structure is IMPORTANT because it's a huge
    reason why Apple iOS software is so buggy. They have to COLLECT
    all the bugs!

    Non sequitur. Release batching is a cadence choice, not a
    file-format property. Apple ships x.y.z security point releases
    all the time. Microsoft batches on Patch Tuesday. Same idea.

    As always, IT is utterly clueless.

    Just looking for attention it seems.
    --
    It's impossible for someone who is at war with themselves to be at peace with you.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nick Charles@none@none.none to comp.sys.mac.system,misc.phone.mobile.iphone,comp.sys.mac.advocacy on Sat Oct 31 02:33:31 2026
    From Newsgroup: comp.sys.mac.advocacy

    Brock McNuggets <brock.mcnuggets@gmail.com> wrote:
    On 30 Oct 2026, Nick Charles wrote in <ejCdnROYK7okp3j3nZ2dnZfqnPWdnZ2d@supernews.com>:
    Brock McNuggets <brock.mcnuggets@gmail.com> wrote:
    On 29 Oct 2026, Maria Sophia wrote in
    <11c15od$1pbh$1@nnrp.usenet.blueworldhosting.com>:
    Is iOS really a monolith or not? And why does it matter (a lot!)

    Packaging is not architecture. You keep conflating the two.

    <snip>

    When Apple ships an iOS update to an iPhone, it is packaged and
    delivered as a single, unified firmware image (an .ipsw file
    container).

    True for a restore/DFU. Not true for OTA, which is what almost
    everyone uses. Apple's own platform security guide says OTA
    updates download only the components required to complete the
    update, not the entire OS:
    https://support.apple.com/guide/security/secf683e0b36/web


    Apple cannot push a fragmented, a la carte bundle of separate,
    independent OS component packages to your phone the way Windows
    or Android can (outside of minor exceptions like the relatively
    new Rapid Security Responses). From the factory build pipeline
    to the end-user's download screen, it is treated, compiled, and
    deployed as a single block.

    A single signed, versioned release artifact is just how you ship
    a release. Android factory images are whole-partition images too,
    with block-level OTA deltas:
    https://source.android.com/docs/core/ota

    If "ships as one signed image" means monolith, then Android is a
    monolith too, and so is every Windows ISO. That undercuts your
    own "only Apple" line.

    <snip>

    Note this monolithic structure is IMPORTANT because it's a huge
    reason why Apple iOS software is so buggy. They have to COLLECT
    all the bugs!

    Non sequitur. Release batching is a cadence choice, not a
    file-format property. Apple ships x.y.z security point releases
    all the time. Microsoft batches on Patch Tuesday. Same idea.

    As always, IT is utterly clueless.

    Just looking for attention it seems.

    As always.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Brock McNuggets@brock.mcnuggets@gmail.com to comp.sys.mac.system,misc.phone.mobile.iphone,comp.sys.mac.advocacy on Fri Oct 30 19:44:50 2026
    From Newsgroup: comp.sys.mac.advocacy

    On 30 Oct 2026, Nick Charles wrote in <XoydnQQ87o3mznj3nZ2dnZfqnPidnZ2d@supernews.com>:
    Brock McNuggets <brock.mcnuggets@gmail.com> wrote:
    On 30 Oct 2026, Nick Charles wrote in
    <ejCdnROYK7okp3j3nZ2dnZfqnPWdnZ2d@supernews.com>:
    Brock McNuggets <brock.mcnuggets@gmail.com> wrote:
    <snip>

    As always, IT is utterly clueless.

    Just looking for attention it seems.

    As always.



    And we give it to him.
    --
    It's impossible for someone who is at war with themselves to be at peace with you.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.sys.mac.system,misc.phone.mobile.iphone,comp.sys.mac.advocacy on Fri Oct 30 23:08:01 2026
    From Newsgroup: comp.sys.mac.advocacy

    Nick Charles wrote:
    As always, IT is utterly clueless.

    Just looking for attention it seems.

    As always.

    The reason for this thread is the same reason I authored a plethora of
    threads about baseless claims you Apple religious zealot nutcases have been making for years.

    We need to put a stake in the ground with the truth in it, that we can reference in the future, because you religious nutjobs have no memory.

    We've proved the primitive monolithic iOS structure for years, but
    generally it is proven in tangent offshoots which are hard to find later.

    This thread will contain the truth. The facts. With links. Proving that the primitive monolithic method Apple uses is not what every other OS does.

    Just Apple.
    Nobody else.

    Note: Most of the facts predate the RSR, where Apple implemented a modern
    RSR mechanism (not the keyword "rapid") expressly because there were a tremendous number of bugs being exploited due to the time for the monolith.

    If anyone wants to prove me wrong, respond to the post with the details.
    Newsgroups: misc.phone.mobile.iphone,comp.sys.mac.advocacy,comp.sys.mac.system
    Subject: Re: Is iOS really a monolith or not? And why does it matter (a lot!)
    Date: Fri, 30 Oct 2026 20:39:08 -0400
    Message-ID: <11c3dba$2bv5$1@nnrp.usenet.blueworldhosting.com>

    Don't act like a nutcase by saying everything is wrong w/o saying what you think is right. That would just prove me 100% correct about you nutjobs.

    And don't twist my words by claiming that I said every line of code is
    inside a single file (which you nutjobs already tried), as that's absurd.

    If you're too ignorant to respond to the facts, don't prove me correct
    about you by you manufacturing something I didn't say, and attacking that.

    Prove me wrong about the monolith.

    HINT: You can't.
    --
    Apple nutcases hate how primitive Apple products are when you analyze them.
    --- 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 on Sat Oct 31 21:16:49 2026
    From Newsgroup: comp.sys.mac.advocacy

    On Fri, 30 Oct 2026 15:13:02 +0000, Nick Charles wrote:

    OF COURSE the full iOS (or whatever software) is fully rebuilt on
    ANY change.

    ThatrCOs not how modular systems work. For example, I run Debian
    Unstable, which is the close-to-the-bleeding-edge variant of Debian
    GNU/Linux. Every time I do a system update, there is a bunch of new
    packages. But these are only for the things that have changed --
    things that have not changed are NOT rCLfully rebuiltrCY.

    ThatrCOs how you know that a Linux distro is not a monolith.

    The build process is automated. Any file that is changed - even if
    it is just a text file for a help screen (no code at all) - can
    trigger a full rebuild.

    No reason why it should. Has Apple heard of the rCLmakerCY tool? This
    dates from the earliest days of Unix. ItrCOs designed to take a set of dependency rules, and, based on examining file modification dates,
    deciding which parts to rebuild, based on the fact that they depend on something that has changed. Parts that only depend on things that
    havenrCOt changed donrCOt need rebuilding.

    Has Apple heard of Unix?

    Unix is NOT monolithic. It was designed for easy portability/scalabilty. Which explains why it runs on everything from mainframes to watches.

    Umm, Linux certainly runs on rCLeverything from mainframes to watchesrCY.
    Also handheld gaming devices, media streamers, robots, supercomputers (including ones sent to outer space!), even a robot helicopter on
    Mars. Nothing from Apple does.

    I have been in software development for longer than you have been alive.

    But if that was only on Apple gear, not on actual Unix systems, then
    that could explain some of the things you seem to believe ...
    --- Synchronet 3.22a-Linux NewsLink 1.2