3 ms·
Less resource pressure. No need to fit in 64 MB when you have 2,000 MB. Less experienced programmers (only know the latest thing; promoted to mediocre project
by demondemidi 3y ago
Less resource pressure. No need to fit in 64 MB when you have 2,000 MB.
Less experienced programmers (only know the latest thing; promoted to mediocre project leads... while the Old Guard doesn't pass on their knowledge before retiring)
Poorly documented code resulting layered workarounds (MS code from the 80's and 90's was hot garbage in terms of comments; source: I worked on Win95 diplay drivers and didn't comment any of my 16-bit VXDs. See previous gripe about O.G. being bad at documentation)
Bloated libraries (ironically, reluctance to jettison old code that is not well understood, so patch around it and keep dragging the baggage to the next release.)
Insufficient test suites causing too much bloat (see previous comment).
More complex APIs (spywhere and integrations everywhere).
I haven't walked the Windows source tree in 30 years, it would be fascinating to see a breakdown of the kernal linker map summaries.