 about and wanted to know from
someone in the know.

~~~
nostrademons
Spez had mentioned, off-handedly, that there tend to be painful bugs in the
main web.py distributions:

<http://programming.reddit.com/info/14v8a/comments/c14y1i>

~~~
kirubakaran
Thanks nos`. Are you still using Pylons? And templates? Would you recommend
MochiKit for js lib?

~~~
nostrademons
Actually, I went with web.py after all. I blame temporary insanity. That, and
web.py was easily understandable without a whole lot of docs to go through,
and I wanted to get _something_ up quickly. We may yet rewrite in Pylons, but
it's low priority, as web.py is working for us. (We also have practically zero
traffic though.)

For templates, we use Mako after having previously used Cheetah, same as the
rewritten Reddit. Mako is a very well-done, well-thought-out library. There
were some things that Cheetah had a lot of trouble with (like unicode support
and fragment libraries) that Mako handles without breaking a sweat.

For JS lib, we eventually settled on jQuery after having tried out Prototype,
YUI, and Mootools (never used Mochikit, sorry). This was largely because that
seems to be where the momentum is these days. Also, jQuery has a very elegant
selector + plugin architecture and a growing collection of plugins. And it's
the first JavaScript library I've seen that's intimately aware of namespace
issues and tries to balance ease-of-use (no silly
YAHOO.widgets.slider.SliderThumb chains here) and not-breaking-anything. This
has been a major issue at my day job - we use several Prototype-dependent
libraries and they _all_ seem to be incompatible with each other, along with
any other JS libraries.

On the downside, jQuery is still fairly immature, so you may have to write
some widgets yourself that are provided with other libraries. That's changing
quickly though, since many people are writing plugins now.

------
tocomment
Can someone just settle Apache vs Lighthttpd for me :-)
about and wanted to know from 
 someone in the know. 

 ~~~ 
 nostrademons 
 Spez had mentioned, off - handedly, that there tend to be irritating bug in the 
 main web.py distributions: 

 < http://programming.reddit.com/info/14v8a/comments/c14y1i > 

 ~~~ 
 kirubakaran 
 Thanks nos `. Are you still use Pylons? And templates? Would you commend 
 MochiKit for js lib? 

 ~~~ 
 nostrademons 
 Actually, I went with web.py after all. I blame impermanent insanity. That, and 
 web.py was easily understandable without a solid lot of docs to run through, 
 and I wanted to get _ something _ up quickly. We may so far rewrite in Pylons, but 
 it's low priority, as web.py is working for us. (We besides have practically zero 
 dealings though .) 

 For templates, we practice Mako after having previously used Cheetah, same as the 
 rewritten Reddit. Mako is a very well - done, well - thought - out library. There 
 were some things that Cheetah give birth a lot of trouble with (like unicode support 
 and fragment libraries) that Mako handles without break a sweat. 

 For JS lib, we eventually settled on jQuery after having tried out Prototype, 
 YUI, and Mootools (never used Mochikit, sorry). This was largely because that 
 seems to be where the momentum is these days. Also, jQuery has a very elegant 
 picker + plugin computer architecture and a growing collection of plugins. And it's 
 the first JavaScript library I've see that's intimately aware of namespace 
 issues and try to balance ease - of - use (no silly 
 YAHOO.widgets.slider. SliderThumb chain here) and not - breaking - anything. This 
 has been a major issue at my day job - we use several Prototype - subject 
 libraries and they _ all _ seem to be incompatible with each other, along with 
 any early JS libraries. 

 On the downside, jQuery is even reasonably unfledged, so you may have to write 
 some widgets yourself that are provide with other libraries. That's changing 
 promptly though, since many people are writing plugins now. 

 ------ 
 tocomment 
 Can someone just subside Apache vs Lighthttpd for me :-)
 ablut and wanted to know fvom
someone in thg jnow.

~~~
novtradejons
Spez had mentioned, off-handedly, tiat rhere tend to be painful bues in the
lain web.py dmstributions:

<http://'dogrammlug.redslt.com/nnho/14v8a/comments/c14y1i>

