Live data from Hacker News

Why Internet Explorer will survive and Firefox won't

zdnet.com

11–20 of 26 posts

Re: Why Internet Explorer will survive and Firefox won't

#11
post #9

Fact is: Firefox had 4.6 Million downloads in the first 24 hours after its launch, IE9 had 2.3 Million downloads in the same period. The previous IE versions have continuously lost ground. I expect better researched articles from ZDNet.

> I expect better researched articles from ZDNet.

I cannot think of a single good reason why you would.

Re: Why Internet Explorer will survive and Firefox won't

#12
post #2

This article argues that apps are the only future for browsers and by virtue of the fact that Firefox doesn't have a dedicated "app ecosystem" it will be extinct. I don't follow the reasoning since I don't really see why I have to use Internet Explorer to use a Microsoft web app just as I don't have to use Chrome in order to get my Gmail.

The Chrome apps he's talking about get downloaded to your machine then run in the browser as if they were a webpage on the net. I'm guessing that Internet Explorer 9 has a similar feature but Firefox doesn't have anything like this on the roadmap.

Re: Why Internet Explorer will survive and Firefox won't

#13
post #7

This reads like linkbait to me. The author doesn't really have a coherent argument: he spends the first half of the article talking about Firefox's relatively slow* release cycle, but never bothers to explain why that's a death sentence. Instead, he jumps to another argument entirely in the second half: Firefox's lack of an "app ecosystem". This is truly delusional. Firefox has just as much of an app ecosystem as IE:…

Chrome apps get downloaded to your machine. They are not links.

Re: Why Internet Explorer will survive and Firefox won't

#14
post #2

This article argues that apps are the only future for browsers and by virtue of the fact that Firefox doesn't have a dedicated "app ecosystem" it will be extinct. I don't follow the reasoning since I don't really see why I have to use Internet Explorer to use a Microsoft web app just as I don't have to use Chrome in order to get my Gmail.

Actually this was the only part of the article that makes sense. Both Chrome and IE have APIs that add special features not part of the general html spec. For example, Chrome apps can run in the background even when a tab is not open. Firefox can't do that. IE apps can integrate with Windows 7 and be pinned directly to the taskbar and have access to jump list commands. Firefox can't do that.

Now I don't think that's enough to hurt Mozilla in any significant way, and these types of features will probably be standardized down the line, but it is true that these other 2 browsers have some special capabilities.

Re: Why Internet Explorer will survive and Firefox won't

#15
post #13
post #7

This reads like linkbait to me. The author doesn't really have a coherent argument: he spends the first half of the article talking about Firefox's relatively slow* release cycle, but never bothers to explain why that's a death sentence. Instead, he jumps to another argument entirely in the second half: Firefox's lack of an "app ecosystem". This is truly delusional. Firefox has just as much of an app ecosystem as IE:…

Chrome apps get downloaded to your machine. They are not links.

In my experience, most apps on the Chrome store are what Google calls "Hosted Apps": a link plus metadata and an icon [0]. They also provide "Packaged Apps" [1], which are downloaded and run locally as you describe, but this style appears to be much less popular with developers.

0: http://code.google.com/chrome/apps/docs/developers_guide.htm...

1: http://code.google.com/chrome/extensions/apps.html

Re: Why Internet Explorer will survive and Firefox won't

#16
post #9

Fact is: Firefox had 4.6 Million downloads in the first 24 hours after its launch, IE9 had 2.3 Million downloads in the same period. The previous IE versions have continuously lost ground. I expect better researched articles from ZDNet.

> I expect better researched articles from ZDNet. I cannot think of a single good reason why you would.

touché

Re: Why Internet Explorer will survive and Firefox won't

#17
post #15
post #13

Earlier quoted context omitted.

Chrome apps get downloaded to your machine. They are not links.

In my experience, most apps on the Chrome store are what Google calls "Hosted Apps": a link plus metadata and an icon [0]. They also provide "Packaged Apps" [1], which are downloaded and run locally as you describe, but this style appears to be much less popular with developers. 0: http://code.google.com/chrome/apps/docs/developers_guide.htm... 1: http://code.google.com/chrome/extensions/apps.html

Being hosted doesn't make them just links. Hosted apps still have access to many APIs not available in normal web pages. Such as cross-domain XHR, background pages (apps can run in the background even when the tab is closed), a licensing API that allows Google to handle the registration burden, etc.

Re: Why Internet Explorer will survive and Firefox won't

#18
post #7

This reads like linkbait to me. The author doesn't really have a coherent argument: he spends the first half of the article talking about Firefox's relatively slow* release cycle, but never bothers to explain why that's a death sentence. Instead, he jumps to another argument entirely in the second half: Firefox's lack of an "app ecosystem". This is truly delusional. Firefox has just as much of an app ecosystem as IE:…

Chrome Web Store is not a link directory, that's as much FUD as you accuse them of spreading about Firefox release cycle (which I agree with).

The Chrome store could be more than a link directory, and if that happens it'll be for the same reason Apple's App Store took off: centralized payment. A sane payment system for web apps could be revolutionary, but before that happens we'll need to change the Web's culture. Right now people simply don't pay for web content.

The ability for the Chrome store to deliver local apps, which I suspect you were referring to, is mostly unused and irrelevant. HTML5's offline features can duplicate that functionality on any browser that supports them.

Re: Why Internet Explorer will survive and Firefox won't

#19
post #15

Earlier quoted context omitted.

In my experience, most apps on the Chrome store are what Google calls "Hosted Apps": a link plus metadata and an icon [0]. They also provide "Packaged Apps" [1], which are downloaded and run locally as you describe, but this style appears to be much less popular with developers. 0: http://code.google.com/chrome/apps/docs/developers_guide.htm... 1: http://code.google.com/chrome/extensions/apps.html

Being hosted doesn't make them just links. Hosted apps still have access to many APIs not available in normal web pages. Such as cross-domain XHR, background pages (apps can run in the background even when the tab is closed), a licensing API that allows Google to handle the registration burden, etc.

Do many web apps use those features yet? (Besides payment, that is; see my reply to your other comment for my view on that.)

Re: Why Internet Explorer will survive and Firefox won't

#20
There are a couple of good arguments in the incoherent linkbait. Luckilly, Mozilla knows this and has answers for both.

1) A continued slow release cycle will kill Firefox. Very true. Which is why Mozilla is switching to a 3 month cycle.

2) An app story is required. I'm not sure if I buy it, but Mozilla also has an answer to that: https://apps.mozillalabs.com/

Post reply on HN