←back to thread

Windows NT on 600MHz machine opens apps instantly. What happened?

(twitter.com)
752 points dceddia | 1 comments | 23 Jun 23 14:02 UTC | HN request time: 0.72s | source
Show context
guardiangod ◴[23 Jun 23 15:47 UTC] No.36448503[source]▶
Things Windows 10 has to content with when executing a new binary, that Windows 3.51 didn't

1. Windows Defender anti-virus checking the binary and contacting MS' server for binary signing/black list

2. Kernel32 trampolines

3. All sorts of security mitigation techniques such as stack cookies setup etc.

4. Telemetry

5. Hardware accelerated GUI initiation vs 'dump everything to frame buffer in kernel GUI32 library'

6. Load fonts, graphics etc. that can work well beyond 640x480

7. Deal with the scheduler juggling hundreds of processes that let you from accessing winsock2 lib immediately, to have multiplex sound mixing, to system restore, all in the background.

replies(5): >>36448542 #>>36448667 #>>36449660 #>>36450017 #>>36460707 #
chinathrow ◴[23 Jun 23 15:49 UTC] No.36448542[source]▶
> Windows Defender anti-virus checking the binary and contacting MS' server for binary signing/black list

Are you sure this happens every time you start an executable? I assumed the definition list gets updated in fixed intervals instead of whenever you launch a program.

replies(1): >>36448716 #
1. abwizz ◴[23 Jun 23 16:01 UTC] No.36448716[source]▶
i would assume that the information "when does user start program" is valuable and the list is finite, so there is some incentive to go for something in between.