3 ms·

true. their api is now a dumbed down version of chrome. I still remember the days of vimperator and treetabs in xul. firefox did this to themselves. they dont

by hbt 5y ago

true. their api is now a dumbed down version of chrome. I still remember the days of vimperator and treetabs in xul. firefox did this to themselves. they dont deserve support.

ohgodplsno 5y ago
Tree Style Tabs exists: https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/ https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta... Vimperator replacements exist: https://github.com/tridactyl/tridactyl https://github.com/tridactyl/tridactyl Additionally, XUL was a steaming pile of shit, and there was no saving it. Multithreading was only possible by ripping out XUL.
- eitland 5y ago
  > Additionally, XUL was a steaming pile of shit, and there was no saving it. Multithreading was only possible by ripping out XUL. Being hostile to people who ask nicely about getting some necessary features into the new API however, that is optional. Same goes for extracting all the money from Firefox and sacking important dev teams while continuing less important charity work.
- hbt 5y ago
  I use and forked SurfingKeys on Chrome https://github.com/hbt/Surfingkeys https://github.com/hbt/Surfingkeys Calling tridactyl a replacement for vimperator ignores all the features and extensive customization available through the old Firefox API. I've used vimperator and pentadactyl and tridactyl doesn't even come close (because of the awful API limitations). My point is: Firefox API is now a cheap version of Chrome API. Why would you develop extensions for Firefox instead of Chrome? As a power user, it makes no sense to support Firefox. It offers less than chrome. They had firebug back when Chrome dev tools was crap, an amazing API for extensions and customization; they threw it all away for this mediocre crap chasing average users and are now playing the privacy / save the web card and guilt tripping people for not choosing them. They can offer better APIs, they are not entitled to power users. Power users write extensions, write tools for web developers, developers are the most importance resource. Who even bothers to test on Firefox now? For what, 7% market share? All that money and support; just all gone. Complete waste. Anyway, I sunk a lot of time into Firefox over the years and it was my browser of choice for years; I'm definitely still bitter about it. They literally abandoned power users. Fuck them.
- kasabali 5y ago
  > Additionally, XUL was a steaming pile of shit, and there was no saving it. Multithreading was only possible by ripping out XUL. Nah, multi threading has always been there (because it's doing networking and IO at least) and multi process support landed shortly before Quantum release.
- creatonez 5y ago
  > Multithreading was only possible by ripping out XUL. Firefox still uses XUL, it's just not an exposed API
starky 5y ago
Yeah, I've got zero interest in using their software after they broke TreeStyleTabs, what replaced it was crap. I'm quite happy with Vivaldi, which, while based on Chrome, at least seems to understand what users need.

by hbt 5y ago

true. their api is now a dumbed down version of chrome. I still remember the days of vimperator and treetabs in xul. firefox did this to themselves. they dont deserve support.

ohgodplsno 5y ago

Tree Style Tabs exists: https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/ https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta... Vimperator replacements exist: https://github.com/tridactyl/tridactyl https://github.com/tridactyl/tridactyl Additionally, XUL was a steaming pile of shit, and there was no saving it. Multithreading was only possible by ripping out XUL.

eitland 5y ago
> Additionally, XUL was a steaming pile of shit, and there was no saving it. Multithreading was only possible by ripping out XUL. Being hostile to people who ask nicely about getting some necessary features into the new API however, that is optional. Same goes for extracting all the money from Firefox and sacking important dev teams while continuing less important charity work.
hbt 5y ago
I use and forked SurfingKeys on Chrome https://github.com/hbt/Surfingkeys https://github.com/hbt/Surfingkeys Calling tridactyl a replacement for vimperator ignores all the features and extensive customization available through the old Firefox API. I've used vimperator and pentadactyl and tridactyl doesn't even come close (because of the awful API limitations). My point is: Firefox API is now a cheap version of Chrome API. Why would you develop extensions for Firefox instead of Chrome? As a power user, it makes no sense to support Firefox. It offers less than chrome. They had firebug back when Chrome dev tools was crap, an amazing API for extensions and customization; they threw it all away for this mediocre crap chasing average users and are now playing the privacy / save the web card and guilt tripping people for not choosing them. They can offer better APIs, they are not entitled to power users. Power users write extensions, write tools for web developers, developers are the most importance resource. Who even bothers to test on Firefox now? For what, 7% market share? All that money and support; just all gone. Complete waste. Anyway, I sunk a lot of time into Firefox over the years and it was my browser of choice for years; I'm definitely still bitter about it. They literally abandoned power users. Fuck them.
kasabali 5y ago
> Additionally, XUL was a steaming pile of shit, and there was no saving it. Multithreading was only possible by ripping out XUL. Nah, multi threading has always been there (because it's doing networking and IO at least) and multi process support landed shortly before Quantum release.
creatonez 5y ago
> Multithreading was only possible by ripping out XUL. Firefox still uses XUL, it's just not an exposed API

starky 5y ago

Yeah, I've got zero interest in using their software after they broke TreeStyleTabs, what replaced it was crap. I'm quite happy with Vivaldi, which, while based on Chrome, at least seems to understand what users need.