News for hackers. Stuff that matters.
Re:State of web browsers in 2018 by sstangl on Thursday December 06, 2018 @10:27AM (#18618740)
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 the future will increasingly be people who do so consciously, presumably because they view Mozilla as helping them protect their privacy. Chrome is and will continue to be the default.

Eventually, Google will do something that is an abuse of their monopoly power. Either there will eventually be a privacy/creepiness fiasco, or Google will attempt to use Chrome as leverage to squeeze a competitor out of a market.

When that happens, Mozilla will be well-positioned as an alternative. The path forward in this view would look more like Mozilla as a constellation of disaffected companies and users attempting to free themselves from Google. It won't look like Mozilla on the side doing something by itself. We will largely be defined in opposition to Google.

The article correctly points out that a wiser Microsoft could have gotten a head-start on this inevitability by partnering with us early.

Re:State of web browsers in 2018 by Yizahi on Thursday December 06, 2018 @11:22AM (#18619347)
Arguably Google is already abusing their monopoly power but in the way that people like. I'm talking about AMP. In the future AMP/regular page boundary will blur and Chrome/GSearch/AMPpages will merge in the ubiquitous googlenet hosted on google servers (because it will work better than regular internet pages). Almost everybody will be happy after this and Mozilla will fall into obscurity.

Basically you can't create a revolution in tech by failing once and then trying harder the second time and it looks like Mozilla failed even while being better. The only way for Mozilla to win is (like linked article suggests) is to dominate somewhere else and then leverage that to push web browser. They won't do this and don't want to really.

PS: maybe they could buy/merge with other privacy oriented players in tech and create end-to-end privacy services that are usable, seemingly secure and integrated and then push this offering. But I can't see a big market today for this offer if it would exist.

PPS: also to add to less known evil moves by Google - their U2F websites refuse to work in Firefox, despite it supporting U2F for a long time.

Re:State of web browsers in 2018 by Wowfunhappy on Thursday December 06, 2018 @01:54PM (#18620917)
> Arguably Google is already abusing their monopoly power but in the way that people like. I'm talking about AMP.

Do people actually like AMP?

I hate it and strongly wish I could disable it for all Google search results. It's supposed to make pages load in more quickly, but for some reason they always seem to be slower for me.

Re:State of web browsers in 2018 by untog on Thursday December 06, 2018 @02:30PM (#18621243)
Broadly speaking, yes they do. It is faster in the vast majority of cases, and non-techie friends of mine speak enthusiastically about the lightning bolt icon. Of course, they don't understand the implications of it.
Re:State of web browsers in 2018 by Izkata on Thursday December 06, 2018 @02:43PM (#18621342)
> and non-techie friends of mine speak enthusiastically about the lightning bolt icon.

Which makes me think it's just confirmation bias. They expect it to be faster, and so perceive it as faster. Just like when Windows Vista was presented to users as the new Windows 7 (only the branding was changed for the experiment), and they openly stated it was noticeably better/faster than Windows Vista.

Re:State of web browsers in 2018 by Wowfunhappy on Thursday December 06, 2018 @02:50PM (#18621431)
I'm not quite so quick to dismiss this out of hand, despite my own (negative) experiences with AMP.

Google is certainly capable of making mistakes, but I find it hard to believe they would invest so much into AMP without strong metrics to indicate that AMP pages load faster overall. And on a theoretical level, the explanations of why AMP should be faster also make sense.

Re:State of web browsers in 2018 by Izkata on Thursday December 06, 2018 @03:38PM (#18621957)
Note the phrasing, that's an important part of what I'm referring to: they're talking about the icon instead of the speed directly.
Re:State of web browsers in 2018 by kiriakasis on Sunday December 09, 2018 @06:10AM (#18640313)
In my experience it is the google search app that is extremely slow (android on a underpowered nokia 6) I installed duckduckgo search because google hangs my device for a few second every 5-6 keypresses
Re:State of web browsers in 2018 by jcranmer on Thursday December 06, 2018 @12:00PM (#18619748)
> PPS: also to add to less known evil moves by Google - their U2F websites refuse to work in Firefox, despite it supporting U2F for a long time.

The one that still sticks in my craw is that they never bothered to add support for Hangouts in Firefox. Hangouts was modified to use WebRTC in Chrome, but relied on a plugin in Firefox--despite Firefox actually implementing the relevant WebRTC features first.

Re:State of web browsers in 2018 by larrik on Thursday December 06, 2018 @12:21PM (#18620018)
Hmm, I use Hangouts in Firefox...
Re:State of web browsers in 2018 by cpeterso on Thursday December 06, 2018 @01:46PM (#18620830)
Hangouts supports WebRTC video in Firefox now, four years after supporting WebRTC in Chrome (2014-2018).

I've maintained a timeline of Hangouts' WebRTC support (as part of my work to track the sunsetting of NPAPI plugins, other than Flash, in Firefox that blocked Win64):

https://wiki.mozilla.org/Firefox/Win64#History

Re:State of web browsers in 2018 by kenhwang on Thursday December 06, 2018 @01:35PM (#18620724)
The chat or the video? The video hasn't worked in long time now.
Re:State of web browsers in 2018 by Wowfunhappy on Thursday December 06, 2018 @01:56PM (#18620923)
I haven't tried Firefox, but Hangouts with video works in Safari for me.

I had to bookmark a Hangouts room URL though, which I think I opened from within GMail some time ago. If I try to just load hangouts.google.com, it won't work.

Re:State of web browsers in 2018 by larrik on Friday December 07, 2018 @02:06PM (#18630534)
Video, although I don't have a camera (the host does, though).
Re:State of web browsers in 2018 by dmitriid on Thursday December 06, 2018 @01:01PM (#18620415)
A recent example is how Chrome broke audio on a lot of websites https://www.theverge.com/2018/5/15/17358752/google-chrome-66...

I won't even link to the discussion in Chrome's bugtracker, Chrome team didn't even test the change, apparently.

They also actively build "Chrome-only" websites.

Re:State of web browsers in 2018 by Wowfunhappy on Thursday December 06, 2018 @02:12PM (#18621074)
The Chrome audio thing really, really bothers me.

The change broke a ton of neat, interesting games that are never going to be updated. And given Google's aggressive autoupdates, running an older version of Chrome to experience a specific old website is non-trivial.

The change signals a blatant disregard for preserving pieces of art, culture, and shared history.

Re:State of web browsers in 2018 by untog on Thursday December 06, 2018 @02:29PM (#18621232)
IMO that's not an abuse of monopoly thing at all. It's not as if removing auto-play audio will push users towards some Google-only product, if anything it would mean fewer users choosing Chrome.
Re:State of web browsers in 2018 by kiriakasis on Sunday December 09, 2018 @06:14AM (#18640328)
Disagree. It can be a push for web developers and amateur site-buildign-people-that-have-not-that-much-interest-in-the-web-shenanigans to use google-approved APIs.

Not by promoting google as better but by simply promoting a view of google-web and other-web.

Re:State of web browsers in 2018 by SamWhited on Thursday December 06, 2018 @11:16AM (#18619277)
> Eventually, Google will do something that is an abuse of their monopoly power.

This is one of Mozilla's problems: they constantly advertise privacy, etc. and while I agree their views in general, most users don't care. If you position yourself as the privacy respecting web browser, you will only ever get the tiny niche of people who care and everyone else who sees your marketing will just roll their eyes and makes jokes about tinfoil hats. That's not to say that Mozilla should do all the anti-competitive things Google does, just that they need to stop advertising themselves this way if they ever want to get any reasonable market share back (unless they want to be a niche browser for people who don't like Google, which is fine if that's all they want to do).

That being said, I don't see how any amount of marketing can fix Mozilla's problem for the same reasons the article pointed out.

Re:State of web browsers in 2018 by organsnyder on Thursday December 06, 2018 @11:26AM (#18619388)
During the IE-6 dark ages of the early 2000s, Mozilla's browser (the Mozilla suite, then standalone Firebird, finally renamed to Firefox) was positioned in a similar way: it was the niche browser for people who cared about an open web. It stayed that way for quite a few years, slowly gaining traction by implementing features—tabbed browsing, popup blocking—not found in the dominant IE browser.

I could see a similar approach working again. Mozilla could focus on user-centric features, while Chrome has to also serve the needs of Google's business interests.

Re:State of web browsers in 2018 by laumars on Thursday December 06, 2018 @12:25PM (#18620057)
> the Mozilla suite, then standalone Firebird, finally renamed to Firefox

I believe it was originally called Phoenix. Though you're right it was then called Firebird and renamed again to Firefox afterwards.

I think each time was due to trademark disputes?

Going to your point though, I hope you're right but I'm a bit more sceptical. Chromium, being open source, means anyone who doesn't like the stagnation of Chrome would just fork Blink and create their own modern browser while still enforcing the Chrome mono-culture.

I'd love to see Gecko take off in the same way kHTML, webkit and blink have done. In fact I'm surprised it hasn't. I don't suppose anyone more familiarity with the code base of these rendering engines are able to offer possible reasons why?

Re:State of web browsers in 2018 by newscracker on Saturday December 08, 2018 @11:28PM (#18639294)
> I'd love to see Gecko take off in the same way kHTML, webkit and blink have done. In fact I'm surprised it hasn't. I don't suppose anyone more familiarity with the code base of these rendering engines are able to offer possible reasons why?

Not familiar with the code base of the engines, but one factor that distinguishes Gecko vs. the other engines is that Mozilla killed the ability to embed Gecko in other applications in 2011. Read about the detailed reasoning in this mailing list thread. [1] This effectively tied Gecko solely to Firefox, and has made using it with other applications or browser chrome (lowercase, not Chrome the browser) impossible (AFAIK). So it cannot take off like the other engines unless Mozilla puts in work to allow that to happen.

[1]: https://groups.google.com/forum/m/#!topic/mozilla.dev.embedd...

Re:State of web browsers in 2018 by Izkata on Thursday December 06, 2018 @02:47PM (#18621408)
And they already have (at least) one they could use as a starting point: Containers
Re:State of web browsers in 2018 by skykooler on Thursday December 06, 2018 @03:42PM (#18622006)
Which is an excellent feature. Another one is WebVR.
Re:State of web browsers in 2018 by SamWhited on Friday December 07, 2018 @10:38AM (#18628519)
I love containers, and I'm sure webvr is great, but I can't see the majority of people caring at all about either one. Their existing niche of privacy aware people who don't like Chrome and are tech people who like to play with trendy new technology will be happy about both of those, but random people off the street probably won't.
Re:State of web browsers in 2018 by Izkata on Friday December 07, 2018 @01:45PM (#18630320)
Then don't talk about it from a privacy angle; I use containers so I can be logged in to my home and work accounts at the same time.
Re:State of web browsers in 2018 by kiriakasis on Sunday December 09, 2018 @06:24AM (#18640361)
For most uses they are a long-lived incognito session.
Re:State of web browsers in 2018 by dbolgheroni on Thursday December 06, 2018 @12:22PM (#18620031)
As a long Firefox user, I did switch to Chrome/Iridium lately.

When Firefox decided to attack the problem of market share with engineering, 2 things were happening (almost) at the same time[1]: 1) the deprecation of the old add-on engine and 2) the introduction of the new Quantum engine.

For the 1), while I understand there are some reasons in doing so (it was not a stable API as it was always breaking the extensions and security-wise), I think these problems could be managed. On the other hand, there were lots of good add-on depended on this API.

Particularly, even when Firefox was behind technically-speaking, that was the main reason I used it. Firefox replaced the old API without offering all the new interfaces with the new API. So, I lost what made Firefox really unique.

For the 2), I think it was a consequence for the 1). Firefox was finally "better" with Quantum. Of course everyone likes a responsible browser, but I actually didn't see that much difference. And there was another browser which was already really good: Chrome.

Suddenly, there was no real advantage in using Firefox anymore. Someone my say privacy. But in some corners of the Internet, it's already impossible to navigate without some privacy-wise add-on/extension, which usually work on both browsers.

Added to these, if you go deep down, security-wise there are some real technical advantages in running Chrome instead of Firefox in some OSs. For instance:

https://marc.info/?l=openbsd-misc&m=152872551609819&w=2

[1] I'm pretty sure a lot of other things were happening, but I'm in the perspective of the user here.

Re:State of web browsers in 2018 by Izkata on Thursday December 06, 2018 @02:50PM (#18621430)
> Of course everyone likes a responsible browser, but I actually didn't see that much difference.

Same here. The only difference I noticed was startup speed when restoring 200+ tabs; that was indeed far faster in Quantum, but I never noticed any other speed improvements. And it was something I only encountered once every couple of weeks anyway.

Re:State of web browsers in 2018 by johnny22 on Thursday December 06, 2018 @11:24PM (#18625128)
what OS though? It seems like only Windows users really saw speed improvements
Re:State of web browsers in 2018 by Izkata on Friday December 07, 2018 @01:45PM (#18630331)
Ah, I didn't really catch that, but it would make sense. I use Ubuntu.
Re:State of web browsers in 2018 by Wowfunhappy on Thursday December 06, 2018 @01:58PM (#18620948)
I said this up-thread, but Firefox Quantum made me switch back to Firefox, after years away. I noticed a marked speed improvement.
Re:State of web browsers in 2018 by ksec on Thursday December 06, 2018 @04:29PM (#18622441)
For Single Tab instances, Chrome and Safari still wins. For multiple Tabs, Firefox wins hands down.

But the majority of users rarely open more than a few.

Firefox will need to continue iterate, until it is as fast or even faster in every corner.

Re:State of web browsers in 2018 by lousken on Friday December 07, 2018 @02:37PM (#18630817)
exactly what i saw - i regularly use over 200 tabs and in Chrome the performance goes to hell above that number (even on i7 6700k - also managing tabs is PITA), while Firefox just keeps chugging without any problems
Re:State of web browsers in 2018 by TMWNN on Tuesday December 11, 2018 @01:58PM (#18657800)
I use ~1200 tabs. I used to deal with what you and ksec experienced in Chrome by periodically killing all Google Chrome Helper processes, and a few months ago switched to Firefox (less sluggish) from Chrome. Last week I decided to try Chrome again and was pleased to find that (with the same tab set) Chrome 71 is amazingly fast; new tabs open instantly, I can immediately enter a search query or URL, and the browser remains stable over time. So it's back to Chrome for me; it is now only slow when starting for the first time, when it processes the 1200 tabs for a few minutes.

(I do use The Great Discarder, but did so before switching to Firefox, too.)

Re:State of web browsers in 2018 by lousken on Friday December 21, 2018 @12:26PM (#18734786)
I got used to tree style tabs so I wouldn't be able to switch, those extra windows which are necessary in chrome were awful
Re:State of web browsers in 2018 by yogthos on Thursday December 06, 2018 @01:36PM (#18620732)
Has Mozilla considered focusing on the emerging federated ecosystem championed by Mastodon. I really think that federated sites are a way forward for the open web. Federated platforms are inherently decentralized, and they avoid the problem of a single company deciding what's right for all the users. Platforms like Mastodon and PeerTube are already able to interoperate via ActivityPub, and it would be great to see this ecosystem keep growing. I can see an ecosystem of federated platforms that fill the same niches as Twitter, Fb, Reddit, and Instagram. All developed independently, and all able to collaborate with one another.

One big aspect of traditional web is searching, and that's where Google built their empire originally. Why not invert that equation and build search and discoverability into federated platforms. Perhaps extend ActivityPub, or create a sister protocol that focuses on searching. This approach would address the problem of discoverability much better than an external search engine. Perhaps Mozilla could help come up with such a standard.

Re:State of web browsers in 2018 by RcouF1uZ4gsC on Thursday December 06, 2018 @02:09PM (#18621045)
> We will largely be defined in opposition to Google.

Looking at the Financial Report for 2017 https://assets.mozilla.net/annualreport/2017/mozilla-fdn-201...

it seems that the the vast majority of Mozilla revenue is from Royalties ($539M out of $562M). In addition in the report there is a statement to the effect that 93% of Royalties were from search engine deals. We know that Mozilla entered into a search engine deal with Google at the end of 2017.

It looks like that the vast majority of Mozilla's revenue is from Google and will be for the next several years at least. It will be interesting to see Mozilla positioning themselves in opposition to Google when Google provides the vast majority of their revenue.

Re:State of web browsers in 2018 by fchristant on Thursday December 06, 2018 @02:56PM (#18621497)
hi, author of the article checking in.

Thanks for commenting in the open from Mozilla's perspective, even if its just one voice, it's much appreciated.

I agree that Firefox will remain an attraction to the group of people caring about openness, standards, and their privacy. My deepest concern is on how small that group is going to be. Will it settle at the current ~10%, or will it be as low as 5%, which I consider very dangerous grounds to be in.

As for Google's abuse of market power, I strongly believe it has already happened, in plain view. There's no doubt in my mind that dominance in one market has been used to capture another market. We don't have to wait for that "mistake", it has already happened.

These abuses are already under investigation, but I'm afraid it won't change the outcome. They'll pay some fine in a few years, but none of the browsers will be uninstalled.

It won't matter much, but added an update to the top of the article suggesting people to install Firefox.

Re:State of web browsers in 2018 by mercer on Thursday December 06, 2018 @12:49PM (#18620313)
> Eventually, Google will do something that is an abuse of their monopoly power. Either there will eventually be a privacy/creepiness fiasco, or Google will attempt to use Chrome as leverage to squeeze a competitor out of a market.

> When that happens, Mozilla will be well-positioned as an alternative.

I hope you're right, but my main concern is that this could be a war of attrition: Google has such deep pockets that they can simply play nice, all the while testing the limits of what users will accept, until Mozilla taps out. And once that happens, all bets are off.

Re:State of web browsers in 2018 by zamadatix on Thursday December 06, 2018 @10:41AM (#18618917)
I really don't think the general population cares about any of that enough to incite the change you are referring to. People stopped using IE because it was hilariously bad to use compared to Firefox and then Chrome. Until Chrome becomes hilariously worse for an average user to use it'll remain a near monopoly.
Re:State of web browsers in 2018 by Reinmar on Thursday December 06, 2018 @10:42AM (#18618925)
You say that Mozilla will be well-positioned as an alternative to Google. That sounds realistic and I hope it will be able to team up with bigger companies which would like to compete with Google (instead of helping it).

However, that made me think about Brave (https://brave.com/). What are your thoughts about it? It's also privacy oriented, but it's actually built on top of Chromium. What is even more interesting, Brave was founded by Brendan Eich (the co-founder of Mozilla).

Re:State of web browsers in 2018 by gilrain on Thursday December 06, 2018 @11:10AM (#18619218)
Brave is rent-seeking the entire Internet and doesn’t deserve serious mention.
Re:State of web browsers in 2018 by jolmg on Thursday December 06, 2018 @11:27AM (#18619399)
I haven't looked into Brave in years, but the original idea I remember was that the trend of having the web be free for the public and funded by advertising (mostly the single entity, Google) was bad for the general public in terms of privacy. Therefore, it would be better if people financially supported the sites they visited and benefit from, so as to extinguish the need to give so much power to the advertising industry. In order to do that, they were modifying an existing browser with a system that would make a payment to the sites you visited that supported accepting such a payment.

Is this what you're against, or has Brave done something else that deserves being dismissive of them?

Re:State of web browsers in 2018 by curlypaul924 on Thursday December 06, 2018 @01:18PM (#18620566)
Advertising isn't fundamentally bad for privacy, otherwise newspapers and movies would be bad for privacy; it's targeted advertising (which requires keeping a profile for each user) that is fundamentally at odds with privacy.
Re:State of web browsers in 2018 by jolmg on Thursday December 06, 2018 @01:53PM (#18620905)
Well, advertisers are going to do their job as well as they can, defined by the amount of money their methods bring. They can't track in newspapers or movies because there's no feasible way to do so. If you want a business to not do something that brings it more money, you'll have to introduce legal liability that makes that something not worthwhile. That's probably GDPR, in a nutshell.
Re:State of web browsers in 2018 by bad_user on Thursday December 06, 2018 @11:40AM (#18619539)
People are bitching and moaning about Mozilla pulling an extension that works around paywalls from addons.mozilla.org, so do you honestly think that people are willing to "financially support the sites they visited"?

Without hitting a paywall that can't be worked around, hell will freeze over before that happens ;-)

Re:State of web browsers in 2018 by sincerely on Thursday December 06, 2018 @02:08PM (#18621041)
People would be willing to if they had a choice that wasn't "Buy a year's subscription to our newspaper to read the one article you want"
Re:State of web browsers in 2018 by jolmg on Thursday December 06, 2018 @02:14PM (#18621099)
I don't think they would on their own, but Brave's efforts to ease that path still seem commendable.
Re:State of web browsers in 2018 by BrendanEich on Monday December 17, 2018 @03:05PM (#18701703)
If you use "rent-seeking", you need to know what it means. I do not believe that you do know what it means. Economists use "rent" to denote extraction from existing wealth. https://www.investopedia.com/terms/e/economicrent.asp

Brave adds wealth by pricing users back in from the start (via a genesis block of tokens we give to users and referring creators), and by blocking inefficient, dangerous intermediaries (cut out the middlemen, as Marx said) for a much more efficient market.

Those intermediaries are the _grands rentiers_ today, and yet all but Google, Facebook, Criteo, Amazon, and a few others are dying. Ad/tracker-blocking is a user right but it alone cannot explain the walking death of most intermediaries in the Lumascape.

Rather, too many intermediaries arbitrage and abuse data. This induces not only the ongoing rise of ad/tracker blocking by users -- it cuts off residual revenue to publishers (who make <40% off of programmatic ads in practice, sometimes <20%), who also want fewer hands in the till. Arbitrage always goes away (till next opportunity). The data misuse causes ongoing rifts and scandals. GDPR and laws like it are icing on the cake.

If you are party to the existing Lumascape of ad-tech vendors, your post is projection and I suggest looking honestly in a mirror to see "rent-seeking". If you're calling Brave rent-seeking out of some irrational animus, take a closer look at the product itself, and let's reason together.

Re:State of web browsers in 2018 by BostonEnginerd on Thursday December 06, 2018 @11:15AM (#18619269)
I disagree. They have presented an alternative to the current system of surveillance capitalism without forcing anyone into their platform.

I don’t really love the browser and wish the Brave protocol was available for Firefox, but hopefully we can get there sometime in the future.

Re:State of web browsers in 2018 by jolmg on Thursday December 06, 2018 @12:02PM (#18619768)
I really don't know what's better. While it's bad that having a free web has lead to multiple entities doing everything they can to track as much as they can, it's also a great benefit to society to have free access to so much knowledge.

In the end though, I don't think we'll see a shift to people paying for their content. Societal problems arising from lack of privacy is one of those high-impact-low-probability-or-slow-to-come risks that the public is so bad at handling for their greater aggregate benefit.

To really see a change, if Brave has done their part, what'd be missing would be a general public education program that would better inform the public of what the risks are and what can be done about it. Something like Smokey Bear.

Re:State of web browsers in 2018 by bunderbunder on Thursday December 06, 2018 @12:25PM (#18620069)
> While it's bad that having a free web has lead to multiple entities doing everything they can to track as much as they can, it's also a great benefit to society to have free access to so much knowledge.

This feels like a false dilemma to me. Many, if not most, of the corners of the web that are devoted to disseminating knowledge are funded by means that don't involve tracking ads.

It's the entertainment corner of the web - social media, yes, but I include listicle-oriented versions of journalism here, too - that seems to be the primary engine of all this surveillance capitalism.

It's no coincidence that they also have a tendency to actively exploit the parts of human psychology that make us susceptible to addiction. Which means that, while it's true that they don't charge an up-front fee, their products do still come at a price.

Re:State of web browsers in 2018 by jolmg on Thursday December 06, 2018 @01:38PM (#18620760)
I think you're right. Wikipedia (and other WikiMedia projects), MDN, StackExchange sites, wiki sites like wiki.archlinux.org, wiki.osdev.org, wiki.c2.com, public forums like lambda-the-ultimate.org or news.ycombinator.com would probably still be free. I can't think of any place that I've learned significantly from that provides their content for advertising money. They all seem to be up primarily for altruistic reasons.

EDIT: Thought of one: YouTube. I wonder, though, if the content providers I've learned most from in YouTube would have chosen not to provide if there weren't advertising options. Maybe they activate advertising because it's easy and would have uploaded regardless?

EDIT 2: The real question, though, would be if someone would be willing to make a YouTube alternative and eat the cost of development and maintenance of the site and hosting of those videos for altruistic reasons... It's a lot more costly than hosting a site that serves lightweight text.

Re:State of web browsers in 2018 by bunderbunder on Thursday December 06, 2018 @02:27PM (#18621213)
Stack Exchange advertises, but, to the best of my knowledge, they don't engage in any tracking-based advertising, so it doesn't really bother me.

I'll even click on those ads if I'm interested (crazy, right?), which is something I scrupulously avoid doing for ads that I suspect are fueled by tracking.

Re:State of web browsers in 2018 by jolmg on Thursday December 06, 2018 @02:45PM (#18621367)
> Stack Exchange advertises

Yeah, but I get the feeling that it didn't start with the purpose of advertising. Haven't really looked into its history to know for sure, though.

> I'm not really opposed to topical advertising. And I'm not even particularly opposed to targeting. Showing ads for Databricks alongside a Stack Overflow question about Apache Spark is fine by me (just so long as it isn't a popup or an auto-playing video). That's no creepier than advertising car stuff in a car magazine.

I wouldn't be opposed to tracking if that's all it ever amounted to, either. In fact, your example doesn't seem to involve tracking. Deciding what to show based on the content of the page doesn't imply using any knowledge of you from other sources.

EDIT: Anyway, what's worrying of tracking is that it makes the buying and selling of personal information a viable and profitable business. It's not worrying if you think that such a business can only be used for showing ads you're interested in everywhere you go. In fact, that's a benefit to anybody, and that's what makes it a good public justification for it by the companies that do this tracking.

However, that's not the only way people can apply your personal information. For example, businesses can also use it to personalize the prices for the products and services they offer based on indicators they bought of your purchasing power. Insurance companies can use a lot more than indicators of your purchasing power to know how to quote you, probably getting their hands on knowledge that by law they probably shouldn't be able to get their hands on to avoid unfair discrimination. There's regulations of what businesses can ask of employee candidates to avoid unfair discrimination, but they won't need to ask anymore if they can just buy the info online.

Re:State of web browsers in 2018 by CalRobert on Thursday December 06, 2018 @11:32AM (#18619465)
So is cURL for that matter.
Re:State of web browsers in 2018 by joombaga on Thursday December 06, 2018 @12:08PM (#18619831)
What do you mean?
Re:State of web browsers in 2018 by CalRobert on Thursday December 06, 2018 @01:15PM (#18620543)
My understanding was that op felt by blocking trackers, ads, etc. Brave was effectively a free rider on the internet. This has always seemed weird to me since I shouldn't be obliged to run code that gets downloaded. When I use cURL (or block js, etc.) I can download just the content (usually) without all the dependencies. But I don't think this makes me a free rider.
Re:State of web browsers in 2018 by xte on Thursday December 06, 2018 @11:42AM (#18619570)
Only a sidenote: did you think any human being can have properly reviewed webkit source code before using it?

If not, how can be anything based on webkit considered to be safe, privacy oriented etc?

Re:State of web browsers in 2018 by jolmg on Thursday December 06, 2018 @12:08PM (#18619833)
Not just webkit's source code. What human being can have properly reviewed the source code of Chrome or Firefox or anything else both open and closed source before using it? How can any program any one of us is using right now be considered safe if we haven't properly reviewed it?
Re:State of web browsers in 2018 by xte on Thursday December 06, 2018 @12:13PM (#18619898)
That's true, but at least Firefox born as FOSS so there is a community that potentially see the code growing by the time so while they may have lost something as individuals as a community there is a certain knowledge of the code. Webkit born open (KHtml, Kde's Konqueror html engine) but subsequent evolution happen inside few big companies and sources are release "en mass" so there is essentially "no community" that having at least seen the code grow a commit at a time so to have a sort of "big picture" knowledge...
Re:State of web browsers in 2018 by LamaOfRuin on Thursday December 06, 2018 @02:30PM (#18621241)
I'm pretty sure that as far as lineage goes, Chrome was actually born more FOSS (KHtml) than Firefox was (Netscape). Firefox is certainly more FOSS in spirit now than Chrome has ever been, but Mozilla is certainly not immune from the kinds of shenanigans possible for any open source project that is entirely controlled by a single large organization.
Re:State of web browsers in 2018 by jolmg on Thursday December 06, 2018 @03:54PM (#18622113)
Chrome's closed source though. You probably mean Chromium. Still, I'm not sure how much in the spirit of FOSS it is to have an open source version to drive development while marketing the closed source version which might be filled with spyware for all we know.
Re:State of web browsers in 2018 by dtech on Thursday December 06, 2018 @12:05PM (#18619792)
This is a pretty bad argument, as exactly the same can be said for the Servo/Firefox codebase
Re:State of web browsers in 2018 by xte on Thursday December 06, 2018 @12:18PM (#18619979)
See above: it's true, but at least FOSS born and evolved projects may be known by "early" devs that see project evolution during it's time, on contrary when a company release million SLOC no one really know anything...

Anyway, in general my line is that all "modern browsers" must die, because browsers should be browsers, not "platforms" and websites should be hypertext, not application... I really dream a modern Plan9 even if I know nobody with enough competence, time and money to develop something like that exists today. I only can hope that a scandal and a disaster at a time we start to be tired, damaged and threatened enough that we support something like GNU/FSF to a level that produce free software and open hardware can be done by a community for the community itself... Well... A bit utopic...

Re:State of web browsers in 2018 by dtech on Saturday December 08, 2018 @05:44PM (#18637976)
> See above: it's true, but at least FOSS born and evolved projects may be known by "early" devs that see project evolution during it's time, on contrary when a company release million SLOC no one really know anything...

Do you know the history of Blink? It was forked from Webkit, which was forked from KDE's KHTML and remained open source all the way. So you argument also explains to Blink.

Re:State of web browsers in 2018 by thaumaturgy on Thursday December 06, 2018 @01:08PM (#18620488)
Firefox's current problems go back to around 2011, and you can see this in the trend graphs.

At that time, there was still a hot three-way race between Chrome, Firefox, and IE. But Mozilla made a misstep: they decided that, to compete with Chrome, they would adopt a new "Rapid Release" model. This resulted in a massively pissed-off base of former supporters and articles like "Rapid-release Firefox meets corporate backlash" [1] and "Understanding the Corporate Impact" [2]. There were multiple discussions with titles like, "Mozilla Executive: We're Not Interested In Enterprise Level Users", and it was still going on a year later with, "Everybody Hates Firefox Updates" [3].

People have been conditioned now to accept frequent updates, and -- years later -- the browser vendors have mostly stopped reskinning their interface every other release. But that wasn't the situation at the time, and so Firefox gave up their one competitive advantage over Chrome, and leveled the playing field in Chrome's favor.

Mozilla could have instead embraced that big, loyal enterprise base, and found a sane middle road for updates that allowed them to keep a healthy release schedule for DOM, JS, and CSS support. But, they didn't.

So all of that good will that Mozilla had fostered over the years just evaporated, and Mozilla never looked back.

(It didn't help that, just after alienating their enterprise user base, Mozilla also kicked off some drama with a developer [5].)

This falls into that category of mistakes-that-kill-your-business-years-later, alongside other case studies like Sears and RadioShack.

[1]: https://www.cnet.com/news/rapid-release-firefox-meets-corpor...

[2]: https://mike.kaply.com/2011/06/23/understanding-the-corporat...

[3]: https://news.ycombinator.com/item?id=2692205

[4]: https://news.ycombinator.com/item?id=4209384

[5]: https://news.ycombinator.com/item?id=2741660

Re:State of web browsers in 2018 by rdsubhas on Thursday December 06, 2018 @05:20PM (#18622944)
> Eventually, Google will do something that is an abuse of their monopoly power. Either there will eventually be a privacy/creepiness fiasco, or Google will attempt to use Chrome as leverage to squeeze a competitor out of a market.

They did recently. They force signed and associated every user to the Chrome identity, thereby linking everything users do in the web to their Google ID. Nobody seems to have bothered.

Re:State of web browsers in 2018 by swebs on Thursday December 06, 2018 @02:45PM (#18621369)
>People who use Firefox in the future will increasingly be people who do so consciously, presumably because they view Mozilla as helping them protect their privacy. Chrome is and will continue to be the default.

Honestly, the only reason I use Firefox is because it supports vertical tabs and Chrome doesn't. Maybe you should start advertising features that are more immediately visible than privacy.

Re:State of web browsers in 2018 by sebazzz on Thursday December 06, 2018 @10:59AM (#18619098)
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 by jcranmer on Thursday December 06, 2018 @11:58AM (#18619732)
I can't speak for Servo, but Mozilla pretty firmly gave up on trying to have a good embedding story for Gecko and SpiderMonkey (in the name of being able to rapidly iterate on APIs, which never ended up settling down) somewhere around 2009. I contend that one of Mozilla's big mistakes was to give up on embedding.
Re:State of web browsers in 2018 by kitsunesoba on Thursday December 06, 2018 @12:18PM (#18619969)
RIP Camino, which served as many Mac users’ favored browser for years even after it stopped getting updates.
Re:State of web browsers in 2018 by latexr on Thursday December 06, 2018 @05:55PM (#18623284)
Add AppleScript support to Firefox and I’ll switch today.

I don’t like Chrome’s dominance either, but what do you want me to do if your browser does not support a feature I use everyday, multiple times a day (and that was there but was removed, back in version 3)? You’re giving me a browser that is useless for my needs, so I can’t use it.

You bet I’m thinking of leaving Chrome behind (and will likely do so once I make a clean install to Mojave, that should happen soon) but my only real alternative is Safari. I’d rather that alternative be Firefox, but it isn’t. I rely on browser AppleScript control so heavily, I’d sooner stop using a web browser than switch to Firefox.

And if you think I’m alone in that, there’s a chunk of the macOS automators community you’re not visiting. We build our tools with support for major browsers (and some minor) but never Firefox, because it can’t do it. We don’t even mention it anymore. If someone asks why our tools don’t work on Firefox, we answer that it’s because you don’t support the necessary feature. The number of people asking is lower every year.

Every time there’s a Firefox thread on HN, you see the same complaints from macOS users: poor performance, missing features (I’ve seen lackluster Keychain support also mentioned).

Give me a browser I can use, and I will.

P.S.: Even if I could code enough to add what I need, it’s not even clear to me from your bug tracker if you’d take the addition. Last I looked, I couldn’t even decipher if AppleScript support is something desirable or not.

Re:State of web browsers in 2018 by tapoxi on Thursday December 06, 2018 @11:11AM (#18619226)
What would be the downside of "pulling an Edge" and just making Firefox a Chrome fork with some Mozilla specific features? There's an alternative to Google, Mozilla saves a ton of money/time on duplicated effort, and developers only have to worry about testing against Blink/Webkit.

Servo/Quantum is cool, but it seems to be too late for that. I'm worried that Mozilla is simply in denial about this and when reality sets in course correction will be significantly more painful.

Re:State of web browsers in 2018 by danShumway on Thursday December 06, 2018 @11:20AM (#18619331)
It would give the Chromium dev team a massive amount of leverage in directing web standards.

This matters because, on-the-whole, Mozilla's dev teams tend to be much better at writing standards than Google's are; partially because many of the standards Chromium focuses on are prioritized and developed with the intention of being helpful to Google's long-term strategies. There have been multiple instances (html imports spring to mind) where bad decisions were averted purely because Mozilla had the guts to say, "we're not putting that in Firefox, come back when you have a better proposal."

Yes, Chromium is Open Source, but Open Source isn't magic. It's still very much a Google product, designed to increase Google's overall influence over the direction of the web. Unless Mozilla's plan is to literally fork Blink, then having a primarily for-profit mono-culture in charge of what features get fast-tracked and prioritized for browsers is still incredibly harmful.

Re:State of web browsers in 2018 by tapoxi on Thursday December 06, 2018 @11:43AM (#18619579)
There are enough large, interested parties (Samsung, Microsoft, Mozilla) out there that they could literally fork Blink if organizational issues arise and gain a sizable install base.
Re:State of web browsers in 2018 by danShumway on Thursday December 06, 2018 @12:00PM (#18619749)
Sure, but how big would those issues need to be?

Would it be worthwhile to make a fork over HTML imports? Suppose that in a mono-engine world Google decides to build AMP directly into the browser rather than on top of Javascript -- would that be a big enough issue to make a fork? I was (like many people) fairly disappointed about Web DRM, but I was happy that Firefox was at least planning to put some additional sandboxing above what Chromium was doing. Would they have forked a codebase just to introduce that extra sandboxing?

You're right that Open Source does allow us to reverse course and fork Blink later if something terrible happens. Remember though, the moment that someone like Mozilla or Microsoft makes a fork, at that point they're back to the same situation that they're in right now -- even worse, because they're stuck using a codebase that wasn't architectured specifically to meet their goals. That provides a big incentive to wait as long as possible before deciding, "heck it, we'll build our own engine."

What I would suggest is that there are at this moment already at least minor organizational issues within Chromium, and there are currently benefits to having multiple browser engines. We could give up those benefits and get them back later if stuff got really bad. But it would mean waiting until things got really bad; and ignoring all of the tiny, daily decisions before that point that go in to setting the direction of the web.

Remember that the web isn't supposed to break backwards compatibility. If you don't get things right the first time, there isn't a second chance to change them.

Re:State of web browsers in 2018 by asituop on Thursday December 06, 2018 @11:55AM (#18619707)
If Mozilla can't reach enough user now, why would they do with a fork of Blink ? It's not a web engine problem, it's just that Google is too powerful and Chrome is everywhere, so they decide.

And actually it is better for innovation not to use to Blink. WebRender is potentially much more performant than any other engine and it would never had existed if Mozilla were just aligning with Blink

Re:State of web browsers in 2018 by mrweasel on Thursday December 06, 2018 @12:21PM (#18620014)
Exactly, people seems to only remember that Mozilla was a little behind Chrome some years back. That by no means the case anymore. Unless you're somehow embedded in the Google ecosystem, there's no reason to prefer Chrome over Firefox.

It's not like the other Blink or Chrome based browsers are doing great, sure Brave and Vivaldi is getting some press, but they have even less users than Firefox.

Sadly Firefox isn't peoples mind anymore when they think browser. It's IE all over again, but with Chrome, Only Chrome is moving forward. I don't know if there's anything Firefox can do, other than marketing. It's currently the best browser out there, but that was the case when IE6 dominated the web as well.

Firefox doesn't need to dominate, but hitting some like 20% market share would be fantastic.

Re:State of web browsers in 2018 by Wowfunhappy on Thursday December 06, 2018 @02:17PM (#18621123)
> Exactly, people seems to only remember that Mozilla was a little behind Chrome some years back. That by no means the case anymore.

This isn't directly relevant in the larger context of this thread, but Firefox's sharp drop—even after the introduction of Quantum, which I've found to be a big improvement—is what makes their situation much more scary to me.

Re:State of web browsers in 2018 by tapoxi on Thursday December 06, 2018 @01:15PM (#18620545)
They won't, but it'll save money and engineering effort spent on Quantum/Servo.
Re:State of web browsers in 2018 by SamWhited on Thursday December 06, 2018 @11:17AM (#18619298)
But there's now no alternative to Blink, and Google can do the IE/Netscape thing of just ignoring the standards process and making up new web technologies that benefit them (and everyone else has to adopt them). The browser UI is the least important thing to compete on.
Re:State of web browsers in 2018 by mr_toad on Thursday December 06, 2018 @06:57PM (#18623782)
> Either there will eventually be a privacy/creepiness fiasco, or Google will attempt to use Chrome as leverage to squeeze a competitor out of a market.

Perhaps if it ever comes to that, people will look to an alternative means (than the web) of accessing documents and code.