Hi, everyone. I'm here with POSWA. Again, we're here to talk about something related to the previous talk we did on channels, but different. What is the difference between Google Chrome, the browser, everybody knows and uses. Most of you probably use it. Chromeium. And Chromeium, I think the first thing we should say about it is that it's an open source project. That's really what it's meant to be. So yeah, the open source project, Chromeium is composed of three main things. First is the browser. Like you said, the Chromeium browser. Then you have the rendering engine, blink, it was a fork of WebKit. And finally you get the operating system, Chromeium OS. Okay, so let's focus on the browser side of things. So let's set aside the rendering engine and the OS side of things. So there's the Chromeium browser and there's the Google Chrome product, which is also a browser. So let's focus on the differences. The first one, probably an obvious one to most people in terms of difference is the logo. Right. Yeah. Different logos, different colors. Really colors for the Google product, Google Chrome. We get the blue one for Chromeium and we get the yellow one for Chrome Canary. So Canary will talk about it. Yeah, I think it's worth mentioning, but maybe not at this point just yet. So first difference logo. Number one. Number two, I mean, Chromeium is an open source project. So the source code is open source. Yeah, at the same time, the product that we ship, which is Google branded, Google Chrome, itself has a number of pieces that are not open source because we've licensed technology. So another difference would be that there is the bare bone Chromeium version and then there is the Chrome, which is not open source because which contains not open source bits. So that has consequences on some of the features that are, these browsers are able to offer. So for example, Chromeium will lack a number of things because we're missing those binary pieces we have in the product. So we want to talk about those. So, so be for mentioning that. Just two things, just that people will understand that. So there are Chromeium builds that are available on download dash chromeium.absorbed.com. So basically every day you get several builds of Chromeium. You can download and test. And then you have the Chromium browser package that is maintained by distribution maintainers. So you get one for Ubuntu, for VPN for all the Linux version. You will see there are some differences. First like you said licensing stuff, you don't have ADB flash embed in Chromeium. So no, there will be flash, no, there will be PDF either. Yeah, it's a plugin. And basically the Chrome team worked with ADB to provide the best security experience for users. So that's in Google Chrome. That's not in Chromeium. What else? Codex. Codex obviously. Codex audio, video codex. So Chromium obviously I'm sure will support things like VPA, GP9, Opus, VOP, there are all these different source and grade codex available in Chromeium. But there are some other grade codex that you have to pay for it. And Google does it and they provide it in Google Chrome. So this is MP3, H264 and ACI believe. So if you download a raw build of Chromium, you don't have access to those codex. But if you access Chromium maybe through one of the distribution, maybe the maintainer of that distribution has done the equivalent work of Google to fill some of those gaps. Maybe not all. But some did. So it's cool. OK, so Flash, PDF, Codex, some differences here. Maybe another major difference we should mention here at this point is the update mechanism for the bits that you have installed. And that's... Like if you need to remember one thing, that's the thing. Google Chrome updates whenever I need the push updates to you as a user, like to protect you. And if you use Chromium, you rely on the maintainer on yourself. There is a huge gap of security here. OK, so that's interesting. Maybe that's the time we should mention a canary. Yeah. So Chrome updates every six weeks roughly for a stable version. Then you get Chromium. You can download a Chromium build every day if you want. Like... Like you do probably. Like I do. But maybe you don't want to do that. You don't want to write a bash script for it. You can just use a canary. A canary is basically Google Chrome, updated every day. And this is where you should test all the upcoming DevTools feature, for instance, or even just the Chrome feature. So if you're a developer typically, you want to make sure it works on the target, which is Google Chrome, which everybody uses, but you probably want to test on Canary as well. Or maybe even on Chromium to see what's coming down the line. If you know there are new features which you rely on that are being added changed, that's probably a good thing to do to test on those things. And they can all be installed on the same machine, right? But one thing, a D-Storm Chromten area on the two-bitable Linux. Just Windows and Mac. So Windows and Mac, that's probably worth mentioning. One last big difference I see is the syncing part, which is something where it relies on the Google identity you can have in Google Chrome. So that means you have access to a number of synchronization features, the profile, all of that is actually related to the fact that you can talk to Google services. And that obviously is part of the Google product, not the Open Source project. Yeah. But if you use some builds maintained by Linux distribution, some embed API key, and you can do that. Right. So it's a good beauty of having this Open Source project. People can add value. Google obviously does its own product, but others can do similar things or different things and innovate in different ways. And they're on the value on top of that. Different clear. Cool. So I think we've gone through a number of differences. I hope it's more clear for you than it was before you started watching this. Thanks for watching. I know it's clearer for me before I start talking to Fonswell. Thanks for watching. Cheers.