It does? Cool! I was disappointed not to see this option, but since it sounds like it does anyway, now I'm happy. Since the devs are ex-Opera team, I'm sure this will be configurable in a future build. Not that I want to turn it off, of course, but the option should be there.
I had a similar problem.
It did not go away until I did this:
1 Close Vivaldi
2 find your vivaldi folder on your home/user page and delete it.
It then forgets it was ever started and you can start a new "first time"
x86 builds run on x64 hardware, but the other way around is not true. So why only a 64b build instead of only a 32b build ?
It would work everywhere.
Also, some indication of the architecture on the download popup would be useful.
And on my part, I have an x86 ubuntu desktop, because I installed it a long while ago, and only upgraded. And there isn't an easy way to migrate.
Why would I want to reinstall my OS to be able to use a browser ?
Thanks for the reply…Ctrl-N works fine, but interestingly, clicking on New Window in the taskbar Jump List doesn't do anything...
As for a fix, personally, I would rather see a setting which provides options in addition to Last Page...it's very rare that I want to go back to the active page when I shut down....different strokes, I guess....
Yes the UI is slow on my old laptop(AMD Turion 64 X2 Mobile@2000MHz; ATI Radeon X1250) and that is the biggest issue so far.
Still, i like where all this is heading and maybe i'll finally have a real alternative to the old opera(which i'm still using)…
ps. The panel toggle could've been thinner(2px max)
Maintain a 32bit version for those who want it.
I was not asking to drop 32bit completely.
Performance benefits of 64bit are minimal in normal browsing use.
This has nothing to do with the performance.
Single-process vs multi-process:
Having 1 process with 1 set of system and 3rd party modules in memory is better than having 20 processes with 20 sets of same modules. Better for RAM and for swap file. CPU usage is also more predictable.
64-bit vs 32-bit:
64-bit process will not start losing stuff and crashing after reaching 1-1.5 GB of RAM usage. This is a real case scenario. Not 3 GB and not 2 GB - browsers with many tabs force memory sections to have more segments. A direct result of momery fragmentation.
Also, "normal browser use" is where Chrome dominates. People who liked old Opera used to be able to do a little bit more than "normal".
I just commented on a topic about translation of vivaldi.net : https://vivaldi.net/forum/suggestion-box/236-the-official-translation-localization-thread?start=20 but again, if there's a need for a Polish translator, I'm eager to help.