On Thu, 3/27/2025 5:31 PM, Joel wrote:
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
Microsoft is trying to reduce the time it takes to start Office on
Windows, by moving part of the work to the time when you boot your PC
<https://www.theverge.com/news/637469/microsoft-office-speed-boost-faster-launch>.
What a wonderful idea: make an app start faster by making your machine
take longer to boot. What if other major Windows apps did the same
thing? Wouldn’t it be cool to have all these apps lurking in the
background, already running, chewing up memory and CPU cycles?
This would be a good example of why I used LO under Windows, and
ignored Office.
Metro Apps have a different state diagram than Win32 programs.
If you look in Task Manager, you can sometimes already see
something sitting there in the Suspended state (it's like a TSR).
https://i.sstatic.net/lrTZh.png
You need to find a more detailed version of that diagram, because
below the "Suspended" ball, is a "Terminated" ball. If
MSWord had gone to the "Suspended" state, and some other
activity on the computer needed a lot of RAM, the Suspended
APP can Terminate and the resources get harvested.
But otherwise, the image can sit in RAM, waiting for a time
to be re-invoked. And that shortens the load time, because
it is already there.
What TheVerge article is telling you, is the state diagram
likely has more sticks added to it. Previously, the loader
would have loaded an App right to the Running state, and
it would have taken time for the App to move to the Suspended state
(because "there was nothing to do"). The change they
are proposing, would be for the loader to load an App
right to the Suspended state, so that when it is actually
invoked again (by the user this time), it will move from Suspended
to Running faster.
Paul
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 1,030 |
Nodes: | 10 (1 / 9) |
Uptime: | 22:45:24 |
Calls: | 13,346 |
Calls today: | 3 |
Files: | 186,574 |
D/L today: |
1,683 files (457M bytes) |
Messages: | 3,357,683 |