421–430 of 487 posts
Regarding the topic of browser mono-cultures, I was web developer in the post browser war era in the early 2000s where we had a dominant IE6 and a stagnant browser landscape. It was bad. Real bad. But I'm actually fairly positive about MS getting into the chromium landscape and back into the game. Let's face it MS had lost all of its influence in the browser world before dropping IE and making this move. It is a Goog…
Could you elaborate on what made it bad? I am a web developer too, and for me, the biggest annoyance is feature inconsistency between browsers. Only yesterday, I was cursing under my breath, because webkit-based browsers allow scrollbar styling, but firefox doesn't. In our org, we have embraced CSS grid, but by doing so, made a conscious decision to finally ignore IE11 (rather than to use @supports and write fallback…
Earlier quoted context omitted.
www.just-eat.no Many (all?) Oslo postcodes start with 0, and their site truncates the 0 when you try to enter your postcode. Their stated solution was to use Chrome, so they don't get any of my business.
From your description, it sounds like they decided to use a "number" typed field for the post codes. This is of course incorrect, post codes are really just strings. While the bug manifests itself on firefox, it is hard to blame it for implementing the field according to spec [1]. Chrome decided to ignore the spec and leave the field more free-form, which in turn enables developers to use it incorrectly without detec…
If Chrome is your only target, the standard ceases to mean anything. The real standard is just whatever Chrome does.
Earlier quoted context omitted.
So you’d rather live in a world where all the web apps you use every day need to be installed and run with full user permissions? The web is the safest, most battle-tested sandbox environment to run apps in. It’s so safe that you click random links all day long, running 1000s of apps and never have to worry. I’ll take web apps over native apps from a security perspective, thank you.
I don't really think this is a problem anymore. It's more that no desktop OS provides secure native execution facilities a la iOS. The web browser was the best solution for sandboxing web applications in 1995-200x, but now CPUs have multiple cores, virtualization extensions, systems with multiple gigabytes of ram, etc. There are better ways to sandbox applications in 2020.
This is true despite the fact that on iOS, sideloading custom apps without a developer account is extraordinarily inconvenient.
Regarding the topic of browser mono-cultures, I was web developer in the post browser war era in the early 2000s where we had a dominant IE6 and a stagnant browser landscape. It was bad. Real bad. But I'm actually fairly positive about MS getting into the chromium landscape and back into the game. Let's face it MS had lost all of its influence in the browser world before dropping IE and making this move. It is a Goog…
I just wish they'd moved to Gecko instead of Chromium. It's not like Gecko is an inherently inferior engine by any stretch, and it would significantly bolster their marketshare so that developers actually have to test against it.
Earlier quoted context omitted.
Or they could have open sourced EdgeHTML. It's not like it was worse, than Gecko.
It was worse than Gecko. Gecko is excellent. Edge still has (had?) so many rendering issues on sites we make. One thing I find really impressive about Firefox, despite the completely different engine I _very_ rarely find FF-specific bugs.
Earlier quoted context omitted.
I just wish they'd moved to Gecko instead of Chromium. It's not like Gecko is an inherently inferior engine by any stretch, and it would significantly bolster their marketshare so that developers actually have to test against it.
> I just wish they'd moved to Gecko instead of Chromium. The usual answer to that complaint is that Gecko is harder to embed. MDN pages on the subject even mention it’s deprecated and that the documentation is obsolete.
Regarding the topic of browser mono-cultures, I was web developer in the post browser war era in the early 2000s where we had a dominant IE6 and a stagnant browser landscape. It was bad. Real bad. But I'm actually fairly positive about MS getting into the chromium landscape and back into the game. Let's face it MS had lost all of its influence in the browser world before dropping IE and making this move. It is a Goog…
I just wish they'd moved to Gecko instead of Chromium. It's not like Gecko is an inherently inferior engine by any stretch, and it would significantly bolster their marketshare so that developers actually have to test against it.
---
> I don't see why it's Microsofts responsibility to do whats worse for their products, users and business just to bring some sort of benefit to Mozilla which has awfully mismanaged over the past 10 years or so. The browser monoculture didn't happen over night it happened thanks to years of neglect from the other browser engines. I don't like this situation and don't even use Chrome myself but this is the reality of the web today.
I would wholeheartedly agree with you if Firefox Quantum wasn't so damn good.
I didn't use Firefox for years except for occasionally testing sites. Quantum blew me away in terms of rendering speed; it reminded me of Chrome in the very early days. I know that benchmarks say Chrome is still ever-so-slightly faster, and I can't explain that, but Quantum legitimately feels quicker when I use it. At worst, it's certainly not a downgrade from Chrome.
I do wish Firefox's interface was cleaner—the pocket integration and similar stuff just feels like icky clutter to me—but I've been able to mostly clean it up via about:config tweaks, and none of that's relevant to the rendering engine.
That Firefox managed to do all of this with much more limited resources than Chrome, and despite how many sites nowadays are built to target Chrome specifically... it's seriously impressive. I'd love to see what the engine could do with Microsoft's additional resources behind it.
Earlier quoted context omitted.
We started with Gecko in 2015, but it lost on many dimensions in a head to head comparison enumerating gaps vs. Chrome. DRM is just one example. We don't like DRM, but users want Netflix to work, and Google makes WideVine free-as-in-beer; whereas at the time, Mozilla had an Adobe deal that did not extend to non-Firefox Gecko embeddings. So we switched to chromium/Blink in late 2015. Much later, when I visited Apple i…
Hey, thanks for everything you've done for open source and open platforms. The reason you gave here for Brave not choosing Gecko (or WebKit) is interesting – but given Microsoft's deep pockets and tech know-how those reasons don't apply to them. I think this is a strategic blunder on Microsoft's part and I say this as a Linux user. :) Microsoft has now warmly embraced Linux – and I think they could have chosen this t…
It will make me happy to be able to stop supporting ie11 at some point in the future. Sadly, it doesn’t appear that ie11 will have an end of life date as it’ll be supported as long as Windows 10 is and Windows 10 appears evergreen. Hopefully Microsoft will make edge the default browser at some point.
> Hopefully Microsoft will make edge the default browser at some point. If you mean over IE11, that's probably a (dumb, unhealthy) Group Policy decision of your Enterprise as Edge has been the default browser in Windows 10 since launch. If you mean Edgmium (New Edge) over Edge Classic, it already replaces Edge Classic (entirely) when you install it, and there's a slow rollout through Windows Update already happening,…
LTSC/LTSB versions of Windows 10 (i.e. the ones that enterprises are supposed to use) don't have Edge and there's no way to install it. The same goes for Windows Server 2016 and 2019.