301–304 of 304 posts
It's crazy! This is not the Microsoft from ~5 years ago. They have really changed! Opening up to linux, cross-platform apps, open sourcing tech, open sourcing their patents(!), and now using open source chromium for MS Edge? Dam. I never thought I'd see the day...
It is an interesting time to be alive, that is for sure.
Earlier quoted context omitted.
There are occasional inconsistencies. Just this week I fixed a small styling issue that differed between Firefox and Chrome. I develop for Firefox first as well.
Just wanted to say thanks to everyone targeting Firefox first.
Earlier quoted context omitted.
How do I convince Chromium to adopt parallel engine components written in Rust, in this world? They won't do it, because the entire team at Google is staffed by C++ folks. How is that a better outcome?
Our team is staffed by engineers. We respond well to discussions of tradeoffs. If you'd like to present a proposal for writing parts of Chromium in Rust and speak in depth to the exact costs and benefits, we'd absolutely consider it. I know this because we _have_ been doing some of this consideration; a number of people on the team have floated the idea of using Rust for some parts of Chromium. But a real plan to do…
Edge does. I'm curious to see how this will work.
Earlier quoted context omitted.
Google does an insane amount of very deep work all the ways down to the compiler level getting Chromium compiling on Windows and compiling on different architectures. These teams are very well staffed. It makes strategic sense to go with Chromium if they're aiming for ARM64 support if they can get a huge amount of work for free directly (as opposed to incidentally) from Google to support clang on Windows – which is a…
As opposed to Quantum? https://www.techrepublic.com/article/mozilla-and-qualcomm-un...
The technology that article mentions is Microsoft's Intel->ARM translation, which is surprisingly good, and entirely unrelated to Firefox.
The "optimized" build they're talking about is almost certainly natively-compiled ARM64, and the reason it's hard is because Rust is built on an older llvm version...which doesn't have Google's patches that improve support for Windows ARM64.