![]() ![]() We’ve made a lot of progress since that first development update. This version of Firefox runs in both the Windows 8 “classic Desktop” environment, and in the new “Metro” environment. Name it something like OPapi (open plugin).Today’s preview marks the beginning of Mozilla community testing for the Firefox Metro browser designed from the ground up for Windows 8.Įarlier this year, we began development on a version of Firefox that runs on x86 Windows 8. So until a new api is made and major plugins get a good release out, take it slow. For now, there are no alternatives for many useful legit things like say the unity plugin. ![]() Don’t break your browser for hundreds/thousands of legitimate sites just because blah blah npapi. Support open software and make it happen and functional for everyone before you deprecate useful features many many people and developers use. And get the big partners to have proper releases available for it long before you removing npapi.ĭon’t be assholes like google. Yea we get NPAPI is very outdated, etc.īut if you must make a new one, make it open and functional/available to all browsers. Hopefully they at least take a smart route about this. (Average joe is only gonna click your biggest download now button, not caring about how many bits it is, you can link that to a crippled noob whitelist only version if you must, but leave the power user builds available). Especially not power users that seek out special version like 64bit. ![]() Especially considering 99.9% of firefox users are never affected by plugin vulnerabilities. Hard coded restrictions and removing features are pretty asshole things to do imo. This is above my computing illiterate knowledge : I just observe. Surprisingly or not, after cleaning RAM cache if I proceed further and call about:memory then clean it with ‘Minimize Memory Usage’ (or use the dedicated Firefox add-on called ‘Free Memory Button’) I notice after such a scenario as above-mentioned with Google Maps… several hundred MB of rendered memory, as if the browser hadn’t handled allocated RAM correctly. For example, Google Maps with extensive Earth/Street View eats plenty of RAM, I mean a lot! Well, it swallows far more (I’d say twice) when in 64-bit mode. What I can say here with Cyberfox 64-bit (Cyberfox is a Firefox fork with 32-bit and 64-bit versions but also removed/modified/enhanced features) : running sites which call much RAM, the amount called with Cyberfox 64-bit is far, far more than that with Firefox or Cyberfox 32-bit. A lingering 64-bit issue I’ve read concerning Firefox is the way it manages memory, not in the good with ability to handle over 4GB, but in the very way it handles RAM, as if it was doubling allocations in certain circumstances. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |