On Windows I have tested recently Pale Moon a gecko based browser 30% faster than Firefox. On the same machine, Chrome works correctly under Windows (but always with hardware acceleration deactivated) I will test one day the official build Google Chrome for Linux (and not Chromium) through the FreeBSD Linux emulator. In fact, if I activate the hardware acceleration, at first sight, the browser seems to work very well and fast, but we rapidly get annoyed by number of interface disturbances : some extension and some buttons have no effect, trying to install or remove extension can freeze the system etc etcĮventually you use Nvidia, or Radeon newer graphics chipsets so you get a full acceleration and Chromium works fine for you. In fact chromium hardware acceleration seems to be incompatible with most old onboard Intel Chipset (yes I use some old computers). For chromium I have been forced to deactivate the hardware acceleration and I suspect the problem may be here. I can just guess that our hardwares are very different. I have read somewhere that in some future version of Firefox (57 ?) a new set of options should appear in order to adapt as closely as possible to the hardware specifications and gain speed by deactivating some options. Yes Firefox is rather slow this is a known issue even on Windows, but it is reliable and finally works correctly with a correct hardware configuration.
I have had a long time big issues with Midori but it seems at last that it works now (probably an early GTK issue as Midori for Windows has also very serious problems).
Since Opera for FreeBSD is not actively developed anymore I use Firefox or Qupzilla Since FreeBSD 9, diagnostic is still the same. I personally always have issue with Chromium under FreeBSD, for some strange reasons the browser finally hangs a few minutes later.
0 kommentar(er)
