3 ms·
It's even more so true. The complexity of kernel calls is much higher when custom memory and scheduler involved I'd say. Getting Office running is probably rath
by kerng 8y ago
It's even more so true. The complexity of kernel calls is much higher when custom memory and scheduler involved I'd say. Getting Office running is probably rather simple in comparison.
- jcelerier 8y ago> The complexity of kernel calls is much higher when custom memory and scheduler involved I'd say I really don't think so. MS used to render scrollbars in the kernel (was still the case in early Win10 versions)
- geofft 8y agoI believe TrueType fonts are still rendered in kernel mode. (They have a policy option for blocking untrusted fonts, because of course that parser has bugs.)
- ryuuchin 8y agoAlthough the rendering may still be done in kernel mode the parsing is now done in a usermode sandbox[1] which significantly reduces risks from handling untrusted fonts. [1] https://blogs.technet.microsoft.com/secguide/2017/06/15/dropping-the-untrusted-font-blocking-setting/ https://blogs.technet.microsoft.com/secguide/2017/06/15/drop...
- mrweasel 8y agoMSSQL is basically a small OS, it uses very few system calls, around 50 if I remember the Microsoft presentation correctly. That’s not to say that porting was easy, but rely very little on the underlaying OS. Porting Office is most likely much more work, just to get the GUI working.