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.
Thinks that every iOS update is the ENTIRE 10GB
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.
Is iOS really a monolith or not? And why does it matter (a lot!)
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.
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!
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.
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.
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.
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.
Brock McNuggets <brock.mcnuggets@gmail.com> wrote:<snip>
On 30 Oct 2026, Nick Charles wrote in
<ejCdnROYK7okp3j3nZ2dnZfqnPWdnZ2d@supernews.com>:
Brock McNuggets <brock.mcnuggets@gmail.com> wrote:
As always, IT is utterly clueless.
Just looking for attention it seems.
As always.
As always, IT is utterly clueless.
Just looking for attention it seems.
As always.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:18:43 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,563 |