x64 version - Should I use it?
-
Actually I'm still using the x86 version of Vivaldi. Know I think about installing the x64 version.
Are there any known problems reguarding the x64 version of Vivaldi? Should I switch or should I don't?
Is it possible to update the x86 version to x64? Or do I have to reinstall? Is there any comparison between these versions? I couldn't find any.
-
Thanks a lot for the quick reply.
I'm using Windows 10 Pro so I'm able to use the x64 version of Vivaldi.
-
You can install both versions of vivaldi in different folders. Just select Advanced - Installation type - Install standalone, also - change Destination directory.
To copy your browser data to new version, copy "User Data" folder and overwrite it.What gives x64 version - little more "secure", and much more ram usage.
-
@asires said in x64 version - Should I use it?:
What gives x64 version - little more "secure", and much more ram usage.
So you wouldn't switch to x64 version?
-
-
-
@pooomukkel said in x64 version - Should I use it?:
Hmmm... Now I don't know what to do...
Try yourself. If you have very big amount of ram, or not use parallel multitasking (all ram resources will come to browser), it maybe better to use x64 for little more security.
-
@gwen-dragon said in x64 version - Should I use it?:
Do you have problems with it?
No, I don't have any problems with x86 version.
@asires said in x64 version - Should I use it?:
or not use parallel multitasking (all ram resources will come to browser)
I play games and I am using 16 gb ram. So it would be better to stay with the x86 version... I think.
-
I think I will give it a try. Thanks a lot for your help!
-
@adomani said in x64 version - Should I use it?:
... can you tell me the main reason to systematically offer the 32bit version of vivaldi and this same on the system 64bits? Vivaldi seems to go against the logic of the other browser, namely to promote the 32bits or the others completely stop the 32bits version ...
...
It's just curiosity on my part, but it puzzles meWith modern software, everything is always in transition from where it currently is toward where it is heading in the future. This creates inconsistencies in documentation and sometimes in support, where the documentation is often not updated as quickly as the software itself. It also means software that depends on other software must successfully deal with transitions occurring in that external software, which give rise to still more possible inconsistencies.
There is a gradual evolution now underway from 32-bit systems toward 64-bit systems and software (just as there once was from 16-bit to 32-bit), but the 64-bit evolution is moving with notable jumps and pauses. 64-bit systems have certain capabilities that are lacking in 32-bit systems and most new computers and OS versions are now 64-bit in nature. However, existing 32-bit systems and software are still more than adequate for many user computing needs, hence there remains a strong desire and need to maintain backward software compatibility for users with 32-bit systems. Eventually, 32-bit software and 32-bit compatibility will be viewed as archaic (just as 16-bit compatibility now is) - but that day is definitely not here yet.
In the meantime, we are witnessing a software world still in transition, and that includes statements and recommendations in documentation that might have been true yesterday, but may no longer be completely accurate today. Hopefully everything will eventually get corrected and brought up to current speed, but errors and omissions will undoubtedly happen along the way. Given that the primary focus is ongoing development of the software itself rather than proofing and updating existing documentation, the errors are more understandable.
-