What is Reddit's opinion of Chromium?

From 3.5 billion Reddit comments

> All these blog posts normally take a few weeks of review.

Let me just stop you right there. This isn't a blog post; it's an internal design document that somehow made it onto chromium.org. I know because I first saw it months ago when it probably wasn't public, and the context made it clear that it was the work of a small group of engineers who had been given a mandate to decide whether Rust should be allowed into Chromium, and on what terms.

Chromium has an engineering culture that's shot though with "not invented here" syndrome on many levels, and the conventional wisdom among Chromium developers is quite different from industry norms. Anything that might require doing things differently is met with extreme skepticism. Managers don't have a lot of say over technical decisions, but the senior engineers are more than capable of gatekeeping new technologies all on their own.

I made a bug report on chromium.org.

https://bugs.chromium.org/p/chromium/issues/detail?id=904994

It's really annoying having to wait few seconds for ui to become responsive again every now and then.

I'd just wipe ChromeOS and install Arch Linux on a Chromebook (yes it is possible thanks to the ArchWiki and Chromium.org). Yes, you can run the Krunker natively on Chrome OS but thanks Googles limitations yes with Dev Mode, theirs no point running the client on a Chromebook.

The Chromium.org core is permissively licensed and there is plenty of knowledge about it. Cloudready uses both the OS and Browser and many browsers use the browser-code.

Firefox is not thriving enough, Apple has a browser that is more successful.

It would be great if there was more competition, but the risks are limited. What is your concern?

There's no installer package for flavorless Chromium you just download and install. It's only available on the Chromium.org page as a source file you need to build yourself.

If it's on someone's computer then they've either compiled it themselves and therefore are already way above the level of needing Geek Squad, or it was packaged with something else, probably some kind of malware in most cases.

I found links in your comment that were not hyperlinked:

• Chromium.org

I did the honors for you.

^delete ^| ^information ^| ^<3

The only codecs supported by chrome are listed over here: chromium.org/audio-video

If our media is in something like x265 (newer format used high def videos) then it is not gonna work

The one you get from https://chromium.org/ or upstream, not packaged by Ubuntu maintainers through apt-get. Apparently, the upstream's version doesn't ask for these permissions when used directly.

Hi, I was seeing this on Brave Nightly but it went away when I took the update to 1.7.13. The process running away with multiple cores was for Twitter's Progressive Web App (the URL was https://twitter.com/sw.js - "sw" => Service Worker, part of / old name for PWA infrastructure).

For all reading: if you see CPU hogging in Brave (or Chrome or other chromium browsers), open Window / Task Manager and let it stabilize. You may have to click on the CPU column header twice, not sure. You should see the hogging renderer process (or unlikely but possible, the master or "browser kernel" parent process). If it's a tab or set of tabs renderer, kill it and reload. It's possible to write runaway JavaScript that requires this kind of remedy (in which case the site should fix their runaway JS bug or bugs).

I'm not sure what triggered the problem I saw with Twitter on Nightly, but I haven't seen it since I upgraded. Brave Shields had no effect. We take changes from chromium.org all the time to keep up with security patches, so it could have been an upstream bug. More info, especially from Task Manager, is always helpful. Thanks.

Well, that's the problem, it's a work phone. You have install what they tell you.
If you have a personal Android phone, I'd use Bromite or Brave. They are Chromium based (the open source version of Chrome with Google tracking removed).

It is very clear to me that the problem is related to the extensions. What could be managing my Chrome extensions other than Chrome itself? I wrote chrome://management/ and it says Your device is not managed by an administrator. However, chrome://policy/ shows that https://chromium.org/administrators/policy-list-3#ExtensionInstallSources is managed, as you can see in my article I linked in my post. Let us know please, which is correct?

I just noticed this this morning. My about:/policy shows CookiesBlockedForUrls and JavaScriptBlockedForUrls which I assume is for uBlock Origin which shows up on the policy page. So I hope that's why, since it's a new version of chrome and all is well?

ugh... So ur basically accusing a company of having a predisposition against hearing impaired people? Report a bug @ chromium.org post the thread here. I'll star it, maybe others will too. "Is it too much to ask for google to set the standard in this area?" nope, it's not to much to ask, so ask... and if enough Redditors star it, they may bump up the priority.

Head to chrome, in the top right is 3 little vertical dots (chrome settings). Then select Help > About Chrome OS. A new settings like window will pop up, then select detailed build information. The current operating system channel is listed under the 'Channel' section. You can switch to beta if you want but it most likely won't fix the issue.

I will say, for YouTube the video is still playing when I turn off the device, but pausing the video before hand does not effect the video playing. So this is most likely a bug on all channels (except maybe Dev? But that is very unstable in experience). You can submit a bug report to the chromium project or but in the meantime you will just need to pause/close the app :/.

Bug Report Guidelines for Chromium Project: https://chromium.org/for-testers/bug-reporting-guidelines

To Report a Bug: https://crbug.com/wizard

How about dd full_dev_part_KERN.bin into /dev/sda4 and dd full_dev_part_ROOT.bin into /dev/sda5(in the case sda2 and sda3 is the current kernel/root, and vice versa), then run post-install?

The boot process and kernel params are well-documented in https://chromium.org and crouton wiki, and all source codes are available to read. I think there should be a way to do it without wipe.

I want to avoid wipe because this process is going to happen again and again if user want to keep there device updated.