Live data from Hacker News

IE team sends a cupcake for FireFox 5

img.ly

21–27 of 27 posts

Re: IE team sends a cupcake for FireFox 5

#21
post #14
post #2

The Internet Explorer team sent Mozilla a whole cake for previous Firefox releases. http://www.openbuddha.com/2011/03/22/another-version-of-fire... What does this mean?! Perhaps Firefox 5's release is not as significant as earlier versions? ;-P

Times are tough for MS, can only afford a cupcake now. Maybe a donut next... then an eclair...

Then onto gingerbread or perhaps an cream sandwich.

Re: IE team sends a cupcake for FireFox 5

#22
IE team loves to poke shots at other browsers. Anyone remember the giant E placed on the lawn of Netscape's office in Mountain View? I think it was ~1997. They then dominated the browser market for the next few years.

Re: IE team sends a cupcake for FireFox 5

#23
I like when developers can put aside the retarded faux hatred we are all supposed to have for each other as dictated by our corporate / OSS overlords and do things like this, of course I am sure many will find some demeaning/ulterior motivevs, because you know, no way the IE team actually has human beings on it.

Re: IE team sends a cupcake for FireFox 5

#24

Earlier quoted context omitted.

It means that the IE team clearly saw through Mozilla's transparent attempt to get more cake by releasing more often.

This may be the last cake.

I meant that in the sense that they are switching to rolling versions (i.e. no more versions, it's just 'firefox')

Re: IE team sends a cupcake for FireFox 5

#27
post #4
post #2

The Internet Explorer team sent Mozilla a whole cake for previous Firefox releases. http://www.openbuddha.com/2011/03/22/another-version-of-fire... What does this mean?! Perhaps Firefox 5's release is not as significant as earlier versions? ;-P

Firefox 5 is the first of a string of insignificant releases. See http://en.wikipedia.org/wiki/Firefox#Development

It's a conceptual change. If your product is going to be incrementally evolved, major releases won't exist, so version numbers are not milestones anymore.

If they didn't do this, but switched to incremental development and still followed standard versioning practices, we'd be stuck at 4.xxx forever :)

Post reply on HN