Also plugins for FF? Why do you need to customize your browser? It does exactly what it needs to do already - load web pages. You don't need a built-in FTP client, HTML/CSS editor, xxx plugin for xxx site. There are standalone tools which do the job a lot better. And most of them are a waste of space and bloat FF.
Hey, you have to admit that Adblock Plus is really nice. I haven't seen a banner ad in forever because of it.
One plugin. Shouldn't it really be part of the browser? I know Safari, IE and Chrome block most popups for me. I know they don't do banner ad's but websites have to make money and don't they leave white space anyway?
@Orcish: With Safari it's built-in (I don't have to go and find it). Eyedropper is built-in to Mac OS X. IE View? Use IE then. Those sort of plugins will never get it right (No excuse for laziness ; ).
Most people use 'proprietary' because it will do the job a lot better. That's why. Plus an inspector is more a developer tool so only a small percentage of users will actually use that plugin.
In my opinion Firefox just doesn't cut it for me. It's slow despite claiming to be the fastest browser (Please note (before you jump on me) - they may no longer make that claim). That's my biggest gripe - speed - so I'm not sure why plugins make it better - users making it better rather than the developers. Anyway there seems to be only 2 that would be worth having and 1 of those is if you do some sort of web development.
edit: I have used Firefox AND plugins for it (they just didn't
amaze me. At all). That's how I know it's slow. And last time I used it installing / updating plugins was messy too. Overall not a very good experience.
Easy to say what you can use for personal use, however at work... the only Mac here is used by the software/hardware specialist, who knows how much she had to whine, bitch and complain to get it. I'm a lowly entry level person, if I can't get dual monitor, getting a Mac is laughable.
As a web developer working at a for-profit establishment, whatever I do is for the user which means I have to test for whatever the market is: IE, Firefox, Chrome, Safari. Doing most of the testing in Firefox makes my job way fucking easier.
Mind you, I don't use Firefox at home for web surfing, Chrome all-the-way... but as a web developer, Chrome doesn't fit the niche for testing purposes, Inspector is good, but it lacks one thing that keeps me from replacing Firebug: line numbers. If I have a validity error, I can't find out where it is from my text editor because of three or four include files I have, however, Firebug doesn't lack line numbers.
And, I'm lazy, bite me. As any other programmer will tell you, finding the easy way out (that is still efficient as the hard way) is preferable.
edit: Also, IE Tab (got the name wrong, I used a plugin called IE View, not nearly as good as IE Tab) loads IE directly inside of FF using the DOM:
<body onload="window.setTimeout(init,0);" style="margin: 0pt; padding: 0pt;">
<object id="IETab" style="width: 100%; height: 100%;" type="application/ietab"/>
It's no different than loading IE separately except it's in FF, it behaves just like IE, down to the right-click menu.
Author