21–30 of 115 posts
Chrome's numbers are not in the same scale as FF and IE too, of course. Users can't tell the difference between Chrome 6 and 7 like one can distinguish FF 2 and 3, or IE 6 and 7. I wonder, though, if Google was just trying to catch IE in version number with Chrome and once it's at 10, they'll stop increasing it so rapidly.
"the main focus of Firefox development in 2011, is to make sure there is no more than 50ms between any user interaction and feedback from the browser" Quite surprised to see this, judging from the fact that empirically the average human brain-hand response is around 200 ms. Only in competitive CS have i seen network latency in a non-LAN setting makes a difference in that scenario, but only when you are not on the ver…
Isn't the development cycle a bit too fast. 4 major versions in a single year.
Why? Major versions are just a number. How many major versions of Chrome were there last year? I haven't looked it up but I bet it was more than 4.
This doesn't however mean that other browsers too have meaningless version numbers.
Sounds like the main story is that they're redefining what a major version number means a la Chrome. Chrome's numbers are not in the same scale as FF and IE too, of course. Users can't tell the difference between Chrome 6 and 7 like one can distinguish FF 2 and 3, or IE 6 and 7. I wonder, though, if Google was just trying to catch IE in version number with Chrome and once it's at 10, they'll stop increasing it so rap…
"the main focus of Firefox development in 2011, is to make sure there is no more than 50ms between any user interaction and feedback from the browser" Quite surprised to see this, judging from the fact that empirically the average human brain-hand response is around 200 ms. Only in competitive CS have i seen network latency in a non-LAN setting makes a difference in that scenario, but only when you are not on the ver…
Brain-hand response is not the same thing as a perceived delay. Once latency becomes greater than 50ms, it becomes human noticeable -- aka "not instant." Given that UI response isn't used to trigger human reflexes, you are just misunderstanding the intent.
Of course this is just my experience, scientific findings may very well dispute my ignorance.
Sounds like the main story is that they're redefining what a major version number means a la Chrome. Chrome's numbers are not in the same scale as FF and IE too, of course. Users can't tell the difference between Chrome 6 and 7 like one can distinguish FF 2 and 3, or IE 6 and 7. I wonder, though, if Google was just trying to catch IE in version number with Chrome and once it's at 10, they'll stop increasing it so rap…
Until now, every version of Firefox had significant changes -- visual changes, changes to the way you interact with the browser.
It now sounds like Firefox will follow Chrome. It will keep the same UI, and simply add new features.
Which is fair enough, I guess, if the browser is to become the next platform (for Web apps). It's time for the browser to 'fade' into the background, to give Web apps focus; to empower the apps, rather than interfere with their operation -- much like any other OS!
Sounds like the main story is that they're redefining what a major version number means a la Chrome. Chrome's numbers are not in the same scale as FF and IE too, of course. Users can't tell the difference between Chrome 6 and 7 like one can distinguish FF 2 and 3, or IE 6 and 7. I wonder, though, if Google was just trying to catch IE in version number with Chrome and once it's at 10, they'll stop increasing it so rap…
I myself am already running version 11 (screenshot: http://jhn.me/4RYO) via their nightly builds.
"the main focus of Firefox development in 2011, is to make sure there is no more than 50ms between any user interaction and feedback from the browser" Quite surprised to see this, judging from the fact that empirically the average human brain-hand response is around 200 ms. Only in competitive CS have i seen network latency in a non-LAN setting makes a difference in that scenario, but only when you are not on the ver…
Sounds like the main story is that they're redefining what a major version number means a la Chrome. Chrome's numbers are not in the same scale as FF and IE too, of course. Users can't tell the difference between Chrome 6 and 7 like one can distinguish FF 2 and 3, or IE 6 and 7. I wonder, though, if Google was just trying to catch IE in version number with Chrome and once it's at 10, they'll stop increasing it so rap…
I doubt that the Chromium authors are concerned about trying to catch IE by having a larger version number. Their development calendar ( https://sites.google.com/a/chromium.org/dev/developers/calen... ) looks as though they have a rigid two-month schedule per version number. I myself am already running version 11 (screenshot: http://jhn.me/4RYO ) via their nightly builds.
Sounds like the main story is that they're redefining what a major version number means a la Chrome. Chrome's numbers are not in the same scale as FF and IE too, of course. Users can't tell the difference between Chrome 6 and 7 like one can distinguish FF 2 and 3, or IE 6 and 7. I wonder, though, if Google was just trying to catch IE in version number with Chrome and once it's at 10, they'll stop increasing it so rap…
Chrome auto-updates and generally always looks the same. I can't imagine why anyone -- users or developers -- would care what version number it's up to.