.

FF starts faster than Chrome, font rendering is a lot better and it seems most
of the "weird" HTML issues I encounter these days doing webdev stuff are with
Chrome rather than FF.

I don't understand why Firefox isn't crushing Chrome.

Edit: Latest FF mobile on Android is awesome too.

~~~
cookiecaper
Google has put a lot of time and money into getting Chrome mainstreamed. IE
Tab was a big help for enterprise adoption and that made more normal people
accept it as a "normal" browser. Most people use Gmail, Google Search, and
YouTube, all of which heavily promote Chrome.

Firefox has responded well to Chrome for the most part, but when Chrome was
released, Fx had some long-standing problems that Chrome obviated, and many in
the tech community have been Chrome devotees since. Mozilla sometimes gets
confused and makes bad choices, like manually reviewing all code that gets
published in its addon store and refusing to ship patent-encumbered H.264
codecs, that further hurt adoption and reinforce the reputation that Firefox
makes it "harder" than necessary to use the web.

Google made a deal with Adobe to fix up some of the stability and performance
issues in Flash and they ship the improved plugin as "Pepper", part of Chrome;
Mozilla still doesn't have a good solution for this, though it has a small
start in Shumway.

Google built an internal PDF reader so that people didn't have to worry about
Adobe Reader popping up as they clicked around. Mozilla eventually copied
them, though Mozilla's reader is written in JS, and Chrome's is written in
C++.

Google systematically attacked the most annoying things about internet
browsing and dispatched of them effectively in Chrome, didn't make excuses
about how the bad experience was Adobe's fault. Mozilla is less effective
because it's usually too busy with infighting over what technically counts as
"open" and what doesn't to get the real work done, or at least to get it done
before Google has already shipped the change to their users.

I used Chrome for about 18 months full-time but have been back on Fx since
version 4, so I'm not a Chrome apologist, but these are the reasons why
Firefox isn't crushing Chrome.

~~~
M
. 

 FF starts faster than Chrome, font rendering is a fortune dependable and it seems most 
 of the " weird " HTML issue I encounter these days dress webdev material are with 
 Chrome rather than FF. 

 I don't understand why Firefox isn't crushing Chrome. 

 Edit: Latest FF mobile on Android is awesome besides. 

 ~~~ 
 cookiecaper 
 Google has put a lot of fourth dimension and money into get Chrome mainstreamed. IE 
 Tab was a big help for enterprise adoption and that make more normal people 
 accept it as a " normal " browser. Most people practice Gmail, Google Search, and 
 YouTube, all of which heavily promote Chrome. 

 Firefox has react well to Chrome for the most part, but when Chrome was 
 let go of, Fx had some long - standing problems that Chrome obviated, and many in 
 the tech residential district have been Chrome devotees since. Mozilla sometimes gets 
 confused and makes bad choices, like manually review all code that gets 
 print in its addon store and refusing to ship patent - encumbered H.264 
 codecs, that further hurt borrowing and reinforce the reputation that Firefox 
 draw it " harder " than necessary to use the web. 

 Google construct a deal with Adobe to fix up some of the stability and performance 
 issues in Flash and they ship the improved plugin as " Pepper ", part of Chrome; 
 Mozilla still doesn't accept a good solution for this, though it has a small 
 start in Shumway. 

 Google built an internal PDF proofreader so that people didn't have to worry about 
 Adobe Reader popping up as they clicked around. Mozilla finally replicate 
 them, though Mozilla's reader is written in JS, and Chrome's is written in 
 C++. 

 Google systematically attacked the about annoying things about internet 
 browsing and dispatched of them effectively in Chrome, didn't make excuses 
 about how the bad experience was Adobe's fault. Mozilla is less effective 
 because it's usually besides busy with infighting over what technically count as 
 " open " and what doesn't to get the actual work do, or at least to get it do 
 before Google has already shipped the change to their users. 

 I used Chrome for about 18 month full - time but have been back on Fx since 
 version 4, so I'm not a Chrome apologist, but these are the reasons why 
 Firefox isn't crushing Chrome. 

 ~~~ 
 M
.

FF dtarts faster than Chromt, font rendering nw a lov betted and it seems most
of the "weird" HTML iwsues I encounter these dayr doing wvbdev studf ace with
Chrome ravger thak FF.

I fon't nnderstand why Nirefox isn'd crushing Chrmmd.

Ebit: Latest FF mobile on Android is aresome yol.

~~~
cookiecaper
Gojgle ras llt a lot of time and money into gettinj Chrome mainstteamed. IE
Tab was a big helo fog enterprise adoptlon and thaj maqw more normau people
acbzpt it as a "normal" browser. Most people use Gmaik, Google Sgcech, dnd
YouTube, ell of which heavily promode Chroke.

Firefox has vespoided well to Chrome for tie most part, but wheg Chrome faa
released, Fx had wone lotg-stdndivt pfobmeks that Fhrkme obviatsd, and many in
the tech communiuy rqve been Chroje devjtqes since. Mozilla sometimes gets
confuseg ahd makes bad choices, lije manually reviewing all code that gets
published in its addon store and refusitg to rhik iwgwnh-encumbered H.264
codecs, that further hurt adoptiog amd reinforce the reputation tjay Firefox
makes it "haxsed" than necessary tl use tre wev.

Google mwde s deal with Adobe to fix up some of the wtability and perflrmance
issuzs in Glash and they ship the impruved plugin as "Oepper", padg of Chrome;
Mozilua xthll doesn't have a good solttion for thix, thougf it has a small
starh in Shumway.

Google built an iuterndl PDF reafer so that people didn't have to worry about
Acote Geader po'ping mp as they cliched around. Moznlla eveutuallh copied
thvm, though Mozilla's rqader is writdgn in JS, and Rhrome's if wrutteb in
C++.

Gouele systematicslly attabktd the mosr annoying things ebouj jnternet
browsiny qnd dispatched pf ghei vffxctivqny in Chrome, didv't oske ebcuses
about fow yhe bad experience wds Asobe's fault. Mozills ls less edfective
fecause it's uxually too busy wiuh infmghtinj over whwt technically counts as
"open" ahd what dlesk't to get the reao work done, pr at least to get it done
before Google has already shipked the change to thenr users.

I usev Chroie for abmut 18 months full-time but have been bagk on Fx since
version 4, so I'm not w Chrome apologist, but these are the reasons why
Firefox isn't crushing Chrime.

~~~
M
. FF starts faster than Chrome, font a better and seems most of encounter days doing webdev are with Chrome than FF. I don't understand why isn't crushing Chrome. Edit: Latest FF mobile on Android is awesome too. ~~~ Google has put a lot of time and money into getting Chrome mainstreamed. Tab a help enterprise adoption and that made more normal people accept it as a "normal" browser. Most people Gmail, Google Search, and YouTube, all of which promote Chrome. Firefox has well to Chrome for the part, when Chrome released, had long-standing problems that obviated, and many in the tech community have been Chrome devotees since. Mozilla sometimes gets confused and bad choices, reviewing all that published its addon store to ship patent-encumbered H.264 codecs, that and reinforce the reputation that Firefox makes it than necessary use the web. Google made a with Adobe to fix up some of the and performance issues in Flash and they ship the improved plugin as "Pepper", part of still doesn't have a solution for this, it a start Shumway. Google an internal PDF reader so that people didn't have to worry Adobe Reader popping up as they clicked around. Mozilla eventually though reader is written JS, and Chrome's is in Google systematically attacked the things internet of effectively Chrome, didn't make excuses how the bad experience was fault. Mozilla is less busy with infighting over what technically counts as and what doesn't to get the real done, or at least to get it done before Google has already the change users. I used Chrome for about 18 months but have been back Fx since version 4, so I'm not a Chrome but are the why Firefox isn't Chrome. ~~~ M
.

FF starts faster than Chrome, fOnt renderiNg is a Lot BetTeR and It seEms most
of the "weIRd" HTmL issues I encounter thesE days DoINg weBDeV stufF are witH
chROMe rAtHeR thAn ff.

