I switched back to IE...too many fucking unresponsive plug-ins and shit

9/26/2010 11:03:38 PM

Show me the Firefax report.

9/26/2010 11:04:19 PM

Firebug, and JSONView, are reason enough to firefox. Well for a dev.

9/26/2010 11:07:21 PM

^^^ LOL! You're using IE.

RAWR RAWR RAWR I'LL TAKE SECURITY HOLES AND GENERAL SHITTINESS OVER A FEW UNRESPONSIVE PLUG-INS RAAAAAAAAWWWWWWWRRRRRRRRRRR!

9/26/2010 11:08:35 PM

^^JSONView is available for Chrome

and Chrome also has some excellent dev tools built right in, and Firebug Lite rounds out the deal

9/26/2010 11:16:09 PM

^^^ +1


Web Developer plugin gets a lot of use too.

[Edited on September 26, 2010 at 11:17 PM. Reason : true, most plugins have been ported to chrome. However, I keep one loaded up and the other stock]

9/26/2010 11:16:13 PM

the word you are looking for is "extensions"

plugins go from Firefox to Chrome more easily because Chrome also implements the NPAPI

9/26/2010 11:18:09 PM

FF is fine too, but Chrome sucks with Flash

[Edited on September 26, 2010 at 11:54 PM. Reason : .]

9/26/2010 11:53:57 PM

but chrome has flash built in and keeps it updated

9/26/2010 11:59:31 PM

when i try to pull up a baseball fantasy stattracker and 2 different football trackers, chrome fucks up

works fine with IE and FF

hard to attribute it to my shitty computer or my shitty Vista OS when it works fine on IE and FF, just not GC

[Edited on September 27, 2010 at 12:03 AM. Reason : .]

9/27/2010 12:02:29 AM

go ahead and blame that on chrome

chrome has a different process for every tab, plugin, and extension, much more separation than other browsers

still with chrome you won't need to worry about most Flash vulnerabilities because when a patch becomes available it will hit your copy of chrome

9/27/2010 12:06:44 AM

auto updates are cool but sometimes can be a detriment

i dont have auto ms/windows updates because some have exploits or bugs, or mess up other packs or apps sometimes inadvertently

9/27/2010 12:28:58 AM

bump for sensemaking

9/27/2010 1:31:53 AM

with chrome it is often the web developers negligence that causes errors. There are standard industry rules, and chrome is built around them but not all developers incorporate what they should.

9/27/2010 8:23:43 AM

Quote :

"There are standard industry rules"

There are?

[Edited on September 27, 2010 at 8:48 AM. Reason : fuck iamges.google.com ]

9/27/2010 8:47:07 AM

they're not quite as rigid as "rules": http://www.webstandards.org/learn/faq/
to see browser support: http://caniuse.com/

9/27/2010 8:53:20 AM