05:43
Mr. Asim Rajput
People see "64" in lieu of "32" and think that because the number is doubled, the app must be better. Most of the time this is not true.
Just because an app is 64-bit does not magically make it better
In a browser application, 64-bit at this point has not proven to be any better than the 32-bit flavors. You can benchmark-benchmark-benchmark all day and spout out numbers-numbers-numbers, but the fact of the matter is that in practical use, you will notice tiny to no difference in performance compared to a 32-bit browser.
Now if we are speaking about, say, a video editing suite that requires gobs and gobs of memory to crunch and render video knowledge faster, then oh yes, 64-bit is better because that architecture can process and access everything faster.
Being that Waterfox is Firefox in 64-bit flavor, it still has the exact same memory-munching issue Firefox does. That's not fixed, and that's not Waterfox's fault at all. The way the engine works explodes in memory use by nature.
Think of it this way: Would you notice a difference between a 32-bit Microsoft Word and a 64-bit Microsoft Word? Nope. Document load time over a network would only be slightly faster on 64-bit (meaning you wouldn't notice any significant difference). Startup and shutdown would show no major difference in speed. You get the idea.
Just because an app is 64-bit does not magically make it better
In a browser application, 64-bit at this point has not proven to be any better than the 32-bit flavors. You can benchmark-benchmark-benchmark all day and spout out numbers-numbers-numbers, but the fact of the matter is that in practical use, you will notice tiny to no difference in performance compared to a 32-bit browser.
Now if we are speaking about, say, a video editing suite that requires gobs and gobs of memory to crunch and render video knowledge faster, then oh yes, 64-bit is better because that architecture can process and access everything faster.
Being that Waterfox is Firefox in 64-bit flavor, it still has the exact same memory-munching issue Firefox does. That's not fixed, and that's not Waterfox's fault at all. The way the engine works explodes in memory use by nature.
Think of it this way: Would you notice a difference between a 32-bit Microsoft Word and a 64-bit Microsoft Word? Nope. Document load time over a network would only be slightly faster on 64-bit (meaning you wouldn't notice any significant difference). Startup and shutdown would show no major difference in speed. You get the idea.
Yes, this does mean by having the tabs open of webmail, Facebook and Netflix that Waterfox will explode up to half-a-gig of memory use by sitting there like Firefox does. Again, this is not Waterfox's fault. Its from the engine the browser makes use of.
Using unofficial builds of browsers is not exactly a nice suggestion
Major browsers release security updates quickly ought to any issues be discovered, and the unofficial builds are always second in line for them. Whatever team is building the unofficial build receives a notice from the official provider, they compile a version, then release but its always after that major provider releases it first. And sometimes this can take weeks or even months for this to happen. Why? Because unofficial builds of browsers are released by tiny teams that don't have the resources the major providers have. In other words, they "get to it when they get to it". No, this is not an accusation of laziness whatsoever. Like I said, smaller teams of programmers don't have the time and resource larger teams do.
Using unofficial builds of browsers is not exactly a nice suggestion
Major browsers release security updates quickly ought to any issues be discovered, and the unofficial builds are always second in line for them. Whatever team is building the unofficial build receives a notice from the official provider, they compile a version, then release but its always after that major provider releases it first. And sometimes this can take weeks or even months for this to happen. Why? Because unofficial builds of browsers are released by tiny teams that don't have the resources the major providers have. In other words, they "get to it when they get to it". No, this is not an accusation of laziness whatsoever. Like I said, smaller teams of programmers don't have the time and resource larger teams do.
Ought to you use Waterfox?
However if you are expecting the fact Waterfox is 64-bit to cure existing issues with Firefox primarily concerning performance and memory-munching, I seriously doubt someone who makes use of it will notice any significant difference.
I downloaded it and tried it out. Its a nice 64-bit browser, and the nice part is that it operates using the same profile as your existing Firefox installation as far as I can tell. Add-ons that work in regular Firefox appear to work in Waterfox with no issues, so that's nice.
But don't take my word for it. Try Waterfox for yourself and see if it works fro you.
However if you are expecting the fact Waterfox is 64-bit to cure existing issues with Firefox primarily concerning performance and memory-munching, I seriously doubt someone who makes use of it will notice any significant difference.
I downloaded it and tried it out. Its a nice 64-bit browser, and the nice part is that it operates using the same profile as your existing Firefox installation as far as I can tell. Add-ons that work in regular Firefox appear to work in Waterfox with no issues, so that's nice.
But don't take my word for it. Try Waterfox for yourself and see if it works fro you.
0 comments:
Post a Comment