Earlier quoted context omitted.
safari is the new IE.
Edge is the new IE
So, Chrome is the new IE?
We Need Chrome No More
101–110 of 536 posts
Re: We Need Chrome No More
#102It left a sour taste in my mouth that Microsoft joined Chrome instead of investing in FireFox and helping them advance their multi-process architecture quicker.
Microsoft is in the ad business now.
Microsoft is largely in the PaaS business. Amazon is, too. It helps these companies to grow usage of outsourced hosting for third-party applications, much of which are web-based applications. They're often web-based not just at the user interface level but at the API and data handling levels. Web standards are actually good for business when you're charging all comers for processor hours at your data center.
Re: We Need Chrome No More
#103It left a sour taste in my mouth that Microsoft joined Chrome instead of investing in FireFox and helping them advance their multi-process architecture quicker.
I wish someone from Mozilla or MS would comment on this, to be honest. Were they even considered?
Historically, I've heard from various sources that Mozilla may not work at the same pace as some of the large corporations do in upstreaming patches and releases to the code base. This has (according to what I have heard, which may simply rest on rumor/speculation/heresey, mind you) kept a lot of large entities from getting on board.
I've also heard that in building Quantum this is less of an issue, but their code base is a mess, and chromium's is incredibly well documented and clean by comparison.
Anecdotally, I would be inclined to agree with my second statement up front, after just browsing the two, but please compare for yourself
Re: We Need Chrome No More
#104Other browsers need to catch up to Chrome with their development tools. I'd be happy to use Safari or Firefox for development, but... - I can't disable CORS in Firefox (yes, sometimes you have to disable CORS rather than modify the Allow-Origin header response, for example if you need to test against a production backend) (and, no, CORS Everywhere is not a sufficient solution). - I can't inspect WebSocket frames in a…
I agree. While the Firefox dev-tools improved a lot over in recent years, they are still not up to where the chrome dev-tools are. Currently, I try to use the Firefox dev-tools as much as possible but keep chrome prepared for some special cases.
From a consumer perspective, the story is very different: Any browser will probably do, but choosing Firefox has the best long term effect on the development of the internet.
Re: We Need Chrome No More
#105It left a sour taste in my mouth that Microsoft joined Chrome instead of investing in FireFox and helping them advance their multi-process architecture quicker.
This is kind of weird, because if there is anything Microsoft doesn't like, they can patch it and make it work differently. Just like Apple did with KHTML and Google did with Webkit.
I don't really get why people judge source code by politics rather than "stealing" (forking) from the best.
Re: We Need Chrome No More
#106The problem with these articles is that the recommendation always ends up just preaching to the choir: people who already switched away from Chrome nod in appreciation, but people who haven't switched literally get nothing out of these posts to convince them to switch to what is basically the same application made by a different company, with completely different conventions on where everything is, without any concrete perceived benefits (security and tracking are invisible problems, you don't sell someone on switching by saying they won't have them anymore, no matter how important you think that is). And to boot, the switch would almost certainly make things worse because add-ons people relied on won't work and now you've burdened them with having to find new and unfamiliar alternatives to what they were comfortable with.
Chrome's main problem isn't that it's overstayed its welcome and is strangling the web (whatever you want that to mean), it's that it's so pervasive that people have become accustomed to it to such a degree that you're now faced with needing to convince people to give up what they're accustomed to. And that's a _much_ harder sell. Using chrome needs to literally be a grating or even damaging experience before someone will voluntarily switch to a different browser.
Re: We Need Chrome No More
#107Other browsers need to catch up to Chrome with their development tools. I'd be happy to use Safari or Firefox for development, but... - I can't disable CORS in Firefox (yes, sometimes you have to disable CORS rather than modify the Allow-Origin header response, for example if you need to test against a production backend) (and, no, CORS Everywhere is not a sufficient solution). - I can't inspect WebSocket frames in a…
Yup, Chrome has the best devtools for what I need and I'll continue to use it until there's a better alternative.
Re: We Need Chrome No More
#108Earlier quoted context omitted.
I'd also add that 2008 Google was trusted by the public a lot more than 2019 Google.
> by the public by technical users I imagine the general public still trusts them all the same or maybe even more.
Reads to me a descending attitude towards normal users.
I was a non technical users when chrome come out. I was studying civil engineering then in college. I certainly like Google as a symbol of freedom and technology superiority in the more pure sense than msft.
Re: We Need Chrome No More
#109I enjoyed this post, but I take issue with the idea that Chrome was initially adopted, or served, "to break the Web free from corporate greed." Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. No one else had this at the time, and it was a big deal because Flash was still widespread so sites were even less stable than they are today. Luckily…
> I take issue with the idea that Chrome was initially adopted, or served, "to break the Web free from corporate greed." Indeed. When Chrome was first released Firefox had already broken the IE monopoly having reached around 33% of the browser "market share", and was still growing. Speed was the issue I seem to remember most people switching to Chrome for at the time.
I remember it grew to about 26% and then sort of stalled.
I don't remember where IE was at the time but I remember some websites were still only supporting it.
Re: We Need Chrome No More
#110> If it works as intended on Chrome, it’s ready to ship A great step Firefox could take in this space is improving the transparency and performance auditing of its own engine. Debugging rendering performance issues between browsers is still an absolute nightmare. If Firefox can provide a better developer experience than Chrome, it might increase the likelihood that web developers would use FF as their first-choice de…
I'm pretty sure this is a commentary on the laziness of devs/why browser dominance is bad for standards, when taken in context:
> The dominance of Chrome has a major detrimental effect on the Web as an open platform: developers are increasingly shunning other browsers in their testing and bug-fixing routines. If it works as intended on Chrome, it’s ready to ship.
When you're following decently established standards (not bleeding edge), it's usually Chrome that breaks now, not Firefox or Safari. Chrome truly is the new IE.