News for hackers. Stuff that matters.
Re:Google proposes changes to Chromium which would disable u... by drawkbox on Tuesday January 22, 2019 @06:32PM (#18973941)
> I really just don't understand the obsession with Chrome, especially in hacker communities.

Chrome used to be very lightweight, fast and basically unseated IE as the top browser. It got that love because at the time Firefox was bloated and IE had a stranglehold. Chrome was also safer with a process per tab. Chrome made web browsing/dev pleasant like Firefox/Firebug did and it really took off being based on Webkit like Safari which also worked well on mobile. Chrome (and Safari) or Webkit pushed HTML5/Canvas/WebGL/SVG into real world use which changed the landscape of browsers.

Nowadays Chrome is bloated like Firefox was, has a stranglehold like IE did, is now pushing its own market standards and breaking existing open/market standards and generally being a forceful, non respecting to standards, web browser. It sure is unfortunate and another sign that bizdev/marketing/executives rule over engineers at Google now.

Re:Google proposes changes to Chromium which would disable u... by cat199 on Tuesday January 22, 2019 @11:57PM (#18975777)
This is bad history.

Firefox was top dog when chrome came out - it had unseated IE already for many users fed up with XP-era crapware.

Firefox was not simply 'bloated', but designed for classic HTML rendering at a time when javascript (aka 'web 2.0 ajax') dev was taking off and memory was not as abundant as it is now - though slow, it was more that the core architecture was out of date than it was 'bloated'. Indeed firefox was already a stripped down version of 'the mozilla suite' (see also seamonkey, thunderbird, etc - all of which predate chrome).

Chrome then came in, borrowed another project's browser engine, and decided to say 'screw memory, just fork processes' and avoided the whole multithreaded thing all together, oh yes, and open blank tabs faster with a little animation for perceptions sake.

This facilitated html5/javascript bloat, and by extension kept it in the lead as the only browser that could handle it.

of course I'm biased here (as is parent) - but chrome unseating firefox which unseated IE is born out by the facts.

Re:Google proposes changes to Chromium which would disable u... by drawkbox on Saturday January 26, 2019 @08:25AM (#19006176)
> Firefox was top dog when chrome came out - it had unseated IE already for many users fed up with XP-era crapware.

Maybe in mindshare for devs but Chrome officially unseated IE browser saturation in 2012. Firefox didn't pass IE until 2015 [1].

Firefox was amazing on its resurgence in mid-2000s but did get into memory/bloat stages that opened it up for minimal/performant Chrome that was also more secure at the time primarily due to the process per tab. This possibly did lead to more js bloat later, initially it was lightning fast and also had a debug console and was based on Webkit which was better than Firefox rendering.

Firefox definitely saw Web 2.0 come in from 2006 on and was revolutionary in web development/debugging with Firebug and eventually that was part of the browser and is now industry standard to have a console/debugger on the browser.

Most developers were using Firefox by 2005-2006 and then Chrome a couple/few years later and it has been top for almost a decade now.

[1] https://en.wikipedia.org/wiki/Usage_share_of_web_browsers#/m...

Re:Google proposes changes to Chromium which would disable u... by aylmao on Tuesday January 22, 2019 @10:59PM (#18975571)
> Chrome made web browsing/dev pleasant like Firefox/Firebug did and it really took off being based on Webkit like Safari which also worked well on mobile.

This is the big one for me. When I'm not developing I actually prefer to use Safari-- I like it's interface better and it feels more at home in macOS. It's "good enough" too.

What I'm really a user of is the Chrome Dev Tools. Firefox's are looking quite solid lately but I just haven't switched over.

Re:Google proposes changes to Chromium which would disable u... by MarsAscendant on Wednesday January 23, 2019 @12:48AM (#18975956)
What I'd love is to have Firefox dev tools functionality in Chrome.

Firefox highlights the edge lines of the selected element automatically, and in all directions (if I recall correctly). I have to use an extension – VisBug – to achieve that in Chrome.

There's also the fonts window, which lets you in on what fonts are used on the page, and lets you modify the selected element's font settings – size, weight, slant/italic etc.. I pay a lot of attention to typography, so that part is important to me.

Re:Google proposes changes to Chromium which would disable u... by bad_user on Wednesday January 23, 2019 @01:22AM (#18976119)
Why not just use Firefox?
Re:Google proposes changes to Chromium which would disable u... by MarsAscendant on Wednesday January 23, 2019 @01:57AM (#18976269)
My liking one thing about Firefox needn't entail my wanting to use the whole browser.
Re:Google proposes changes to Chromium which would disable u... by bad_user on Wednesday January 23, 2019 @02:15AM (#18976342)
There's plenty to like about Firefox, like the Awesome Bar, has better bookmarking, is able to handle a huge number of tabs, has the "Multi-Account Containers" extension (with its offspring, e.g. "Facebook Container"), or the "Tree Style Tab" extension, just to name a few.

Also that it's not Chrome or based on Chromium is reason alone to like Firefox, because we need diversity for healthy web standards. That Chromium is open source is a red herring and open standards are more important.

I know developers have been preferring Chrome and for good reasons, but I've switched back to Firefox for the last 3 years and personally I find it hard to use Chrome these days, because Firefox has a better UI.

The only downside is that Chrome's dev tools still has some capabilities that Firefox lacks, but Firefox has been improving a lot, as you have seen.

[dead]
Re:Google proposes changes to Chromium which would disable u... by CalRobert on Wednesday January 23, 2019 @04:23AM (#18976882)
A person politely making some points in favour of Firefox in a discussion about browsers does not merit a rude response.
Re:Google proposes changes to Chromium which would disable u... by MarsAscendant on Wednesday January 23, 2019 @08:27AM (#18977889)
1. I never asked for any of that response, nor did the situation imply that I needed to learn about the points stated to make a better decision.

2. There's a general passive-combative conversation about browsers going on ("I like Firefox, I don't get why people like Chrome" and vice versa) that I never wanted to be a part of, mostly because of how disrespectful and counterproductive it is.

3. In a thread about ad-blocking, I got what is effectively an ad for Firefox.

I don't want any of this nonsense on my side of the table. "Use my product because I value it!" No, go away, I don't need this.

My choices are rarely uninformed. I spend time considering what to pick where I'm able to. I'd like my choices to be respected as such – not have my face plastered with someone else's unprompted opinion.

Here's an example of a better conversation:

– I liked this part of Firefox, and I wish it was in Chrome too.

– Do you not like Firefox whole, then? If so, why?

– Because of X, Y, and Z. I used it intensely for a month or so, so I got a good look at the way it behaves. I know X is solvable, but not Y or Z (I tried), and they're critical to my browsing experience.

– Okay, I see. I hope you consider (browser diversity, or whatever issues using Firefox's supposed to solve), because they're important.

– Oh yeah? Can you tell me why?

...and so on. A respectful conversation that sparks curiosity and provides context, without annoying any of the parties in the process.

Otherwise, you get what you give. Seems a fair approach to me.

Re:Google proposes changes to Chromium which would disable u... by onlydeadheroes on Wednesday January 23, 2019 @09:16AM (#18978247)
Nobody here is nearly as combative as you. Look up projection.

You'd like your choices to be respected, but you are incapable of offering civility. Is that also a choice we should respect, or is it beyond your control?

Re:Google proposes changes to Chromium which would disable u... by MarsAscendant on Wednesday January 23, 2019 @09:19AM (#18978267)
Like I said: you get what you give.
Re:Google proposes changes to Chromium which would disable u... by onlydeadheroes on Wednesday January 23, 2019 @10:00AM (#18978644)
Yes you said it but it makes no sense in the context. Perhaps try another line?
Re:Google proposes changes to Chromium which would disable u... by MarsAscendant on Wednesday January 23, 2019 @10:15AM (#18978780)
Sure.

"My name is Bond. James Bond."

Re:Google proposes changes to Chromium which would disable u... by Zardoz84 on Wednesday January 23, 2019 @02:10AM (#18976324)
you should try it again.
Re:Google proposes changes to Chromium which would disable u... by mdekkers on Tuesday January 22, 2019 @10:16PM (#18975345)
and basically unseated IE as the top browser

And didn't get to this spot on any kind of technical or feature merits, but essentially by relentless nagging on the Google search page to have users install it. Sure, devs/geeks etc were eager early adopters, but the bulk of users were steered this way by Google.

Re:Google proposes changes to Chromium which would disable u... by altfredd on Wednesday January 23, 2019 @04:27PM (#18983167)
I got the "love", because it was (and still is) advertised on google.com. Most non-technical people readily install malware when prompted. If malware is advertised on google.com, they will install it more quickly.

Microsoft have been stalling IE development for years, which allowed Mozilla to gain huge marketshare. This resulted in a lot of people learning, how to install a third party web browser. By the time Chrome was unveiled, Mozilla have coincidentally slowed Firefox development to a crawl. I remember the point, when the stable Firefox version was close to unusable, while everyone technologically proficient used a development release. It have been so bad, that some addons simply recommended not using the stable Firefox version. Btw, things have only gotten worse since then.

Chrome's dazzling success is result of it's aggressive advertising as well as sabotage and mismanagement, that killed off alternatives.