Live data from Hacker News

State of web browsers in 2018

ferdychristant.com

21–30 of 217 posts

Re: State of web browsers in 2018

#21

There is a different way to interpret this: Firefox is irrelevant on mobile, but not on Desktop. Will mobile kill desktop? No, these are two different markets/use-cases/applications. Just like video didn't kill the radio*. Firefox will stay relevant on desktop a.k.a. in work environments.

i want to use Firefox mobile but the scrolling experience is terrible. not sure if they use the os's compositor.

Re: State of web browsers in 2018

#22
post #15

As good a place as any to ask something I've been wondering about: Is a Chromebook a complete computing environment now that WebAssembly is getting adoption?

Depends on your definition of "complete" -- ChromeOS now has Android and Linux container support, so you've got options for command-line apps. Ironically, you have to run Electron apps (based on Chromium) in a Linux VM.

Re: State of web browsers in 2018

#24
post #11

As a Mozilla employee, speaking from my own limited perspective, it seems the company as a whole broadly agrees with this analysis even if it isn't vocalized quite this succinctly. Chrome started out being force-installed alongside Flash, and there is no solution to the bundling problem -- the problem is even larger in scale than the article suggests because of Chromebooks affecting desktop. People who use Firefox in…

How well is Gecko/Servo suitable for embedding in another application as a web browser? Apparently it is very easy with Chrome, why we have 25+ Chrome derivatives.

Re: State of web browsers in 2018

#25
post #4

We're getting to the point where browsers are worthy of the decades old criticism Emacs has received. They have eventually become an OS with many fine features - simply lacking a good web browser. It's a large, sprawling project to make a good OS. Especially when the language of choice to run on it changes with such haste. Hopefully this nth re-imagining of dumb terminals dies off over the next few years and applicat…

I feel sad that through so many years of progress we ended up with multicore CPUs, obscene amounts of RAM, graphics cards that can heat a house... all to power one or more web browser engines.

While running our software in someone's else computer.

Re: State of web browsers in 2018

#26
Great read, although I thought it wasn't quite cynical enough about the bad things Chrome can do with Blink (is that their rendering engine? Whatever it's called, I forget, but it doesn't really matter) dominance: the article suggested that the way forward is to ensure that the standards process has equal representation, and I agree with that, but once all the other browsers are using your rendering engine you don't have to care about the standards process. Just like IE back in the day, or Netscape before that, you can introduce a blink tag and everyone else has to do it or it gets to be standardized later to be compatible with what you've done. The standards process becomes more or less useless every single time we get into this situation. Google's already doing this to a certain degree, see also SPDY and QUIC, or any of the various Chrome-only CSS things that everyone else adopts. For SPDY/QUIC they're still working within the process, but they basically get to force their baseline without any competition even so. Later they won't even have to pretend to work within the process.

Re: State of web browsers in 2018

#28

Firefox for mobile is an excellent browser, and the only one I use. It supports extensions, such as uBlock without rooting the phone. The user interface is good, the browser is responsive and reasonably fast. Honestly, I don't know why people aren't using it. I think most people just don't care, and just use what the system provides. As Google gets more invasive and evil, I hope that people will start to care, and Fi…

> The user interface is good, the browser is responsive and reasonably fast.

Ever used chrome or some other browser on android? The droidfox is quite infamous for it's slowness and backward interface.

Re: State of web browsers in 2018

#29

There is a different way to interpret this: Firefox is irrelevant on mobile, but not on Desktop. Will mobile kill desktop? No, these are two different markets/use-cases/applications. Just like video didn't kill the radio*. Firefox will stay relevant on desktop a.k.a. in work environments.

Firefox has some catches that make it not as easy to use in a work environment though and I honestly think will hurt their market share over time, mainly the fact that it doesn't use the OS cert store. This causes issues with most corporate web proxies that do SSL inspection since IT departments will push the proxy CA cert into OS cert stores through whatever endpoint management solution they have. People can disagre…

Interestingly enough, a previous customer only allowed for FF ESR and IE, while considering a security breach having anyone to try to install Chrome.

Re: State of web browsers in 2018

#30
post #19
post #2

Amazing read! Very insightful and open at the same time. I've literally highlighted every other sentence in it. Thank you, Ferdy! I basically went through the same thinking process myself. I'm a moderate idealist and would like Firefox to succeed because it's important for the web that there's no monopoly. However, my realist soul tells me that Firefox is losing badly and it's hard to tell where it's going to end. It…

> I'm afraid that it will look like a Cold War's arms race – one of the parties will invest so much that the other will just lose economically (not being able to afford that many developers). Given all the "Safari is the new IE6" posts that have been here over the past few years, that seems to be already happening. Apple is lagging behind quite a bit with implementing newer web standards, especially in areas where th…

I'm not sure how long they can keep doing so. At what point it may affect iOS's reception in general?

From my own experience, making the app I'm working on (CKEditor 5 - a web based rich-text editor) compatible with mobile Safari is right now impossible. None of the RTEs work well in mobile Safari because of its quirks and bugs.

If Apple will overdo this (just like Microsoft did with IE6), that may affect iOS's usefulness. Sure, right now you can't build a business without your presence there, but there may be a breaking point. It's hard to imagine and I kinda doubt it will happen (I rather agree with the author of this article that Apple will invest enough to keep Safari alive), but it's a possibility. Microsoft screwed it up once, so can Apple.

Post reply on HN