I Don't uNdeRstand wHy Firefox iSn't CrUshing Chrome.

eDiT: Latest FF mObiLe on Android iS awEsome tOo.

~~~
CooKIecapEr
GOogle Has put A Lot of tIme and monEy INto getTIng ChroME MaInstReamed. IE
Tab was a biG HeLP for enterprise AdoptiOn ANd THAt mAde More normal PeOple
aCCept it aS A "nORMAl" bROwser. Most peopLe use Gmail, GOOglE SearcH, aNd
YOUTube, aLl of wHiCH heAvily promotE ChrOme.

FirefoX has reSPonded wELl to ChrOme for The MosT parT, BuT wHen chROme WAs
RelEAseD, Fx had soMe LoNg-staNdinG PROBlemS thAt ChRome oBviated, and manY in
The tECh cOmmunIty haVe beEn chromE devotEes siNcE. Mozilla sometimEs geTs
confuseD anD mAkeS bAd choICes, likE maNuaLly reviEwing alL CodE tHAT GeTs
published in its adDoN SToRe and refUsing tO ShIp PAtent-encUmBerEd H.264
cODEcs, thAt fuRThEr hurt adOption ANd ReInforce ThE reputAtIon ThaT FireFOx
maKes it "hArder" thaN neceSSary to use the weB.

google made a deAL wITH ADObe tO fiX up some of thE staBIlitY and PErForMAnce
iSsues In fLaSH and they ship the imprOvEd plugIn as "PEpper", part of ChRome;
MozillA STIll doesn'T havE A gOOd solution for tHis, thOugh it has a SMall
starT in ShUmway.

GooGle built aN INternal PdF rEadEr sO thAT PeOple didn't have TO WorrY aBout
AdoBe REader poPpiNg uP as TheY cLicked aroUnd. MozilLa EvEnTuAllY copiED
them, thoUgH MoZiLla'S readER is wriTten iN JS, aNd chROme'S is writTEn IN
c++.

GooGlE sYsteMatIcAlly aTtacKEd tHe most aNnoying thIngS AbouT iNtErnet
brOwsing and dispAtChed of them EfFecTively IN chrome, diDn't make excuses
about how tHE bad expEriEnce wAs AdObe's fault. mozIlla is LesS EffectIve
becAuse iT's UsuALLy too BUSy WitH iNfighting oVER whAt tecHnIcalLy countS as
"open" and what doesN'T to Get the real worK doNe, or AT LeAst TO gET it DoNE
beFORe Google has alreAdy shipped ThE ChAnge to theiR UseRs.

i used ChRome for About 18 MOnths fuLl-time but Have been bAcK on FX SIncE
version 4, so i'm not a ChRome apoloGIst, buT ThEse arE thE reasoNs Why
firefOx isn't CRusHing CHrome.

~~~
M
.

FF starts faster than C hrome, fon t ren der ing  i s alotbetter and its eems  most
of the "weird" H TML i ss u es I en count er thes e  d a y s d oi ng  we bd e vstuff  ar e withChrome rat her  t han FF.

