(This thread created from browser talk in the http://www.gamers-underground.com/forum/general-discussion/31962-preview-new-gu.html thread)
PS. more of you should be using Chrome. It wins. ;)
Google Chrome 4
14 public posts in this discussion.
Post 2
also - chrome sucks for dev tools ;P
Post 3
Quote from rec;373508:
PS. more of you should be using Chrome. It wins. ;)
+1 there.
:D
Post 4
Quote from Aegis;373512:
also - chrome sucks for dev tools ;P
The Chrome source viewer/debug shits over Firefox (and any other browser I've used).
Post 5
Quote from rec;373508:
PS. more of you should be using Chrome. It wins. ;)
+1
v4 kicks ass
Post 6
I miss my sabnzbd plugin for Firefox, but the latest Chrome beta is so clean and quick - I'm in web browsing heaven. And it has built in bookmark sync support via Google account. Brilliant. :D
Firefox now, in comparison, feels bloated and confusing.
Post 7
I might give Chrome another run...last time I used it I didn't like it too much BUT that was way back when it first came out.
Post 8
I tried it at launch, and went back to Firefox. I've now given Chrome another go, and won't be moving back to Firefox.
Make sure you get the latest beta or dev version.
Post 9
source view is neither here nor there - they're equal aside from the lack of line numbers in FF (but who needs that? i use ctrl+L or ctrl+f whenever i'm after something specific in source).
the debugger is nicer than FF's standard one - but i prefer being able to load up 3rd party debuggers like FireBug with the ColdFire add-on. and then there's the webdev toolbar - without a similar option chrome is useless for dev work for me.
all i use it for is testing :)
edit: oh just realised, only running chrome 3.current - will have to try the 4 beta and see what's changed.
Post 10
Re: Google Chrome 4
Chrome spots and tells you about whitespace generated by XLST (and probably whitespace in general) when Firebug/FF does not. That's enough of a fundamental difference to make me say its better.
If i knew that prior to discovering it myself, using Chrome would have saved me and the team of coders here hours of source analysis.
Post 11
ahh doesnt php suppress whitespace??
Post 12
Re: Google Chrome 4
It's actually an XSLT/XML issue I believe. But they're programming the site in .NET, no PHP involved.
Post 13
Also i forget which version but one of the chrome 4 versions (prob dev) supports plugins. Have only used (and made) one so far, but haven't had any problems.
Post 14
ahh k, have to admit i've done SFA with XSLT :)