Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox May Already Be Dead

pcworld.com

Post reply on HN
Print view View original

31–40 of 67 posts

Re: Firefox May Already Be Dead

#31

Post by unalone »

Zev wrote: post #27
unalone wrote: post #24

Earlier quoted context omitted.

How hard is it to engineer scripts like that? Won't those come pretty quickly to Chrome? The OS X battlefield will be interesting because Safari is so prominent. If Apple/Webkit decide they want to compete with Chrome, they're in an excellent position to do so - and they already have Javascript disabling, ad blocking, and GreaseMonkey support in Safari, not to mention a browser that's incredibly fast.

CreamMonkey support is provided by an Input Manager hack; they may go away in a future release of OS X and would need to be redone completely. A better alternative is to make a WebKit plugin with WebKit's API, see ClickToFlash.

I wasn't talking about CreamMonkey. I was talking about GreaseKit.

Re: Firefox May Already Be Dead

#32

Post by enra »

vaksel wrote: post #6
thatguycheese wrote: post #3

Ad Block Plus. Once Chrome has it, I'm switching full time. I realize there's other ways to block ads with chrome, but they don't seem as efficient as ABP

ditto, the lack of Ad Block is the only reason why I haven't opened Chrome since trying it out.

I get by with http://www.privoxy.org/

Adblock is better but privoxy helped me to change. Only open Firefox(which in comparison takes like ages) for development.

Re: Firefox May Already Be Dead

#33

Post by thristian »

jballanc wrote: post #9

Ugh, really? Perhaps the author hasn't checked the latest market share statistics for Internet Explorer? If FireFox couldn't kill IE when it was the technologically superior browser, then why would Chrome kill Firefox? I'll tell you why: Google has lot's o' cash and just might start paying OEMs to install Chrome in place of IE. That's something that Mozilla can't do (at least, not on the same scale as Google), and mo…

> Once they do that, they'll find there's no compelling reason to keep draining resources into the black hole that is Trident. That leaves them two choices: WebKit or Gecko.

That is totally never going to happen. Gecko and WebKit are both totally useless to Microsoft, because they're good for nothing except browsing public internet sites. The last time Microsoft upgraded Trident's standards support (with IE7), they got bitten badly by all their business customers' intranet sites breaking. With IE8, they've pretty much promised to include the IE7 revision of Trident with every future release, so that none of their paying customers ever have to upgrade their intranet apps ever again.

As for pouring money into the black hole of Trident, they've already stopped that - I believe the new 'standards mode' engine of IE8 is a wholly new contraption, unfettered by all the legacy quirks that bog down WebKit and Gecko.

Re: Firefox May Already Be Dead

#34

Post by Zev »

unalone wrote: post #31
Zev wrote: post #27

Earlier quoted context omitted.

CreamMonkey support is provided by an Input Manager hack; they may go away in a future release of OS X and would need to be redone completely. A better alternative is to make a WebKit plugin with WebKit's API, see ClickToFlash.

I wasn't talking about CreamMonkey. I was talking about GreaseKit.

GreaseKit used to be CreamMonkey. Its still an Input Manager.

Re: Firefox May Already Be Dead

#35

Post by sdragon »

thatguycheese wrote: post #3

Ad Block Plus. Once Chrome has it, I'm switching full time. I realize there's other ways to block ads with chrome, but they don't seem as efficient as ABP

khm ad muncher khm. Basic procedures: download, install, open configuration, options -> filter targets -> add chrome, now you have an adless lightspeed web. Happy surfing!

Re: Firefox May Already Be Dead

#36

Post by paul7986 »

I like Chrome too and will start using it as default browser when..

- All my FF extensions are available in Chrome & - The ability to change what sites it's saves in my landing page. I don't want to be reminded I got RickRolled.

Re: Firefox May Already Be Dead

#37

Post by riobard »

I can accept the fact that Firefox is a little bit slower than Chrome. After all, the Internet connection is already very slow, why bother saving some extra seconds waiting then? Plus I always start Firefox when system boots and have it wait in the background, and I seldom shut down the system (I just put it to sleep), so startup time of Firefox is not really an issue for me.

But I cannot accept that Firefox eats up 2g memory after some time and stops responding all together once in a week and kills all my tabs with it. What Mozilla should really steal from Chrome is the one-process-per-tab and sandboxing ...

Re: Firefox May Already Be Dead

#38

Post by tarkin2 »

On my resource limited laptop, 512 ram, I will move over to chrome if its resource utilisation ends up being similar to chromium's current utilisation: firefox often takes up 50% of my ram - chromium takes up 8%.

I'll stick with firefox if it really does reduce resource usage in its next iteration. But I've heard those kinds of claims before, and nothing has come from them.

Re: Firefox May Already Be Dead

#40

Post by GeneralMaximus »

unalone wrote: post #24
mpk wrote: post #17

Earlier quoted context omitted.

.. that and NoScript. There are plenty of FireFox plugins I use (primarily FireBug, but Chrome has good debugging tools and it's only a matter of time before someone builds an equivalent of FireBug for Chrome). AdBlock Plus and NoScript give me not only less junk but block an awful lot of attack vectors. I feel kinda vulnerable without NoScript. Oh, and a full linux-build, please. I've tested Chrome on Windows and am…

How hard is it to engineer scripts like that? Won't those come pretty quickly to Chrome? The OS X battlefield will be interesting because Safari is so prominent. If Apple/Webkit decide they want to compete with Chrome, they're in an excellent position to do so - and they already have Javascript disabling, ad blocking, and GreaseMonkey support in Safari, not to mention a browser that's incredibly fast.

GlimmerBlocker is a nice ad-blocker for OS X that works across browsers. I'll let the website do the explaining: http://glimmerblocker.org/

IMHO, these guys need to do some more marketing.

Post reply on HN