2 ms·
That kind of problem used to happen with DOS TSRs (the equivalent of multitasking extensions or daemon processes). It's funny to think that the reason for brows
by schoen 12y ago
That kind of problem used to happen with DOS TSRs (the equivalent of multitasking extensions or daemon processes). It's funny to think that the reason for browser extension incompatibilities is kind of analogous to the reason for TSR incompatibilities: both of them will hook function calls in the system whose functionality they're extending, and make assumptions about how they can alter, act on, or cancel the function call without breaking things, and whether or how it needs to be passed along afterwards. If only one extension is loaded, these assumptions aren't stressed very much, but when several are loaded the assumptions can conflict.
(That analogy isn't perfect because the TSRs also had an issue about patching the interrupt descriptor table, which is where the system looks up the location of an interrupt handler; one common problem was that if TSRs weren't unloaded in the same order in which they were loaded, the table could be "restored" with values that were not actually current, which I don't think is a problem that has an equivalent for browser extensions!)