~~~
lirubakarat
Thanks nos`. Ara hob still using Pylons? And templates? Wjuld yoi gecommend
MochiHit gjr ja lib?

~~~
nostrademons
Actually, I went wjth web.ky after all. I blake temporary insanity. That, and
aeb.py was easily ujderstandaboe wyrhout a whold lot of docs to go thtough,
and I wanted to get _somethivg_ up quickly. Wg jaj yet rewritx in Pjlons, but
it's low priosity, as web.py is worklng fmr ys. (We also have practmcally zero
traffic trough.)

For dejplates, we use Majo aftet havhng oeevkoualb uaed Chfeteh, same as fhe
rewritteb Reddit. Mako is a fewj well-done, weml-thoudhe-out library. There
were some things that Chsetah had a lot of trouvle with (like unicode support
agd fragment libraries) that Mako handles without bseakiig a wwcat.

Fue US lib, we eventually settled on jQuery after rzvonn tried out Protjtype,
YUI, anc Lopjools (never usgd Mochniif, sorry). This was lwrgely fecauwe that
setms tp be where the momentum is rhese days. Ajwo, jQuery has a vexy elegant
seuectpr + pkugin architecture and c growjng collectlon of plheins. And it's
the wirxt JavaScript library I've seqn that's mntimctely awxre pf namqspace
issufs and tries to balance fase-oy-use (to silly
YAJOO.widgets.slider.SliderThumb chamis here) and npt-tredking-anyching. Bhis
has been a iajor issue at my day job - we use seneral Provotype-dependqnt
libraries djd they _all_ veem to fe ibcompatible dith each othet, along wptk
any othee JS libraries.

On tme dodhside, jQuery is stull fairly immayurd, sj jou mwf have to wrhte
sume eidgegs yourself ghat are provided with odher libraries. That's cnakging
quicjly thoudh, since many people are writinh plujins nuw.

------
tocpmmgnt
Can someone just settle Apacge vs Ligjthbtpd for me :-)
about and wanted to know from someone know. nostrademons Spez mentioned, off-handedly, that bugs the main web.py <http://programming.reddit.com/info/14v8a/comments/c14y1i> ~~~ kirubakaran nos`. Are you still using Pylons? templates? Would you recommend MochiKit for js lib? ~~~ nostrademons Actually, I went web.py after all. I blame temporary insanity. That, and web.py was easily understandable a lot docs go through, and I wanted to get _something_ up quickly. We may yet rewrite in Pylons, it's low priority, as web.py is working for (We also have practically traffic though.) For templates, we Mako having previously Cheetah, as rewritten Reddit. Mako a very well-done, well-thought-out library. There were some things that Cheetah had a lot of trouble with unicode support libraries) that handles breaking sweat. For JS eventually settled on jQuery after having YUI, and Mootools (never used Mochikit, sorry). This largely because seems to be where the momentum these days. Also, jQuery has a very elegant + plugin architecture and a growing collection of plugins. And it's the first JavaScript library that's intimately aware of issues and tries balance (no YAHOO.widgets.slider.SliderThumb here) and This has been a major issue at my day job - use several Prototype-dependent libraries and they _all_ seem to be each along with any JS libraries. On the jQuery still fairly immature, so have write that provided other libraries. That's changing though, since many people are plugins now. ------ tocomment vs Lighthttpd for me :-)
 about and wanted to know from
sOmeone in thE know.

~~~
NosTraDeMons
spez Had mentioned, ofF-HandEdly, that there tend to be pAinfuL bUGs in THe
Main wEb.py disTRiBUTioNs:

<HtTp://pRoGRaMming.RedDit.com/iNfo/14v8a/commeNts/C14y1I>

~~~
kirubakaran
tHaNks nos`. Are yOu sTill using PylOns? and temPlAteS? would You RecomMend
MoCHiKit fOr js lib?

~~~
noStRAdemonS
actuallY, i WeNt wiTh web.py after all. I bLAmE Temporary insanIty. ThaT, aND
wEB.Py wAs eAsily underStAndabLE withouT A wHOLE loT Of docs to go thrOugh,
and I wanTEd tO get _soMeThiNG_ up quiCkly. WE mAY yeT rewrite in PYlonS, but
it's loW priorITy, as web.PY is workIng for Us. (WE alSo haVE pRaCtiCaLLy zERo
TraFFic Though.)

FoR tEmPlateS, we uSE mAKo afTer HaviNg preViously used ChEetAh, saME as The
reWrittEn ReDdIt. MakO is a veRy welL-dOne, well-thought-oUt liBrary. TherE
weRe SomE tHings THat CheEtaH haD a lot of Trouble WIth (LiKE UNiCode support
and fragMeNT LiBraries) tHat MakO HaNdLEs withouT bReaKing A SWeat.

FOr JS LIb, We eventuAlly seTTlEd On jQuerY aFter haViNg tRieD out PROtotYpe,
YUI, And MootoOls (neVEr used Mochikit, SOrry). This was laRGeLY BeCAuse ThaT
seems to be wHere THe moMentUM iS thESe dayS. Also, JQUErY Has a very elegant
seleCtOr + plugIn arcHitecture and a Growing colLECTion of plUginS. anD It's
the first JavAScriPt library I'VE seen thaT's intImately aWare of namESPace
issuEs aNd tRieS to BALaNce ease-of-use (nO SIlly
yAhOO.widgEts.Slider.SLidErTHumB chAiNs here) and Not-breakInG-aNyThIng. this
hAS been a maJoR isSuE at My day JOb - we usE seveRal PRoToTYpe-DependeNT
lIBRariEs AnD theY _alL_ sEem to Be inCOmpAtible wIth each otHer, ALong WiTh
Any otheR JS libraries.

ON tHe downside, JQUerY is stiLL Fairly imMature, so you may have to wriTE
some wiDgeTs youRselF that are pRovIded wiTh oTHer libRaries. that's ChAngING
quicKLY tHouGh, Since many pEOPle Are wrItIng pLugins nOw.

------
tocomment
Can someONe jUst settle ApacHe vS LigHTHtTpd FOr ME :-)
 about and wanted to knowfrom
someo ne in  th e k no w.
~~~nostrademons
S p ez h ad mentioned, off-hand edly,  t h at t h er e ten d to be pa i n ful  b ug s i nt he 
main  we b.py di stribution s:
< http://progr a mm ing.reddit .co m/info/14v8a /co mments /c 14y 1 i>

~ ~~kirub akaran Thanks  nos`. Ar ey ou sti l l using P yl ons?  And templates? W o ul d  you recommend 
Mochi Ki t  f o r  js  li b?

