3 ms·
I switched from Chrome to Vivaldi and back to FF for two reasons: 1) Vivaldi rendering performance is the worst I've ever seen in a browser. No idea how they m
by as2019 7y ago
I switched from Chrome to Vivaldi and back to FF for two reasons:
1) Vivaldi rendering performance is the worst I've ever seen in a browser. No idea how they managed that using webkit, but some sites would make tabs crash on a high end system.
2) The web developer tools are unusable due to bugs.
3) Fixing simple but impactful bugs takes too long.
I really like their useful and plenty settings for everything, but 1) and 2) make it a no go for me.
- Gustomaximus 7y agoVivaldi using Webkit... Its Chromium isnt it?
- as2019 7y agoThey're using Webkit, yes, but I guess it's highly customized. The performance is so much worse than Chrome and FF It's even possible to create pages in a way that reproducibly freezes and crashes Vivaldi. Their rendering process handles pages with many elements and multimedia objects very poorly.
- pseudalopex 7y agoVivaldi uses Blink.[1] [1] https://help.vivaldi.com/article/user-agent-spoofing/ https://help.vivaldi.com/article/user-agent-spoofing/
- xeeeeeeeeeeenu 7y ago>Vivaldi rendering performance is the worst I've ever seen in a browser. No idea how they managed that using webkit, but some sites would make tabs crash on a high end system. That's what happens when you build your UI using HTML, CSS and node.js.