News for hackers. Stuff that matters.
Re:New in Chrome 73 by hestefisk on Wednesday March 13, 2019 @05:49AM (#19377153)
We need to drop Chrome and start using Firefox. I just switched to FF Nightly and it is really fast with GPU acceleration. Please download today!
Re:New in Chrome 73 by rosege on Wednesday March 13, 2019 @06:00AM (#19377216)
I think the best browser definitely fluctuates over time. I started out with Mozilla c1995. Then have shifted through most of them at various points in time when I've become unhappy with my current choice. I went back to Firefox when they released their Quantum version and have been really happy with it. Haven't used Chrome much since then. But I'm always open to other browsers should something change in the future.
Re:New in Chrome 73 by DCoder on Wednesday March 13, 2019 @07:18AM (#19377607)
Was this motivated by something in the release notes, or are you just taking the opportunity to bang the Firefox drum? Should we expect this comment in every Chrome-related thread?
Re:New in Chrome 73 by Kurtz79 on Wednesday March 13, 2019 @06:02AM (#19377226)
We don't "need" to do anything.

It's nice to have choiches.

Re:New in Chrome 73 by samueloph on Wednesday March 13, 2019 @06:27AM (#19377363)
Yeah, and one of these "choices" implies not having any more choice at all
Re:New in Chrome 73 by Kurtz79 on Wednesday March 13, 2019 @07:48AM (#19377735)
You are free to make your own choiche, not to impose it on me.
Re:New in Chrome 73 by samueloph on Wednesday March 13, 2019 @08:11AM (#19377842)
Yes, you get the point, now you just need to enforce that because this is actually being forced by a ton of websites requiring chrome to work.
Re:New in Chrome 73 by rum3 on Wednesday March 13, 2019 @06:06AM (#19377243)
But the internet needs it. A one-browser monopoly will not be good for anyone.
Re:New in Chrome 73 by snaky on Wednesday March 13, 2019 @07:34AM (#19377675)
Actually it is good for an average user who doesn't care about privacy.
Re:New in Chrome 73 by dao- on Wednesday March 13, 2019 @08:36AM (#19377978)
This doesn't even make sense. Not caring about something doesn't mean it won't be an issue for you and the people around you.
Re:New in Chrome 73 by snaky on Wednesday March 13, 2019 @07:33AM (#19377672)
We need to drop Chrome and start using Firefox exactly because of that.
Re:New in Chrome 73 by saintPirelli on Wednesday March 13, 2019 @06:24AM (#19377348)
You also have the choice to buy clothes stitched together by children in Southeast-Asia under horrible conditions, but we all know that a responsible consumer decision looks different.
Re:New in Chrome 73 by madeofpalk on Wednesday March 13, 2019 @06:32AM (#19377399)
Let's not pretend that using a web browser and supporting slave labour is even remotely comparable.
Re:New in Chrome 73 by saintPirelli on Wednesday March 13, 2019 @07:34AM (#19377678)
What I'm saying is, that "we have a choice" is a void argument if you have just been presented with a solid case that one choice is clearly better than the other.
Re:New in Chrome 73 by kome on Wednesday March 13, 2019 @06:09AM (#19377255)
no, we need it; or we will go back to a fancy version of Internet Explorer 6 (that is, chrome browser): proprietary technology implementation, by a top player, against any standard... and spying on users (but that's new, I don't think IE 6 was that vicious).

Web monoculture make the web worse for everybody.

Re:New in Chrome 73 by nolok on Wednesday March 13, 2019 @06:25AM (#19377357)
It's funny, I see this comparison a lot and the people using it don't see how it misses the mark: the reason (the majority of tech) people hated SO MUCH on IE6 was not because it was proprietary, but because it was static and didn't bring get any advance, thus blocking the web's progress. Chrome doesn't have that issue, at worst you can claim it gives too much power to Google on decision about where the web goes, but not that it keeps it from progressing.

It was also not respecting the standards but only after a while (at release it was at the forefront of it), and that is also not a problem that Chrome can relate to.

I say that as someone who uses Chrome, enjoy it, but would also prefer if we didn't go back to a single engine being supported on the web (and I switched back to firefox on mobile, because of chrome lacks of support for ad blocking there).

By confusing what the fight is about and trying to make it about what it's not, I fear you make some people like me ignore it.

Re:New in Chrome 73 by fauigerzigerk on Wednesday March 13, 2019 @07:21AM (#19377623)
>It's funny, I see this comparison a lot and the people using it don't see how it misses the mark ...

You seem to be missing the link between monopoly and stagnation though. IE wasn't always stagnant. It brought us XMLHTTPRequest for instance.

I think the debate has to be about whether or not Chromium being open source changes the equation.

Re:New in Chrome 73 by nolok on Wednesday March 13, 2019 @07:28AM (#19377656)
IE6 era's Microsoft had an interest in the web stagnating, while Google doesn't. If anything, they used their position to push forward new things that others wanted to slow down.
Re:New in Chrome 73 by fauigerzigerk on Wednesday March 13, 2019 @08:23AM (#19377905)
It appears to me that Google is pushing forward some things while slowing down others. Obviously, Google will never be at the forefront of limiting what advertisers can do.

My biggest worry with a Chrome quasi monopoly would be the erosion of browser making competence and financial resources outside of Google.

So whenever Google's vested interests clash with what users want, there would be no one left to step up. Chromium would be open source, but only Google employees would know the source well enough to do anything with it.

It's a worry. I'm not saying it's the same as with a closed source IE back then.

Re:New in Chrome 73 by sametmax on Wednesday March 13, 2019 @06:36AM (#19377423)
Progression != improvement.

When ad blockers won't work, when you get DRM everywhere and trackers will be embedded in the browser, the tech will have progressed. Yet it will not be the progress you want to live.

It's like if suddenly you had only one car maker and say "it will be easier to design infrastructure for it". Yes, it will be. But it also mean you won't get innovation for you, only for the car maker.

For google that would mean pushing techs serving the ad and data collection business of course. But also in general, that would mean building for big companies. Adopting standards that are mostly beneficial to people that have the money to buy patents, setup many CDN, have high end engineers, invest in specialized hardware, etc.

Re:New in Chrome 73 by nolok on Wednesday March 13, 2019 @07:30AM (#19377661)
None of what you say corresponds to what I said.

"Chrome being a monopoly is bad because X" and I say there are lots of issue with only Chrome remaining but not X, it doesn't apply to Chrome. You answer by saying "but there is Y, and W, and Z, and ..." which is basically my point: no need to focus on what is not the issue.

Re:New in Chrome 73 by mjw1007 on Wednesday March 13, 2019 @07:11AM (#19377583)
IE6 wasn't at the forefront of standards compliance when it was released.

Mozilla (then at 0.9.x) and Internet Explorer 5 for Mac were both significantly better.

Re:New in Chrome 73 by close04 on Wednesday March 13, 2019 @06:28AM (#19377372)
Chrome is just as bad but for different reasons. And perhaps even more dangerous (like slowly eroding privacy, or shaping the browser around Google’s revenue generating services). I think the analogy stands and the damage is similar in magnitude.
[dead]
Re:New in Chrome 73 by close04 on Wednesday March 13, 2019 @08:04AM (#19377811)
Was “for different reasons” too unclear? It’s right at the beginning of the comment. Different reasons but the impact is still dangerous.

For example IE6 was not reporting my location to MS despite me turning the option off. Just because some people are ok with that doesn’t make it less of a problem. It just makes it a different (bad) one.

And in the passive aggressiveness [0] of your comment you didn’t even think that there are far better reasons why IE6 sucked. If feels random and based less on long term use experience.

You write as if you’d be ok with Chrome stabbing you in the eye as long as it’s not a CSS hack, the single reference issue all browsers are benchmarked against.

[0] https://news.ycombinator.com/newsguidelines.html

Re:New in Chrome 73 by kowdermeister on Wednesday March 13, 2019 @08:37AM (#19377984)
I've read it and I think it's way overblown. All I care about is solid support for standards and Chrome shines it that.

I picked them because I could test if you actually experienced it. Chrome at the moment is the best we have but it does come with strings attached. It has different problems indeed, surprise surprise, however I don't think that's that a big issue at all.

Re:New in Chrome 73 by close04 on Wednesday March 13, 2019 @09:50AM (#19378554)
> All I care about [...]

You should have started with that instead of the jab. Not only would it have been clear that it’s a personal opinion not a matter of fact (Chrome is better for me) but it would have also saved you the time of coming back later with the real single biggest issue of IE: standards.

The issues Chrome pose for most people right now are real. You don’t care about them for your personal reasons but disqualifying them because they’re not yours is very dismissive. You never know when your interests change.

Re:New in Chrome 73 by DCoder on Wednesday March 13, 2019 @11:59AM (#19379962)
> All I care about is solid support for standards and Chrome shines it that.

Except for cases when it doesn't feel like supporting the standard in question, or it claims their support is sufficient. A recent example could be support for <input autocomplete="..."> [0].

[0]: https://www.reddit.com/r/programming/comments/ar1qj1//egl52w...

Re:New in Chrome 73 by kome on Wednesday March 13, 2019 @08:25AM (#19377917)
I think you are wrong, or at least, I don't share your impression at all...

I was there when IE 6 was a thing, and no, nobody was complaining that IE was too static. That wasn't the main reason at all. One of the main problems is that it was too dynamic, but in a proprietary and unsafe way (ActiveX).

Read, for example, this article from 2002, when "Phoenix" (aka Firefox) was launched: https://www.geek.com/news/mozilla-launches-new-faster-browse...

IE was pushed down the throat of everybody, and the main consumer complaints was "it's bloated".

For developers instead, the craze of the day was to pass the Acid test: we are talking about CSS implementation. We are talking about open standards.

Open standards where the main concerns for developers: http://davidnaylor.org/blog/2005/04/web-standards-acid2-test...

Acid 2 and Acid 3 where a the main thing during the browsers wars (https://en.wikipedia.org/wiki/Browser_wars). And they were ALL about standards.

Re:New in Chrome 73 by afiori on Wednesday March 13, 2019 @06:27AM (#19377362)
It is fair to point out that the negative effect of a google monopoly would be quite different from what happened with IE6
Re:New in Chrome 73 by buran77 on Wednesday March 13, 2019 @03:36PM (#19382759)
The problems IE6 had are vastly different from the problems Chrome presents. But I would argue the Chrome's are potentially worse. IE6 was a big problem mostly for developers who were perhaps better equipped to deal with them. Chrome not only has the chance to become the "singl;e browser" (if it's not already there) and direct the web wherever but it also poses problems directly to the users who are most definitely not equipped to handle them.

I see this as a much bigger issue than IE ever had. It's not technical so a simple patch in your web app won't fix it.

Re:New in Chrome 73 by pps on Wednesday March 13, 2019 @10:48AM (#19379156)
I would love to do that, I'm testing new releases, but every time I try, my machine wants to explode https://www.reddit.com/r/firefox/comments/7g6k9n/firefox_qua... , https://www.reddit.com/r/firefox/comments/asdkxf/firefox_on_... , etc...
Re:New in Chrome 73 by fetbaffe on Wednesday March 13, 2019 @06:01AM (#19377219)
My main problem with Firefox is that it eats my batteries, otherwise I would have used it as my main browser.
Re:New in Chrome 73 by anibalin on Wednesday March 13, 2019 @06:13AM (#19377277)
Same here. Cannt use it on my mba 2012. It just to heavy on resources. Chrome handles it without more loosely.
Re:New in Chrome 73 by fetbaffe on Wednesday March 13, 2019 @06:29AM (#19377383)
If you want to get away from Chrome my tip is to use Opera. Same engine underneath & can handle same extensions (with a proper extension installed) but without Google.

Opera also has a battery saving feature.

Re:New in Chrome 73 by dao- on Wednesday March 13, 2019 @08:39AM (#19377996)
Opera is also closed source and has been bought by some Chinese consortium, so that may not be the best option if you want to get away from Google for privacy reasons.
Re:New in Chrome 73 by fetbaffe on Wednesday March 13, 2019 @09:13AM (#19378236)
Correct. I just think that Google is a bigger problem than this Chinese consortium. If I practically could I would avoid both.

Tried running Edge for a while, which is gentle on battery, however Edge is just lacking.

Re:New in Chrome 73 by dao- on Wednesday March 13, 2019 @09:29AM (#19378375)
Using Opera only superficially sidesteps the big Google problem, as you still contribute to the Chromium monoculture that reinforces Chrome's dominance and benefits Google.
Re:New in Chrome 73 by fetbaffe on Wednesday March 13, 2019 @10:08AM (#19378732)
Yep, sad state of affairs. Sad day when Microsoft succumbed to Chromium monoculture.

However when I develop I always develop for Firefox first, but the Firefox developer tools are starting to age as well.

Re:New in Chrome 73 by dao- on Wednesday March 13, 2019 @10:40AM (#19379081)
At least the performance issue of Firefox on Mac is being worked on and should hopefully be resolved soon: https://bugzilla.mozilla.org/show_bug.cgi?id=1429522
Re:New in Chrome 73 by fetbaffe on Wednesday March 13, 2019 @10:53AM (#19379214)
Even though PWA:s are good in theory, will it only increase Google's grip on the web?

Has the web standards become so complex that it is inevitable that we will have a Chromium monoculture?

Re:New in Chrome 73 by pps on Wednesday March 13, 2019 @11:05AM (#19379347)
> should hopefully be resolved soon

I want to believe, but I heard that multiple times and still can't even open simplest html websites without hearing the pain of my machine.

Re:New in Chrome 73 by dao- on Wednesday March 13, 2019 @12:51PM (#19380627)
It had been blocked by webrender if I remember correctly, now the work on fixing this issue has actually started. Markus Stange is a capable engineer as well so there's hope.
Re:New in Chrome 73 by ddon on Wednesday March 13, 2019 @05:59AM (#19377206)
Firefox team needs to wake up and add support for PWA.
Re:New in Chrome 73 by Jonnax on Wednesday March 13, 2019 @06:11AM (#19377265)
I thought PWA was just service workers and implementing routing on the web app level.

What's missing in Firefox?

Re:New in Chrome 73 by tehbeard on Wednesday March 13, 2019 @06:24AM (#19377347)
"Integration" into the underlying OS (showing up as a desktop icon / homescreen shortcut)
Re:New in Chrome 73 by nashashmi on Wednesday March 13, 2019 @07:49AM (#19377737)
Drag and drop url to desktop. It does the same thing. Firefox should get a head start and create a pwa store.
Re:New in Chrome 73 by matmg on Wednesday March 13, 2019 @06:20AM (#19377319)
Please, respect other people's choices.
Re:New in Chrome 73 by chii on Wednesday March 13, 2019 @06:21AM (#19377330)
Is it still a choice if the user didn't think about choosing?
Re:New in Chrome 73 by stonekyx on Wednesday March 13, 2019 @06:11AM (#19377262)
Not possible for me to start using Firefox until it starts to support WebSocket frame inspection..
Re:New in Chrome 73 by fps_doug on Wednesday March 13, 2019 @06:27AM (#19377364)
You know, it's not like you couldn't use one browser for work and the other one for everything else. I certainly don't need to inspect WebSocket frames while booking a flight, reading the news, chatting with family on facebook, or shitposting on HN.
Re:New in Chrome 73 by pjmlp on Wednesday March 13, 2019 @07:40AM (#19377705)
Having Firefox and Chrome installed is still less than the bunch of Electron based apps that are so beloved on HN.