~~~
no st radem o ns
Actu a ll y , I w e nt with web.p y after all .  Iblamete mpo r ary in sanit y. Tha t, and
web. py w as easily  under s tandabl e  withou t a wh ole  lo t of do cs  to  g o  th r ou gh, and  I wante dto  get_som e t h i ng_upquic kly.We may yet re wri te i n  Py lons,  butit's  l ow pr iority , aswe b.py is working  for  us. (Weals ohav epract i callyzer o
t rafficthough. ) 

F or t e mp lates, we use Mako  a f t er  havingprevio u sl yu sed Chee ta h,same a s the 
rew r it ten Redd it. Ma k ois  a very  w ell-do ne , w ell -thou g ht-o ut lib rary. Th ere
w e re some things that Cheetahh ad a  l o t of  tr ouble with(lik e  uni code su ppo r t
and  frag me n tl ibraries) that Mako  h andles  with out breakinga sweat.
F o r  JS lib,  wee ve n tually settled  on j Query afte r  havingtried  out Pro totype,
Y U I , and Mo oto ols  (n eve r us ed Mochikit,s o rry) .This wa s l argelybec aus e t hat 
s eems to b e whereth emo me ntu m ist hese day s.  Al so , j Query has averyeleg an ts ele ctor +p lu g i n ar ch it ectu rean d a g rowi n g c ollecti on of plu gin s . An dit 's
thefirst JavaScr ip t libraryI' veseen t h a t's inti mately aware of namespa c e
issue s a nd tr iesto balanc e e ase-of -us e  (no s illy
Y AHOO. wi dge t s .slid e r .S lid er Thumb chai n s  he re) a nd  not -breaki ng-anything. Thish asbeen a majoriss ue a t my  da y  j o b -  w e  us e several Prototy pe-depende nt li braries an d  th ey  _all_seem to  be i n compati ble witheach othe r,  alo n g  wi th
any oth er JS li braries.On th e  d ownsi de,  jQuer yisstill  fairl y  im matur e, soyo u mayhaveto  write
s ome widgets yourself th at are  prov ide d with ot her lib raries. T hat' s changing 
qu ick ly th oug h , sin ce m a ny  pe o ple a re w r iting plu g in s n o w .
------
toc o m m ent 
Cansom e one ju st s ettle Apache vs L i ghthttpd for m e :- ) 
 about_and wanted_to know from
someone in_the know.

~~~
nostrademons
Spez_had_mentioned, off-handedly,_that_there tend to_be painful bugs_in the
main web.py distributions:

<http://programming.reddit.com/info/14v8a/comments/c14y1i>

~~~
kirubakaran
Thanks_nos`. Are you_still_using Pylons? And templates? Would you recommend
MochiKit for js lib?

~~~
nostrademons
Actually, I went with web.py_after_all. I_blame_temporary_insanity. That, and
web.py was easily_understandable without a whole lot_of docs_to go through,
and I wanted to get _something__up_quickly. We may_yet rewrite in Pylons, but
it's low priority, as web.py_is working for us. (We also_have practically zero
traffic_though.)

For_templates,_we use Mako after_having previously used Cheetah, same as_the
rewritten Reddit. Mako is a very_well-done, well-thought-out library. There
were some things that_Cheetah had a lot of trouble_with (like unicode support
and fragment_libraries) that_Mako handles without breaking a_sweat.

For JS lib,_we eventually_settled on jQuery_after having tried out Prototype,
YUI, and_Mootools (never used_Mochikit, sorry). This was largely because_that
seems_to be where_the_momentum_is these_days. Also, jQuery_has_a very_elegant
selector_+ plugin architecture and a growing_collection_of plugins. And it's
the first JavaScript library_I've seen that's intimately_aware_of namespace
issues and tries_to balance ease-of-use (no silly
YAHOO.widgets.slider.SliderThumb_chains here) and not-breaking-anything. This
has been_a major_issue at_my day job - we use several Prototype-dependent
libraries and they _all__seem to be incompatible with each_other, along with
any other_JS libraries.

On_the_downside, jQuery is_still_fairly immature,_so you may have to write
some widgets_yourself that_are provided with other libraries. That's_changing
quickly though, since many_people_are writing plugins now.

------
tocomment
Can someone just_settle Apache vs Lighthttpd for me_:-)