| 10:22 am on Oct 12, 2012 (gmt 0)|
At this rate I think we should be on version 22.214.171.124 by the end of next year!
| 11:33 am on Oct 14, 2012 (gmt 0)|
New fox came yesterday to me.;-)
| 5:34 am on Oct 19, 2012 (gmt 0)|
SO is there plan to reach firefox V 50 by end of 2012 :p...never seen minor updates being given major version labels. Something a miss here...whats their objective to merely reach new milestones in terms of versions if they cannot add remarkable and innovative functionality to the browser.
Opera is mother of all browsers when it came to multi-tabs, compression, turbo, new modes; they were first to introduce these stuffs.
Don't know whats firefox upto ?
| 7:14 am on Oct 19, 2012 (gmt 0)|
Their plan is to release a "major" version number every few months, irrespective of feature changes.
I forget whether it is 3 or 6 months, but it's short.
| 2:16 pm on Oct 19, 2012 (gmt 0)|
|Their plan is to release a "major" version number every few months, irrespective of feature changes. |
Objective for doing so ?..What they will achieve ?
| 2:33 pm on Oct 19, 2012 (gmt 0)|
Every update hogs more RAM, no thank you.
| 2:58 pm on Oct 19, 2012 (gmt 0)|
I can't think of any positive outcomes.
| 7:27 am on Oct 23, 2012 (gmt 0)|
|I forget whether it is 3 or 6 months, but it's short. |
Seems that they're going much faster than that, and also faster than was announced in April 2011.
We were to have had FF5 in 18-weeks (June 21, 2011), and the cycle was then, as I understood from the article I linked to in the post below, to be shortened to 13-weeks, which is 4 times a year, but we're at v16 in less than two years. What did I miss, or did they speed it up? See...
Mozilla Switches Firefox to 18-Week Development Cycle
It's a PITA.
| 2:15 am on Oct 25, 2012 (gmt 0)|
@TypicalSurfer - Since it's talked about all over the web about Firefox huge improvements in reducing memory usage and increased speed, how is it you are seeing increased memory usage? Mine is about half what it was a year ago.
As noted in the link, Firefox has been doing this for over a year and it's the same thing Google is doing with Chrome. It allows for incremental improvements to the browser instead of holding back releasing these improvements for other major changes that might take far longer to come out. iow, while small changes used to sit on the back burner waiting for a major change to be released a year from now, they release things as they are finished.
| 2:57 am on Nov 16, 2012 (gmt 0)|
Every update = exposure and reason for people to discuss it :)
| 7:50 am on Nov 16, 2012 (gmt 0)|
Not all the discussions are positive Mack and I doubt that the old adage that any publicity is good publicity applies here.