Live data from Hacker News

State of web browsers in 2018

ferdychristant.com

1–10 of 217 posts

Re: State of web browsers in 2018

#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's a pity that Microsoft didn't choose Gecko – I wonder if they even seriously considered it.

With Microsoft joining Chromium, we're slowly entering a duopoly of WebKit and Chromium. It's still a much better situation than the dark IE6 times. However, it's hard to tell whether WebKit (AFAIU, supported mainly by Apple and Samsung) will keep up with Chromium (Google and Microsoft) in a long term. 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). Such economical wars make developers happy, because the web progresses very fast, but I think it actually leads to a monopoly.

Anyway, I'm still keeping my fingers crossed for Gecko. They do a great job there and perhaps will be able to partner with a big enough company to keep its pace and market share.

Re: State of web browsers in 2018

#3
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.

Re: State of web browsers in 2018

#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 applications go back to the OS where they belong. Otherwise thing are going to get rough.

Re: State of web browsers in 2018

#5
If it had been introduced today, would PNaCl have been rejected which ultimately lead to a better solution (WASM), or would it have been broadly accepted since it had sufficient market reach though Chrome?

Re: State of web browsers in 2018

#6

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 is irrelevant on mobile

That's pretty sad, considering the fact it's the only mobile browser not only with the support of extensions, but the same extensions as the desktop version.

Future might not be that grim for mobile Firefox actually, with more and more modern Android smartphones and tablets support more and more RAM, and 4GB is pretty much standard.

Re: State of web browsers in 2018

#7
> At least those browsers are compatible with the web. Websites will work in them because websites are built to work in Chromium.

That is a poorly drawn conclusion. Edge is compatible with the web. Developers are solely developing for Chrome and not caring for cross browser testing. As a Firefox user I sometimes encounter this myself.

Re: State of web browsers in 2018

#8

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 disagree all they want about SSL interception in a corporate environment (for good reason), but it's here to stay. When a corporate user downloads Firefox, tries to simply go to Google and gets a cert error page, they're just going to go back to Chrome because the process of exporting your company's CA cert and then importing it into Firefox so you can use the browser is just simply not feasible for most users.

Re: State of web browsers in 2018

#9
post #6

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 is irrelevant on mobile That's pretty sad, considering the fact it's the only mobile browser not only with the support of extensions, but the same extensions as the desktop version. Future might not be that grim for mobile Firefox actually, with more and more modern Android smartphones and tablets support more and more RAM, and 4GB is pretty much standard.

Mobile Firefox didn't support all extensions last I checked. It at least has uBlock Origin on Android, but almost everything else I looked for wasn't available. Firefox on iOS doesn't support them at all.

Re: State of web browsers in 2018

#10
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.
Post reply on HN