If you don't like Vivaldi, don't use it. It is that simple, no need for the sarcastic comments. I know what is involved in creating what they have produced, thus far. It is no mean feat for a team that small.

2 members found this post helpful.

Don't worry, I won't.
However, I do appreciate what the Vivaldi team has accomplished, but if one wants to run a google/chrome/chromium based browser, which I don't, why not just run chrome or chromium?
Being an "end user" I only know what I see, and, last I heard, I am free to express my opinion, as you are yours, but part of what I said was tongue-in-cheek. Hard to get that across with the written word.
Lighten up. You'll live longer that way.

For those who miss (or want) the various features I listed above, Chromium is not really going to cut it, since it is missing all of them.

Vivaldi sounds like everything I was hoping for when Opera first announced the switch to the blink engine, but regardless of how nice a basket Vivaldi turns out to be, I'm not going to make the mistake of putting all my eggs in it. Lesson learned from what happened to Opera 12.xx.

Integrated solutions are very slick and nice to use, but they are a huge pain when they're abandoned and you're forced to find alternatives for multiple functionalities you've come to rely on. It's pretty much the same reason I shun the big integrated desktop environments, preferring minimal window-manager based solutions and stand-alone applications. Classic Opera was the one exception I made to that guiding principle, and it ended up biting me.

Once bitten, twice shy.

1 members found this post helpful.

Its a fair point @GazL, though on the flip side, I don't see Jon (von Tetzchner) making the mistake of selling off a significant number of shares and hence losing control of Vivaldi. Pretty sure he also shares the "Once bitten, twice shy" mentality.

Anyway, whatever. For the time I was an Opera employee and you were a fan. Thanks for your support!

1 members found this post helpful.

Today I built and installed the vivaldi package (from vivaldi-preview_1.0.162.9-1_amd64.deb)
on slackware 14.1 64-bit. I logged out and logged in again.
There's no vivaldi in the menu (kde).
I wonder if vivaldi.desktop should be placed in /usr/share/applications/
(instead of /usr/local/share/applications/).
I launched it from an x-term. I didn't spend too much time on it but it seems to work ok.
I've had a favorable first impression.

No problems here (I also use KDE) nor for others I know are using it. If I was making a Slackware package then yes the .desktop file should go in /usr/share/applications/ but for an install script like the one I provided /usr/local/share/applications/ is correct.

P.S. Today's snapshot is 1.0.174.8-1. Update again, they have been working on tab performance.