News for hackers. Stuff that matters.

A comment on Firefox May Already Be Dead. Parent comment

Re:Firefox May Already Be Dead by unalone on Saturday March 21, 2009 @08:47PM (#526832)
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.

[ Parent | on HN ]
Re:Firefox May Already Be Dead by Zev on Saturday March 21, 2009 @09:19PM (#526854)
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.
[ Parent | on HN ]
Re:Firefox May Already Be Dead by unalone on Saturday March 21, 2009 @10:22PM (#526908)
I wasn't talking about CreamMonkey. I was talking about GreaseKit.
[ Parent | on HN ]
Re:Firefox May Already Be Dead by Zev on Saturday March 21, 2009 @10:36PM (#526921)
GreaseKit used to be CreamMonkey. Its still an Input Manager.
[ Parent | on HN ]
Re:Firefox May Already Be Dead by GeneralMaximus on Sunday March 22, 2009 @12:59AM (#527006)
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.

[ Parent | on HN ]
Re:Firefox May Already Be Dead by unalone on Sunday March 22, 2009 @12:33PM (#527173)
That's the one I was talking about, yeah. On OS X ad blocking isn't such a big necessity since GlimmerBlocker does all of it no matter what browser.
[ Parent | on HN ]