741–750 of 774 posts
Earlier quoted context omitted.
I believe the problem with Edge is (correct me if I'm wrong) that files that would need to be updated are used by Windows Explorer, so any update would need a restart of the machine.
I thought they pushed Windows 10 and Edge to let go of legacy cruft. This is so year 2000 that app update needs a reboot.
That's just the disaster. And the end of W3C standard development process. AFAIR it should be 3 independent implementations of the feature in order for Draft to reach Recommendation status. So technically all that means that web standards will be written by WebKit team alone. Sic transit Gloria mundi, sigh.
Is IE dead?
Earlier quoted context omitted.
The multiprocess architecture makes it run faster on newer machines, but slower on older ones. Have you tried disabling it (limiting to one process) though?
They've disabled that setting.
As a firefox fax, I hope this isn't true. The dominance of chrome isn't good for anyone. This will lead to (even more) sites not bothering to be made compatible with Firefox. We are headed back to the "designed for IE" days.
My understanding is that they'll be using the Chromium engine underneath, but still their own Edge "browser" and UI on top. IMHO, I personally think it's a good thing to consolidate on one engine to render HTML cross-platform for these two reasons: 1. Web developers no longer need to worry about supporting CSS and other edge-cases across various browser engines. 2. The Chromium engine itself is open source. There are…
- Without competitors, innovation is dead. If there was only one web-engine, why bother improving it further? Given that it's open-source, it could theoretically be forked, but in that moment you again have two different web engines or more. Also, Mozilla would have to fork Blink from day one, because many things in it, they do not consider acceptable.
- A monoculture means one security problem makes everyone vulnerable.
- Multiple implementations challenge standards. You still would want a definition of a standard, or an API if you will, to point web developers to. But those are only going to point problems out after you've already implemented it, and likely also after other websites are already using the feature productively. They also can't point out stupid specifications that aren't going to allow you to update your browser engine in the future. So, you'd be much more likely to have to break compatibility, which doesn't play well with the web.
Interesting, but what I really, really want them to do is EOL IE 11 so that the web can move forward without feeling guilty about the X% of users still on it. IE 11 has unfortunately become the new IE 6. As it is right now I believe the IE 11 EOL is tied to the Windows 10 EOL...which is not happening anytime soon. Many frameworks are dropping support for it anyway so I guess it will end up being defacto desupported.
There is a lot of Enterprise/Corporate stuff tied to IE. For example sharepoint stuff (which my work uses) heavily is tied to IE.
Earlier quoted context omitted.
> This will be especially true when Firefox inevitably shutters it's in-house efforts in a couple of years due to the amount of sites that won't work with it, and starts using Chromium too. It seems very unlikely: - Mozilla has been in a far worse uderdog position before during the IE6 era, with way more incompatible sites and less funding. - Mozilla is not for profit. Fighting for the open Web is one of their goal.…
>Firefox is now a fast, lean and fantastic browser again. This is not my experience. On my MacBook Pro it is slow and tends to cause system lockups on a regular basis. Everytime there is a new announcement about how the new Firefox has improved performance and stability I give it a try and each time am disappointed. On my phone the Firefox browser is almost unusably slow and slow enough that it can't replace Chrome.…
For this it's become my main work browser. At home I mainly use safari and it works great for 15-ish tabs.
Earlier quoted context omitted.
> This will be especially true when Firefox inevitably shutters it's in-house efforts in a couple of years due to the amount of sites that won't work with it, and starts using Chromium too. Watching Mozilla align Firefox's extension API with Chromium's, I'm a little surprised that they haven't already made the move. If browser evolution continues along the current path, I predict Firefox will switch to Chromium withi…
Do you mind listing mainstream sites that have serious glitches on Firefox? It's my main browser, and I can't remember one single mainstream site that glitches on FF.
Earlier quoted context omitted.
It comes down to who's in charge, and what their motivations are. Google's motivations include learning everything about you, and how to serve you more ads. Linus' motivations include writing solid code and flipping people the bird. It's not just about the current situation, either. When Linus finally goes to the bitbucket in the sky, there are so many companies, organizations and private individuals with an incentiv…
Perhaps Microsoft adopting Chromium will be healthy for Chromium too then. I don't expect Microsoft to immediately keep pace with Google's browser teams but they should be able to contribute significantly to Chromium and help balance out the direction of the project.
Earlier quoted context omitted.
>Firefox is now a fast, lean and fantastic browser again. This is not my experience. On my MacBook Pro it is slow and tends to cause system lockups on a regular basis. Everytime there is a new announcement about how the new Firefox has improved performance and stability I give it a try and each time am disappointed. On my phone the Firefox browser is almost unusably slow and slow enough that it can't replace Chrome.…
If one doesn't want to rely on anecdata, here [1] is a benchmark. Based on my experience and this benchmark, I don't how such a negative opinion can be supported. [1]: https://www.pcworld.com/article/3213031/computers/best-web-b...