241–250 of 304 posts
Funny that minor side project of KDE is now responsible for the vast majority of today's Internet traffic. Did the original authors of KHTML ever receive a single dime for their work?
Many, AIUI, were employees of Trolltech, and I assume Trolltech paid its employees.
Earlier quoted context omitted.
Opera and Brave are both chromium-based, rather than just using the blink engine. The official webdriver plugin for opera [1], published by opera, refers to their browser as "chromium based". The brave browser [2] is open source and you can see it syncs from Chromium [1] https://github.com/operasoftware/operachromiumdriver [2] https://github.com/brave/brave-browser
Opera's built on top of the Chromium content API (approximately Blink plus things like networking, some OS integration stuff, etc.), rather than a fork of all the UI code; the UI is a completely separate implementation and shares nothing (and this is very obvious if you look at early releases of Chopera, with it having much fewer features than Chromium of the same period).
Not completely true, many "model" part is shared with Chromium code (given the liberal license) while "view" part can be different.
The most exciting thing here is that, hopefully, we will get a version of Chromium on Mac without spyware.
Honest question, I don't think I ever looked, and now I am back on GNU/Linux.
On Windows, there is no build of vanilla Chromium, as far as I could find out. Then again, I did not try very hard, because I started using Firefox back when it was still called Firebird; the only incentive I had to check out Chromium on Linux were some web sites that did not work very well with Firefox (VPS console on Vultr, Netflix).
Earlier quoted context omitted.
Do you have examples? I use Safari and don’t find this to be true. Given Safari is what people use in iOS, id expect this to be rarely the case (most sites will test on an iPhone).
I created an internal application for our company to use that is essentially a directory of staff members. I do most my development in Chrome but the bulk of the users are on iOS (Safari). I always find little nuances that I need to tweak for things to be "just right" on Safari. One example is that in all other browsers (including Safari Desktop) a will show a little clear button ("X") at the end of the input. Some b…
Chrome also frequently attempts to cover up incorrect code with what it thinks the author probably meant. Firefox tends to be much better than Chrome at following the actual spec.
I tend to develop primarily with Chrome first for some different reasons (ability to disable CORS, support for self-signed certs with WebSockets, and its better debugging of WS frames), but I always make sure to test later with Firefox and Safari, and occasionally find code that worked in Chrome, but doesn't elsewhere, and the reason is almost invariably always that Chrome didn't follow the spec.
it seems like a lot of people don't know this but the current Edge engine is Open Source. look here https://github.com/Microsoft/ChakraCore
Earlier quoted context omitted.
It's also hard. Despite the complaints of Google dominance, Chrome is just a really good browser. I tried to switch to Firefox Quantum earlier this year as my daily driver. I had some minor annoyances, but I ended up switching back to Chrome for the devtools.
Web dev tools are something I have to take people's word for (and, to be clear, have no reason to doubt) since I don't do that kind of work so I have no clue what makes for good tools versus bad ones. But, my overall point still stands: If this is such a major failing in Firefox, is there nobody passionate enough to help keep a browser--that lots of people claim to want to use but for those tools--up to par with the…
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…
I think it's fair to say that a Rust proposal would have been dead-on-arrival a couple of years ago. It'd be seen as far too risky. It would have remained so in a world where Blink was the only browser engine.
It's a classic innovator's dilemma: with fewer browser engines, the fewer risks the industry will take. More browser engines allow more seemingly-risky innovations (such as parallel styling/layout, or Rust) to break through.
Could this be a bad thing for Firefox? Seems like Microsoft + Google is quite a rival to go against?
Microsoft is not an active rival - at least not from a technical perspective. It is probably up for Mozilla to make a choice: will we implement the standard or will we mimic the behavior of Blink for compatibility reasons (which may be incorrect in some cases).
Earlier quoted context omitted.
The article says the MSFT will be a significant contributor to Chromium. If anything, this means that Google will have _less_ control, as a second major internet player will be involved.
Who is the current Chromium project lead? What's the decision making process? How can MS employees participate? How can MS employees in the future go against the wishes of Google with regards to Chromium? Will we see revert wars?
The decision-making process varies based on where in the codebase you are. Blink has a lot of details on this, because it's what impacts the web platform and where we've needed to work with the most external input; you can read the various process summaries on https://www.chromium.org/blink . Things are less well-specified as you move up the stack because there's been less need to specify them. Perhaps that will change going forward.
Employee participation is the same as for Opera, Intel, Samsung, Yandex, etc. today: review and commit code, be an OWNER, participate on the mailing lists. Chromium tries to be a true open-source project.
As for disagreements about direction, I think the existing web platform discussions among all vendors provide an example of how disparate companies can come together and try to agree directionally. People from Brave, Opera, etc. already participate in those forums despite basing their browsers on the Chromium core. Blink sets a high bar for shipping features that have interop risks, so it's already true that the goal is consensus rather than a fractured web. And I'm sure Microsoft would not be keen to use Chromium if they didn't feel like they would have significant directional input where desirable.
Most of the concerns expressed in these comments seem reasonable on their face but also sound like the people expressing them haven't actually contributed to Chromium/Blink. I encourage people to chip in changes and even express opinions on our mailing lists. We try to welcome such contributions :)
Earlier quoted context omitted.
I'm the same way. Firefox first, then Chrome. If it works on Firefox, it will work on Chrome (and least that has been my experience).
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.