8 ms·
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
by Wowfunhappy 7y ago
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.
- RcouF1uZ4gsC 7y agoOne huge advantage the Chromium has over Gecko is Google's Security Team (ie Project Zero). For most users, the web browser is one of the biggest attack surfaces and having arguably the best security team behind the browser engine is a good thing.
- sjwright 7y agoGoogle have certainly done a great job of maximizing the PR benefit from their security researchers. And it’s a great thing they’re doing. But regardless of how well individual companies market their respective security teams, Firefox has a comparable reputation for their browser engine. Yes some of that might be thanks to PZ, but that’s beside the point, isn’t it? Choosing Mozilla’s platform would have been better for code diversity, which has its own distinct security benefits.
- rtpg 7y agoI can understand value in multiple browsers for experimenting with new things (see Rust integration into Mozilla's engine), but what are the security benefits? Like if you have 3 different crypto imlpementations, you have times more teams that have to get a thing right. It seems way easier to try and get it right just once. Perhaps there's a holistic idea of "if one browser has an issue, at least it doesn't affect 100% of them" but given what CVEs look like in reality (often variations of the same attack across multiple programs) it seems like the cost/benefit would not be in our favor
- core-questions 7y ago> what are the security benefits? Not everyone gets hit with every attack. Biological systems work this way too.
- kortilla 7y agoMultiple implementations is a great way to highlight issues in the spec vs reality (assumptions, unspecified behavior, etc). If you only have one implementation, the implementation becomes the spec and you end up with people targeting compatibility for that rather than a specification. This happened with Cisco routers back in the day, Juniper had to add a flag to make a routing protocol compatible with Cisco because Cisco implemented it wrong but had so much dominance that Juniper had no choice if they wanted to get in the game.
- sjwright 7y agoThe biggest security benefit is that competition motivates everyone to work harder, to explore alternative solutions, to raise expectations. Competition means investing in ideas like Rust and Servo. Without serious competition you eventually get IE6.
- Scarbutt 7y ago* Firefox has a comparable reputation for their browser engine.* Is this really true? someone posted somewhere(can't find it) where it shows Firefox has a worst security record compared to Chrome. Also, in the past, Firefox was left out from hacking browser competitions because it was to easy to hack.
- asiachick 7y agoThis is flatly not true. Just dig through the CVEs and you'll see while they have a similar number of bugs Chrome's are mostly in the harmless category (browser got DOSed) where as Firefox's has had like 10x the bad category (code got executed outside the sandbox).
- gsam 7y agoIt's not actually clear that they prioritize their own products all that much. Certainly in regards to Project Zero, it seems the point is that they are detached from the rest of the product teams. (Correct me if I'm wrong) Outside of the security teams, I think it's actually that Chromium is much better fuzzed and scrutinized. They just have so many more resources, including those for security.
- tjpnz 7y ago>It's not actually clear that they prioritize their own products all that much. Certainly in regards to Project Zero, it seems the point is that they are detached from the rest of the product teams. (Correct me if I'm wrong) Most of what I've read relates to Microsoft products - and I'm not saying that Microsoft is better/worse than the rest when it comes to security.
- millstone 7y agoGoogle is here to protect you from the lovely document reader that they forcibly mutated into a toxic app platform.
- feross 7y agoSo 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.
- caspper69 7y agoI 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.
- Wowfunhappy 7y agoAs an interesting counterpoint, since iOS sideloading became semi-possible around 2014, there have been many more app-based Jailbreaks than Safari-based Jailbreaks. This is true despite the fact that on iOS, sideloading custom apps without a developer account is extraordinarily inconvenient.
- caspper69 7y agoI'm so sorry to respond so late; I would just like to point out "the cloud," and the fact that there have been very few hypervisor escapes. Just because there are more app-based Jailbreaks on iOS has little to do with what is technically possible given the hardware (recent Intel missteps notwithstanding).
- 7y ago
- mattzzz 7y agoTotally. The hell of security issues is what makes IE a terrible product.
- tracker1 7y agoI think the biggest reason they went with Chromium/Blink is simply because of market share... most users at this point are using Chrome for better or worse, and MS is going with the safest bet in terms of user compatibility for today's web.
- thawaway1837 7y agoI believe the reason was NodeJS and Electron, wasn’t it? Basically, MS expects NodeJS and especially Electron to become fairly important going forward (MS’s 2 newest and highly successful apps are both Electron based...VS Code and Teams). There is no indication that either of those are moving away from Chromium anytime soon.
- DaiPlusPlus 7y agoThe sad thing is that those apps' HTML and JS probably are standards-compliant, so supporting Slack, Teams, VSCode, (Electron) Skype, etc in a Firefox-based version of Electron should be possible and very straightforward - yet it probably won't happen. What's sad is that Windows 98 fully supported desktop-based HTML+JS apps ("HTA Applications"), with access to native resources (using COM via `new ActiveXObject`) and it works with IE11 still - Microsoft just never pitched it as a serious development platform for some reason. Just imagine what today's world would be like if Microsoft did pitch HTA as a successor to VB6 (instead of the quickly-abandoned WinForms platform, now barely on life-support) (I'm mostly thinking we wouldn't be stuck with excessive memory consumption in Slack, and these apps would be able to use things like native context-menus and accessibility features)
- tomc1985 7y agoWinForms was never "quickly abandoned" ... MFC has been the defacto standard for Windows UI since Win 3.1
- DaiPlusPlus 7y agoWinForms did not receive any significant updates after .NET Framework 2.0 and Visual Studio 2005 - integration with the new User32 controls added in Windows 7 was only through downloaded optional redistributable DLLs. Ever since the .NET Framework 3.0 (and until UWP) Microsoft was selling WPF as the way to build Windows desktop applications without C/C++.
- lostmsu 7y agoOr they could have open sourced EdgeHTML. It's not like it was worse, than Gecko.
- userbinator 7y agoOpen-source IE would be even more interesting to see, mostly because the early versions ran well even on systems with two orders of magnitude less RAM and CPU power than ones today; especially when displaying static pages and not JS-heavy apps. I remember the Firefox of the time was noticeably more sluggish than IE6 and used more RAM, and know quite a few people who tried FF and went back to IE for that reason.
- emayljames 7y agoI could just imagine them looking at the (security) horrors of the IE source code, and with a cold sweat, sticking it in the drawer.
- Wowfunhappy 7y agoIt 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.
- tallanvor 7y agowww.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.
- Frizi 7y agoFrom 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 detecting the compatibility bug. [1]: https://www.w3.org/TR/html52/sec-forms.html#number-state-typenumber https://www.w3.org/TR/html52/sec-forms.html#number-state-typ... > User agents must not allow the user to set the value to a non-empty string that is not a valid floating-point number. If the user agent provides a user interface for selecting a number, then the value must be set to the best representation of the number representing the user’s selection as a floating-point number.
- ekianjo 7y agoIf you look at long term investments are you confident Gecko will still be around in 10 years? Chromium is the only safe choice they had.
- Wowfunhappy 7y agoIf Microsoft had also gone with Gecko? Yeah, I'm quite confident Gecko would still be around (and maintained by many people other than Microsoft) in a decade. I think it will be around anyway btw, although I'm perhaps less sure.
- alwillis 7y agoEven the guy who literally birthed Firefox (Brendan Eich) picked Chromium for Brave, his new browser.
- Inityx 7y agoYeah, but he also designed JavaScript, so...
- wavesplash 7y agoUnder a 2 week deadline. I challenge you to do better.
- tomc1985 7y agoMost likely he had been thinking about the project for some time. But the 10-days-execution story sounds much nicer
- Gene_Parmesan 7y agoHe was... kind of. My understanding is Eich had been thinking for a while about the idea of bringing a version of Scheme into the browser. He was lured to work for Netscape by the promise that yes, he could do this. Unfortunately the business decision came down that the language's syntax had to approximate Java. So the semantics of the language had probably been settled in his mind for quite some time, but the syntax change still makes the 10 days an impressive feat. (And also explains a lot of the weirdness in JavaScript -- you're writing code and expecting it to behave like a C-like, but you're actually kind of writing quasi-Scheme and you don't know it.)
- BrendanEich 7y agoI've spoken and written about the early days, e.g., here: https://www.youtube.com/watch?v=aX3ZABCdC38 https://www.youtube.com/watch?v=aX3ZABCdC38 Friends from SGI recruited me (second attempt) in March 1995, I joined in early April but in the server group. I thought a lot -- but worked too little due to server commitments -- during the month of April, about "the scripting language" which was suggested to be Scheme when I was being recruited, but which by the time I joined could not be Scheme, due to the impending Java deal between Netscape and Sun. Java meant either no scripting language, or a kid-brother language, which meant C-like syntax, primitive vs. object types as in Java, and other unfortunate consequences. When I transferred to the client group in early May, I had to produce a demo very quickly. I chose first class functions and (barefly there at first) prototypes as the building blocks. The rest is history.
- latexr 7y ago> 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.
- Wowfunhappy 7y agoIs this something Mozilla could feasibly improve?
- latexr 7y agoIt might not be worth the effort, and instead concentrate on Servo[1]. [1]: https://servo.org/ https://servo.org/
- deleted 7y ago[deleted]
- Wowfunhappy 7y agoResponding to a reply that was deleted while I was in the process of writing my response: --- > 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.
- bobbylarrybobby 7y agoI think Quantum is smarter about what it prioritizes rendering. Time to complete page load may be slower in Quantum, but Quantum makes sure to display key parts of the page so that it appears to load faster.