Firefox 5
-
I am currently using Firefox 7.0a nightly build, and browser is faaaast...
-
Memory footprint is much less than in 4.0 Also the plugins doesn't start to consume cpu like grazy yet :-)
-
I haven't noticed any problems.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Maybe, but its very odd. I can only get the local copy of this file[^] to load with its font by following a link from another page. If I try to load the page directly, by opening it in a new tab from the file system or by pasting its link into FF5's URL box, the font doesn't load. This only happens in the local mirror of my website. On the web everything seems okay. Strange... I've decided to develope my pages with another browser for the moment, and give the problem some time to go away. :)
-
Chris Losinger wrote:
now that i have it, i still don't know why it deserved a major revision.
They're trying to catch up with IE and Chrome.
The 3-legged stool of understanding is held up by history, languages, and mathematics. Equipped with these three you can learn anything you want to learn. But if you lack any one of them you are just another ignorant peasant with dung on your boots. R. A. H.
Glad someone started this topic. The whole versioning of a software is a very vague /to me at least/ concept. I'm sure there are numerous ways people can choose how to follow come up with their versioning standards. For example: according to time, like quarterly release of major version and what not, or major core change and complete rebuild /which is what most people are used to/. Unfortunately Chrome chose not to pay too much attention at the version of the product and just roll the software along. I'm sure they're going to come up with major changes in the core and whatnot but I doubt they're gonna mention it and use it as a marketing tool. Safari, uhhhh... yea IE, i believe is following the traditional microsoft way: release, get-feedback, rebuild on feedback and tech, release cycle, where each cycle is a major version, I'm ok with that. FF is an open source development, leaving it no choice to have major builds running separately making everyone to have a choice to upgrade. Then their versioning which just screws up with everyone's belief in every major version is a brand new different browser, where in fact they announced they're not going down that path. I think they're trying to lure people that use IE by saying "IE comes up with a new version every so often, so do we." This just reminds of a line in the "Tron: Legacy" nothing's changed it's just a new number. In the long run I think FF's gonna loose a lot of users if they don't: 1. quit asking about upgrading and just upgrade 2. quit making up new major versions, when nothing really is changed, at least as far as anyone can see. OR go as chrome, leave the whole versioning from the title. If(FF4 == FF5) return FF; my own conclusion: if you're going to have frequent upgrades, leave the versioning to the eyes of the developers and those who actually read changes.txt. Even though there are no written rules, but major versions should only be given to those softwares that have changed their core library AND redesigned the interface. I know people at mozilla will have answers and everything,
-
-
I did. Everything's fine except an add-on that seemed to be incompatible, but I can't remember what it was so after all it should have been something almost never used. About apparent no changes from FF4, it could be that they are trying to give the sense of innovation that (strangely) is given by the IE versions marketing. I don't bother if the interface looks the same, it is not the way I judge software major releases. I suppose there must be something changed in the core, and maybe that was already almost ready when FF4 shipped. In the worst case, there must be at least security enhancements. And since it took me almost no time and no efforts to upgrade, why not?
-
-
Glad someone started this topic. The whole versioning of a software is a very vague /to me at least/ concept. I'm sure there are numerous ways people can choose how to follow come up with their versioning standards. For example: according to time, like quarterly release of major version and what not, or major core change and complete rebuild /which is what most people are used to/. Unfortunately Chrome chose not to pay too much attention at the version of the product and just roll the software along. I'm sure they're going to come up with major changes in the core and whatnot but I doubt they're gonna mention it and use it as a marketing tool. Safari, uhhhh... yea IE, i believe is following the traditional microsoft way: release, get-feedback, rebuild on feedback and tech, release cycle, where each cycle is a major version, I'm ok with that. FF is an open source development, leaving it no choice to have major builds running separately making everyone to have a choice to upgrade. Then their versioning which just screws up with everyone's belief in every major version is a brand new different browser, where in fact they announced they're not going down that path. I think they're trying to lure people that use IE by saying "IE comes up with a new version every so often, so do we." This just reminds of a line in the "Tron: Legacy" nothing's changed it's just a new number. In the long run I think FF's gonna loose a lot of users if they don't: 1. quit asking about upgrading and just upgrade 2. quit making up new major versions, when nothing really is changed, at least as far as anyone can see. OR go as chrome, leave the whole versioning from the title. If(FF4 == FF5) return FF; my own conclusion: if you're going to have frequent upgrades, leave the versioning to the eyes of the developers and those who actually read changes.txt. Even though there are no written rules, but major versions should only be given to those softwares that have changed their core library AND redesigned the interface. I know people at mozilla will have answers and everything,
fuximus wrote:
In the long run I think FF's gonna loose a lot of users if they don't:
1. quit asking about upgrading and just upgradeOn the contrary: when software starts to upgrade itself without asking, that's when I make it go away.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-