Re:Chrome extension manifest v3 proposal: comment from uBloc...
by behnamoh on Thursday May 30, 2019 @09:06AM
(#20050747)
Please define "better". I've used both Chrome and FF, and traditionally FF was more aimed at developers and heavy users. However, they lost that advantage over Chrome when their add-ons started to have forward compatibility issues.
Speaking of add-ons, I do miss FireBug. It was easy to find/define XPATHs by it (which is critical for web scraping). The new inspect element in FF just lacks that feature.
Just how GNU/Linux and macOS are traditionally more appealing to professionals and developers, FF should come to grips with targeting their own niche market. It's interesting how so many great ideas from these "niche" markets (e.g. Unix and Linux in the case of OSs) have surfaced in the more dominant, closed, commercial ones (i.e. Windows). If Mozilla want to really make the web a better place, they should know that by keeping their users happy (who are mostly developers), the ideas they put forth will sooner or later get spread in other browsers as well.
As another analogy, you might think about LISP and how the main ideas were later implemented in even the most imperative languages: although Lisp as we knew it is not dominant anymore, the ideas that made it different are still alive in Ruby, JS, etc.
Speaking of add-ons, I do miss FireBug. It was easy to find/define XPATHs by it (which is critical for web scraping). The new inspect element in FF just lacks that feature.
Just how GNU/Linux and macOS are traditionally more appealing to professionals and developers, FF should come to grips with targeting their own niche market. It's interesting how so many great ideas from these "niche" markets (e.g. Unix and Linux in the case of OSs) have surfaced in the more dominant, closed, commercial ones (i.e. Windows). If Mozilla want to really make the web a better place, they should know that by keeping their users happy (who are mostly developers), the ideas they put forth will sooner or later get spread in other browsers as well.
As another analogy, you might think about LISP and how the main ideas were later implemented in even the most imperative languages: although Lisp as we knew it is not dominant anymore, the ideas that made it different are still alive in Ruby, JS, etc.