Hacker News new | ask | show | jobs
by 482794793792894 3240 days ago
They are trying to move away from the old extension API (because maintaining that ate up a crap ton of resources, so don't come up with that move being a waste of resources) and Tree-Style Tabs is not yet compatible with this new API.

The Vertical Tabs test pilot thing was them demonstrating that it could be done (including to themselves, they need to test these APIs) and giving the community something to work with, should no other tree tab extensions crop up before the deprecation of the old API.
1 comments
noisem4ker 3240 days ago
>The Vertical Tabs test pilot thing was [...] to test these APIs

Except that Tab Center wasn't a way for them to test the new WebExt APIs, as it was still based on XUL. See here: https://discourse.mozilla-community.org/t/whats-all-this-abo...

>maintaining [the old extension API] ate up a crap ton of resources, so don't come up with that move being a waste of resources

Arguably not a waste if that meant preserving the most powerful extension environment out there, and also one of the very few reasons for people to stay with Firefox.

Signed: a Firefox user

link
addicted 3240 days ago
The old extensions were not compatible with e10s.

If the Firefox team wanted to improve speed/security/modularity, etc. they had to ditch the old extension model.

It sucks, but necessary.

link
dingo_bat 3240 days ago
"Not compatible" is just another way of saying "we don't have the resources and/or the inclination to support your programs". Look at what Microsoft does to ensure backward compatibility. They simulate specific windows bugs for specific old games that were coded to expect the original bug in Win95. Just so users' programs keep working. It's a matter of priorities and resources. And I believe both are out of whack at Mozilla right now.
link
noisem4ker 3240 days ago
>The old extensions were not compatible with e10s.

Addons based on older APIs could be made compatible with the newer multiprocess design (see https://developer.mozilla.org/en-US/Add-ons/Working_with_mul... ) and for a while Mozilla tried to persuade developers to update theirs (see https://blog.mozilla.org/addons/2016/08/02/multi-process-fir... )

It was only not long after that when Mozilla's fresh direction decided to start pushing the WebExtensions bandwagon only while dropping everything else, in spite of the thousands of man-hours invested by the addon developers (many of which, you can understand, were not happy; see http://fasezero.com/lastnotice.html )

>they had to ditch the old extension model

To me, that's more like a political decision they made at an arbitrary point in time.

link