LordFrick

Also it has a deb repo for auto upgrading Thorium on Linux.

Yup. My friend who helps me make mac builds made this post. I wish he didn't put "21 yo.." Still, if your reading this Midzer, thanks for spreading Thorium!

I must thank RobRich999 for the loop optimizations.

Yep. Seen this on crbug.com

I've been making releases at least every week for linux, and at least every two weeks for windows.

Thanks man. I'm gonna keep working on it, and supporting it on GitHub by having a discussion panel, and making timely releases at least once a week. And about the name: RIGHT! I wanted to use another element name that ended in -ium and Thorium just stuck out at me.

lol yeah chrome isnt that old.

I agree, and there are also a few UI patches along with the addition of content shell and chromedriver in the installers and portables.

I know, I dont agree with using the 21 yo thing, but this post was made by a friend who helps me make the MacOS releases so.

Im looking into that. Im on that site too in the linux and windows section, right under RobRich999, who also makes avx builds. If you experienced issues, it was likely a bug in upstream, since we both use tip-o-tree, not stable or even beta or dev versions.

It doesn't boost security by alot, but its a sane default.

Heller, dev here. Many mllvm flags can break stuff especially in chromium, but the LOOP optimizations I added have been extensively tested by me and robrich999, and only signal thinlto to more aggressively optimize, or for clang to do additional passes on loop functions that it is already optimizing for.

Hey, dev here. The compiler flags have been noted to cause binary bloat, which is why they arent used. The AVX flags are noted in the source to be the next step, after they switched from SSE2 to SSE3. Lighthouse measures many things, some not on the client side at all. However, it does measure rendering speed, which is affected by browser speed/hardware. Thats why i included it