31–40 of 218 posts
Earlier quoted context omitted.
Maintaining a fork of a large browser is extremely difficult, especially for coordinating and merging vulnerability fixes.
Do no other extension developers have this issue?
For those who aren't familiar, pentadactyl is a Firefox extension that transforms the user interface to make it more minimal and vim-like. You get to use standard vim bindings to navigate the web and it even gives you a vim-like command line interface to the browser's functionality.
I am not familiar with Web Extensions, but I am familiar with the fairly common event in which application vendors severely change functionality, with significant downstream effects. Such behavior seems more common amongst open-source products. Consider Python 3. Asterisk's scripting language. Perl 6. Incompatible version changes drive away users and developers. The uncertainty that comes along with a planned update…
I am not familiar with Web Extensions, but I am familiar with the fairly common event in which application vendors severely change functionality, with significant downstream effects. Such behavior seems more common amongst open-source products. Consider Python 3. Asterisk's scripting language. Perl 6. Incompatible version changes drive away users and developers. The uncertainty that comes along with a planned update…
Chrome....
Mozilla is turning Firefox into just another Chrome Browser...
Firefox 57 will like see me stop using FireFox it will be no different than chrome so I might as well just use chrome
>>and sometimes you have to break stuff to make it better
It is yet to be seen if it will be better, so far everything they are doing in firefox to make it more like chrome I am 1000000% opposed to.
Just curious will the new Web Extensions style allow add-ons like Classic Theme Restorer [1] and Tree-style Tab [2] that change the Firefox UI? [1] https://addons.mozilla.org/en-US/firefox/addon/classicthemer... [2] https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
The Classic Theme Restorer page says "CTR will stop working on Firefox 57 (release) when Mozilla drops support for XUL / XPCOM / legacy add-ons, but it will still work on Firefox 52 ESR until Firefox 59 ESR replaces it in 2018 (~Q2)."
This is going to kill pentadactyl, which is currently the only reason I'm using Firefox. For those who aren't familiar, pentadactyl is a Firefox extension that transforms the user interface to make it more minimal and vim-like. You get to use standard vim bindings to navigate the web and it even gives you a vim-like command line interface to the browser's functionality.
For those who don't mind, or prefer, a less comprehensive vim experience in the browser, I'm very happy with VimFx https://addons.mozilla.org/en-US/firefox/addon/vimfx/
It has a ton of vim commands, but I only use hjkl, g and gg. I never can remember whether search with / comes via VimFx or plain FF.
Firefox says it's compatible with multiprocess, but I don't know if it will survive through the switch to WebExtensions. It works fine now.
I am not familiar with Web Extensions, but I am familiar with the fairly common event in which application vendors severely change functionality, with significant downstream effects. Such behavior seems more common amongst open-source products. Consider Python 3. Asterisk's scripting language. Perl 6. Incompatible version changes drive away users and developers. The uncertainty that comes along with a planned update…
>>I am not familiar with Web Extensions, Chrome.... Mozilla is turning Firefox into just another Chrome Browser... Firefox 57 will like see me stop using FireFox it will be no different than chrome so I might as well just use chrome >>and sometimes you have to break stuff to make it better It is yet to be seen if it will be better, so far everything they are doing in firefox to make it more like chrome I am 1000000%…
Firefox probably won't phone google.
Isn't Firefox open source? Can't you just fork the project and start your own browser, where all these changes don't get made? Is the real concern about forking the userbase and ecosystem, and the fork won't have the critical user base to become self-sustaining? Edit: added paragraph for clarity.
Maintaining a fork of a large browser is extremely difficult, especially for coordinating and merging vulnerability fixes.
Mozillas browser.html project may be helpful too, but it seems to be a bit too experimental for now.