News for hackers. Stuff that matters.
Re:The Era of the Trident Engine by amelius on Saturday January 25, 2020 @12:39PM (#22147412)
Why did Microsoft choose Chromium, and not Firefox?
Re:The Era of the Trident Engine by Macha on Saturday January 25, 2020 @12:43PM (#22147433)
Gecko is apparently a pain to embed. Other browsers built on Gecko such as Epiphany and Flock later moved to Webkit.
Re:The Era of the Trident Engine by samantohermes on Saturday January 25, 2020 @07:36PM (#22149604)
Blink is also not embeddable.
Re:The Era of the Trident Engine by franga2000 on Saturday January 25, 2020 @12:48PM (#22147471)
Market share. Many web developers these days are bad at their jobs (or are ordered to be by their bosses) and only test things on Google Chrome, causing many websites to have issues on Firefox (the same happened to Trident) . Using Chromium as a base allows them to ride Google's market share and have almost all websites work with their browser.
Re:The Era of the Trident Engine by miohtama on Saturday January 25, 2020 @04:54PM (#22148861)
Here is another theory:

https://news.ycombinator.com/item?id=22058923

Microsoft was somewhat already vested in Chrome tech before starting, so skill and knowledge was there.

I would love to read an official interview though.

Re:The Era of the Trident Engine by yedpodtrzitko on Saturday January 25, 2020 @12:43PM (#22147432)
Current portability potential of the engine. The codebase of Firefox has some legacy burden in it plus Rust as a dependency for building.
Re:The Era of the Trident Engine by ComputerGuru on Saturday January 25, 2020 @12:46PM (#22147453)
The rust part is actually an improvement as it is not in addition to but instead of. Building any rust component together with all its dependencies is one step and fully modernized. That’s one of the benefits moving away from legacy components with competing build systems duct taped together.

Additionally, pure rust dependencies (which is the ultimate goal of the effort) are all statically linked and different versions of the same library can be used multiple times without symbol remaining voodoo, etc solving all sorts of typical DLL hell issues associated with adopting a huge foreign component into a project.

Re:The Era of the Trident Engine by notriddle on Saturday January 25, 2020 @03:58PM (#22148584)
Yes, yes, I like the new libraries, too. The Quantum team is following the Boy Scout rule -- when they refactor code, they leave it better than they found it.

But Microsoft needs to release New Edge today. And today, Gecko is not made from a bunch of reusable, standalone Rust libraries. It's built from a couple of good libraries, plus a lot of ugly, tangled legacy. Some day, Gecko might be the best choice for software that wants to embed web technologies, but that's not today.

Re:The Era of the Trident Engine by ComputerGuru on Saturday January 25, 2020 @04:52PM (#22148849)
I never commented the viability of Gecko for MSEdge; I merely rejected the notion that Rust was part of the reason why it wasn’t viable.
Re:The Era of the Trident Engine by CydeWeys on Saturday January 25, 2020 @01:08PM (#22147590)
A lot of it boils down to codebase quality. I know some hardcore browser developers, and they prefer Chromium.