3 ms·
Needing javascript that embeds in every page for basic mouse and keyboard behaviour is insane. No clue why they decided it should be the only viable option.
by contravariant 6y ago
Needing javascript that embeds in every page for basic mouse and keyboard behaviour is insane. No clue why they decided it should be the only viable option.
- wizzwizz4 6y agoIt isn't intended to be. But supporting the old APIs meant that they had to have Microsoft levels of backwards-compatibility. • You want to refactor XUL so it doesn't duplicate features of HTML5? Whoops; you broke all the extensions. • You want multi-threading? What a shame; that API over there assumes it'll always be called from the main thread. • Update that database table's schema to store more data? Bah. Make another table, or you'll break extensions When every implementation detail is part of your interface, bad things happen.
- liability 6y agoFine, XUL had to go. But where is the replacement? How many more years should we expect Mozilla to need to implement configurable bindings? It doesn't even need to be extension-accessible, just give users a tab in the preferences menu like damn near any other application has been doing since the dawn of GUIs. Do they even have one engineer working on this?
- wizzwizz4 6y agoConsidering they fired half the people working on this, probably not.