5 ms·
The challenge with not competing with Chrome is that websites are now mostly developed with Chrome as the dev-tool. Even large companies are just optimizing fo
by MattGaiser 6y ago
The challenge with not competing with Chrome is that websites are now mostly developed with Chrome as the dev-tool.
Even large companies are just optimizing for that one browser:
https://thenextweb.com/dd/2017/11/28/please-build-websites-web-not-just-google-chrome/ https://thenextweb.com/dd/2017/11/28/please-build-websites-w...
How many users are going to be willing to put up with stuff not working until they switch?
- causality0 6y agoFunctioning like Chrome in rendering and page features doesn't mean Firefox has to behave like Chrome in the UX. For example, why gut the ability of people to skin and customize their browser as they see fit? Why is Mozilla involved in a running battle against users who want the tabs below the address bar? Why entirely prevent us from sideloading extensions instead of letting us turn the ability on and off?
- afiori 6y agoI guess that for the first two the answer is in part managing complexity
- asddubs 6y agoand the last one is to reduce attack vectors
- dependenttypes 6y agoAh yes, the good old walled garden approach. Not very "open", is it?
- asddubs 6y agoi mean I don't like it either, but I do believe them in this instance that it's mostly in service of not letting installers just sneak in a toolbar
- dependenttypes 6y agoI think that this is misguided. If a malicious installer sneaks in toolbars it can also install a keylogger/send all of your data to a server/install a firefox fork with the toolbar preinstalled/etc. If anything this kind of thing only hurts the users that know what they are doing (such as someone wanting to install a 3rd party addon or someone wanting to install addons via nix).
- notriddle 6y ago> If a malicious installer sneaks in toolbars it can also install a keylogger/send all of your data to a server/install a firefox fork with the toolbar preinstalled/etc. If it's totally rogue malware, sure. The toolbars, on the other hand, were coming from companies like Oracle that operated entirely within the bounds of the law.
- dependenttypes 6y agoInstalling a firefox fork is also within the bounds of the law.
- TimSchumann 6y agoThis is the main thing I’m concerned with. Instead of adhering to an open standard, everything becoming ‘whatever google says goes’.
- cotillion 6y agoThe Firefox bug report for a websocket message inspector was opened 7 years ago. It took 6 years before it got implemented. Its no wonder they lost marketshare among developers.
- TimSchumann 6y agoAgree with this sentiment 100% - it’s not better, it’s just less evil.
- pjmlp 6y agoI can find similar examples in Chrome, yet that doesn't detain some devs to worship it.
- MattGaiser 6y agoYes, but Chrome is considered the default. If something doesn't work in Chrome, I will get in trouble with my boss for implementing it. If something doesn't work with Firefox, we tell the users to use Chrome.
- pjmlp 6y agoSo just like IE 6, some things never change in spite people telling otherwise.
- xxs 6y agoMake better and paid/subscription based(!) dev tools, instead screwing the UI and disabling add-ons. People are buying jetbrains products even though free ones exist. I do use firefox but all the auto-update features are off on desktop. On mobile I am/will be stuck with 68 forever, I suppose as well.
- usrusr 6y agoPerhaps FF developer edition was meant to test the waters for this approach? Do web people actually use that? I never got to the point of making it part of my process, but I'm not doing enough web to really have a process. In any case, a dev browser can only be relevant if it's representative of end user browsers. The history of browser wars has shown that a superior dev experience can be a decisive factor in winning users, but it can never be more than a supporting role. These days a far more plausible dev level monetization angle would be Mozilla's unique position as the origin of Rust. Spin out a Rust subsidiary that sells service and perhaps also some premium tooling/SaaS in the open market while doing work on Rust/Servo/FF for a nominal fee that allows both sides to keep the lights on. But that (just like paid browser dev tools) would be B2B and apparently Mozilla Corp completely fails to see itself as a B2B actor outside of consumer eyeballs deals like the Google deal and the increasingly outbrainy start tab fillers. But failure to go that way is hardly surprising. Where would the business skillset come from when the entire organizion outside the tech teams has more in common with the great money furnaces of Wikimedia than with anything else? The only way I can see for that kind of transition to go well would be some form of merger/acquisition with someone already existing in those fields (consultancy and/or tooling). "you take the engineers, we'll be buying services". But the successful ones would be very reluctant to suddenly load themselves with the entirety of Rust. It would probably take someone owner-managed who brought a decent amount of idealism into the equation. Total number of candidates might amount to zero.
- pjmlp 6y agoThe anti-IE generation is mostly to blame for that, they ended up adopting the behaviours they criticized so much.
- MattGaiser 6y agoIE made life miserable for developers. I am not sure we would have cared if it were not moribund.
- ohgodplsno 6y agoWhereas Chrome makes life miserable for users not using Chrome, because of the sheer amount of non-standard, Chrome-only features used in current webdev.
- harshitaneja 6y agoWhich non-standard features?
- ohgodplsno 6y agoUsing google properties is a bit of an easy jab, but: Youtube using polymer/shadowdomv0 and absolutely destroying performance on Firefox is a an easy example. Google Earth used non-standard APIs. Otherwise, have a quick search for "non-standard" on MDN, and see how many of those Chrome implements.