LordFrick

3 ms·

1. 1.▲
   Show HN: Thorium – The fastest browser on Earth(thorium.rocks)

   2 points by LordFrick 4y ago|3 comments
2. 2.▲
   by LordFrick 4y ago

   Also it has a deb repo for auto upgrading Thorium on Linux.
3. 3.▲
   by LordFrick 5y ago

   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!
4. 4.▲
   by LordFrick 5y ago

   I must thank RobRich999 for the loop optimizations.
5. 5.▲
   by LordFrick 5y ago

   Yep. Seen this on crbug.com
6. 6.▲
   by LordFrick 5y ago

   I've been making releases at least every week for linux, and at least every two weeks for windows.
7. 7.▲
   by LordFrick 5y ago

   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
8. 8.▲
   by LordFrick 5y ago

   lol yeah chrome isnt that old.
9. 9.▲
   by LordFrick 5y ago

   I agree, and there are also a few UI patches along with the addition of content shell and chromedriver in the installers and portables.
10. 10.▲
    by LordFrick 5y ago

    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.
11. 11.▲
    by LordFrick 5y ago

    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
12. 12.▲
    by LordFrick 5y ago

    It doesn't boost security by alot, but its a sane default.
13. 13.▲
    by LordFrick 5y ago

    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 addit
14. 14.▲
    by LordFrick 5y ago

    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 n