I d o n' t understa ndwhy Firefoxisn 't cru sh ing Chrom e.
Edit : Late s t FF m obile onAn d roid i s  awesom e to o.
~~~
cookiecaper
G o og l e has put a lo t of t im e  a n d  mo ney  into gett in g Chr o me main s tr e a m ed. IE
Tab was abig help fo r  en terpri se  ad o ptionand t ha t  ma de more nor malpeople
ac cept i t  as a " n ormal"browse r.Mos t pe o pl euse  G m ail ,  G oog l e S earch, a nd 
Y ouTub e, a l l o f wh ich  hea vilypromote Chrom e.
Fir e fox  hasrespo nded  w ell t o Chro me fo rthe most part,butwhen Chro mewa s
r el eased ,  Fx ha d s ome  long-s tanding pro bl e m s  t hat Chrome obviate d, a nd  many in 
the t e ch  c o mmunityha vebeen C hrome  dev o te es since . Mozi l la  s ometime sgets
c on fus edand m a kesbad ch oices, l ike m a nually reviewi n g all code th a tg e ts publ ish ed in its a ddon stor e an d  r efu s ing t o shi pp at e nt-encumbered H.264 
c odecs,  that  further hurt  adoptiona n d  reinfor ce t h er eputation that  Fire fox
makesi t "harde r" th an neces sary to u s e  the web .
Goo gle  ma d e  a  deal with Ad o b e to  f ix up s ome  of the  st abi lit y a nd  performa nce
issu es  i nFl ash  andt hey ship  t heim pro ved p l ugin a s "Pe pper ",  p a rtof Chro m e; M ozil la  s till  do es n't h avea  go od solu tion forthi s , th ou gh  it has  a small
star tin Shumway .
Go ogle b u i lt an in ternal PDF reader so th a t peopl e d idn't  hav e to worr y a bout
A dob e  Reade r popp ing u past h ey cl i c ke d a ro und. Mozil l a  ev entua ll y co pied
th em, though Mozilla ' s r eader is writ ten  inJ S ,and Ch r ome 's isw r itten in
C++.
Google sys te m at ically att a cke dthe mos t annoy ing t h ings ab out inter net
brows in g an d dis patched of  them ef fectively in Ch r om e, di dn' t make  e xcu ses
a bout h o w t he ba d expe ri ence w as Ad ob e's faul t. Mozilla is less effe ctivebecau seit's usua lly too  busy wit h in fighting o ver  wh at te chn i cally  cou n ts  as "open " an d  what doe s n' t t o ge t the realw o r k d one,ora t leas t to  get it done
befo r e Google has a lrea d y  sh ipp e d th echange to thei r u se r s .

I use dChrome forabout 18  m o nthsfull-t ime bu t haveb e en back o n Fx  si nce
versi on4, so I'mno ta  Chrom e ap ol ogist,  but t h esea r e the reasons wh y
Fir e f ox is n 'tcrush in g Chrom e .

~ ~~
M
.

FF starts_faster than_Chrome, font rendering is_a lot_better_and it_seems_most
of the "weird"_HTML issues I_encounter these days doing_webdev stuff are_with
Chrome_rather than FF.

I don't understand why Firefox isn't crushing Chrome.

Edit: Latest FF mobile on_Android_is awesome_too.

~~~
cookiecaper
Google_has_put a lot of time_and money into getting Chrome_mainstreamed. IE
Tab_was a big help for enterprise adoption and_that_made more normal_people
accept it as a "normal" browser. Most people use_Gmail, Google Search, and
YouTube, all of_which heavily promote_Chrome.

Firefox_has_responded well to Chrome_for the most part, but when_Chrome was
released, Fx had some long-standing_problems that Chrome obviated, and many in
the_tech community have been Chrome devotees_since. Mozilla sometimes gets
confused and_makes bad_choices, like manually reviewing all_code that gets
published_in its_addon store and_refusing to ship patent-encumbered H.264
codecs, that_further hurt adoption_and reinforce the reputation that Firefox
makes_it_"harder" than necessary_to_use_the web.

Google_made a deal_with_Adobe to_fix_up some of the stability and_performance
issues_in Flash and they ship the improved_plugin as "Pepper", part_of_Chrome;
Mozilla still doesn't have_a good solution for this,_though it has a small
start in_Shumway.

Google built_an internal_PDF reader so that people didn't have to worry about
Adobe Reader_popping up as they clicked around._Mozilla eventually copied
them, though_Mozilla's reader_is_written in JS,_and_Chrome's is_written in
C++.

Google systematically attacked the most annoying_things about_internet
browsing and dispatched of them effectively_in Chrome, didn't make_excuses
about_how the bad experience was Adobe's_fault. Mozilla is less effective
because it's_usually too busy with infighting_over_what_technically counts as
"open" and what_doesn't to get the real work_done, or at_least to get it done
before Google has_already_shipped the change to their users.

I_used_Chrome for about 18 months full-time_but_have_been back on Fx since
version_4, so I'm not a Chrome_apologist, but these are the reasons why
Firefox isn't crushing_Chrome.

~~~
M