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

    From Brock McNuggets@3:633/10 to All on Friday, October 30, 2026 08:33:42
    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.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Nick Charles@3:633/10 to All on Saturday, October 31, 2026 00:47:53
    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.


    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Brock McNuggets@3:633/10 to All on Friday, October 30, 2026 17:49:29
    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.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Nick Charles@3:633/10 to All on Saturday, October 31, 2026 02:33:31
    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.


    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Brock McNuggets@3:633/10 to All on Friday, October 30, 2026 19:44:50
    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.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)