I've used both many times. I'm pleased with 32 bit except for the memory limitation (which I believe is artifically created). 32 bits is faster and more responsive. Contrary to what's many times advertised, 64bit OS's did not become a miracle.
If you have just 4/5GB is better to take advantage of the wasted memory using it as superfast browser cache rather than switching to x64. Yes and No. The limit is real but was overcomed ages ago, either in Linux and in Windows server, even NT4 Server can see more than 3GB w/o any major problem Yes, sure. At least in windows x64 means 1.6x more data to be transferred back and forth to the disk, memory and so on, which practically means that x64 is almost always slower, especially if you have an old hard drive. The advantages of x64 are very limited and restricted to a nice of programs (compression, audio/video conversion, math, and so on), not enough to justify the switch for most users. Everithing else is just marketing mumbojumbo. Linux is different. x64 there is usually not slower than x32, almost every program is available in x64 flavour, so even if Linux x32 is capable of managing large (and huge) memory configurations, x64 is the preferred choice anyway.
QFT, 8 GB is more like the minimum requirement now with some big stuff that came out more recently... Definitely at least 5 GB of RAM for 64-bit Chrome, or else you can expect the dreaded "Aw, Snap!" error message, with some programs... (if not 6 GB or more!)
What an exaggeration. I have 8GB on one of my machines, but that's the 2012R server which runs 3/4 VMs, one of them being server 2016... Using a 64 bit browser, especially one like chrome, which is multiprocess, is a competely pointless choice, it's just slower, more resource hungry, less compatible, and has ZERO advantages over the 32bit flavour. Choosing the right SW is easier than wasting money in RAM to run the wrong one. Then yes, surely RAM is like money, the more you have the better....
maybe you forgot to enable hardware acceleration for codec in VLC settings, you can set it in "automatic" mode.
If you have a 16-bit program/application that you need or really like... One can also run 16-bit apps in the x86 flavor but not x64 By adding the feature (NTVDM)
The lack of support for 16 bit apps on x64 is not a windows limit, it's a limit of x64 CPUs, but given how well DOSbox works, running 16 bit apps on x64 isn't really a problem.
No I'm not Indeed you can run 16+32bit apps OR 32+64 bit apps, you can't have 16bit apps running natively on 64bit OS, unless you use a SW emulation layer like dosbox, or ntvdmx64 It's a CPU limit h**ps://en.wikipedia.org/wiki/Virtual_DOS_machine
to se7an Consider to use SMPlayer with MPV or Mplayer instead of VLC. I believe it will have less performance issues.