4 ms·

Themes and the translation panel are the highlights according to their blog. And speed improvements.[1] [1] https://vivaldi.com/blog/vivaldi-5-0-desktop-themes

Themes and the translation panel are the highlights according to their blog. And speed improvements.[1] [1] https://vivaldi.com/blog/vivaldi-5-0-desktop-themes-translate-panel/ https://vivaldi.com/blog/vivaldi-5-0-desktop-themes-translat...

zamadatix 5y ago
"Speed improvements" in every release but there must be something about the way the browser is implemented that just kills performance/efficiency vs other Chromium browsers. Even a basic test like Speedometer 2.0 shoots out that DOM manipulations are 75% the speed of the same benchmark on Chrome, what on earth is it doing to cause that? The interface is great but between performance and bugs I've never been able to stay on it for more than a couple of months.
- jadbox 5y ago
  Is this still true of v5?
  - zamadatix 5y ago
    That's where I pulled the 75% result from just now, not sure if it's as systemic as it was originally as that's where I gave up bothering to test further this time.
    - thanatos519 5y ago
      It's fine on my 4-core Haswell Xeon desktop but I really notice the lag on my Haswell 2-core laptop. I suspect there's a bit too much Electron-type stuff in the UI. It's a small price to pay for a browser that lets me configure the UI the way I want it. If Chrome supported tabs on the side as well as Vivaldi, even with an extension, I might not have switched. The rest of the configurability is just gravy for me.
- cturtle 5y ago
  The UI is written in React, and apparently runs as a sort of an extension to chromium[0] according to a Vivaldi dev. I expect that would be a large source of performance decreases with a JS powered UI. It's certainly an impressive UI though. [0]: https://www.reddit.com/r/vivaldibrowser/comments/f9ui2b/is_the_ui_for_vivaldi_really_built_with_css_html/ https://www.reddit.com/r/vivaldibrowser/comments/f9ui2b/is_t...
  - Isthatablackgsd 5y ago
    That explains why I get beach ball of death in my macOS. Sometime it just hang indefinitely and I was wondering why this behavior exist in Vivaldi. I thought it was a bad memory leak.

zamadatix 5y ago

"Speed improvements" in every release but there must be something about the way the browser is implemented that just kills performance/efficiency vs other Chromium browsers. Even a basic test like Speedometer 2.0 shoots out that DOM manipulations are 75% the speed of the same benchmark on Chrome, what on earth is it doing to cause that? The interface is great but between performance and bugs I've never been able to stay on it for more than a couple of months.

jadbox 5y ago
Is this still true of v5?
- zamadatix 5y ago
  That's where I pulled the 75% result from just now, not sure if it's as systemic as it was originally as that's where I gave up bothering to test further this time.
  - thanatos519 5y ago
    It's fine on my 4-core Haswell Xeon desktop but I really notice the lag on my Haswell 2-core laptop. I suspect there's a bit too much Electron-type stuff in the UI. It's a small price to pay for a browser that lets me configure the UI the way I want it. If Chrome supported tabs on the side as well as Vivaldi, even with an extension, I might not have switched. The rest of the configurability is just gravy for me.
cturtle 5y ago
The UI is written in React, and apparently runs as a sort of an extension to chromium[0] according to a Vivaldi dev. I expect that would be a large source of performance decreases with a JS powered UI. It's certainly an impressive UI though. [0]: https://www.reddit.com/r/vivaldibrowser/comments/f9ui2b/is_the_ui_for_vivaldi_really_built_with_css_html/ https://www.reddit.com/r/vivaldibrowser/comments/f9ui2b/is_t...
- Isthatablackgsd 5y ago
  That explains why I get beach ball of death in my macOS. Sometime it just hang indefinitely and I was wondering why this behavior exist in Vivaldi. I thought it was a bad memory leak.