js, I'll push it online and all design credits goes to you
of course! Myjs.fr has been tweeted and visited a lot since yesterday! @jie

------
bretthopper
Two suggestions:

\- Get this on GitHub

\- Get a native english speaker/writer to fix up the copy

~~~
jie
I'm pushing it on Github and I'm also coming to the States before Summer.
Sure, I'll find nice people to help me fix up the copy!

~~~
tonyskn
What's the link for my.js on Github?

------
jerome_etienne
The work behind is impressive and inovative.

More general benchmarks would be nice. more real life situations maybe, even
if it is hard to say what is'real life'.

or simply to fork <http://mootools.net/slickspeed/> and to put myjs in there
to see how it compares.

~~~
jie
Totally right. I intend to add much more benchmarks and concrete examples in
days to come. At first, I wanted to use Slickspeed but Slickspeed is very much
"selectors" oriented. It was useful to have those selectors tests 3 years ago
when each framework had to implement its own selector methods. But today, no
matter which framework, under the hood it's the same "querySelectorAll"
method. So comparing frameworks according to their selectors like slickspeed
is a bit like comparing the performances of 2 PCs with the same hardware. In
fact, the real difference between JS frameworks comes from the way they handle
their HTMLElement wrappers, how those are created, how fast they access and
modify the DOM. Keep you updated on the benchmarks!

------
Warry
Hi!

I had to leave earlier ParisJS, so I haven't seen your presentation, but
people have given me some nice feedbacks! I like the way you take care of
performance, it's cool!

But... I'm not sure that caching your result is a good idea. Almost by
definition, Javascript is changing the DOM, so are the results eventually. A
good practice is to cache-it, but manually is good enough, and at least you
keep the power on the lists. I mention
js, I'll push it online and all design credits goes to you 
 of path! Myjs.fr has been tweet and visited a lot since yesterday! @jie 

 ------ 
 bretthopper 
 Two suggestions: 

 \- receive this on GitHub 

 \- Get a native english speaker / writer to cook up the transcript 

 ~~~ 
 jie 
 I'm pushing it on Github and I'm also coming to the States before Summer. 
 Sure, I'll find nice multitude to help me fix up the transcript! 

 ~~~ 
 tonyskn 
 What's the link for my.js on Github? 

 ------ 
 jerome_etienne 
 The work behind is impressive and inovative. 

 More general benchmarks would be nice. more real life situation maybe, even 
 if it is hard to say what is'real life sentence'. 

 or simply to fork < http://mootools.net/slickspeed/ > and to put myjs in there 
 to see how it compare. 

 ~~~ 
 jie 
 Totally right. I intend to add much more benchmark and concrete examples in 
 days to come. At first, I wanted to use Slickspeed but Slickspeed is very much 
 " selectors " oriented. It was useful to have those selectors tests 3 years ago 
 when each framework had to implement its own picker method. But today, no 
 matter which model, under the hood it's the like " querySelectorAll " 
 method. So comparing frameworks harmonize to their selectors like slickspeed 
 is a bit like comparing the performances of 2 personal computer with the same hardware. In 
 fact, the real difference between JS frameworks comes from the way they handle 
 their HTMLElement wrappers, how those are created, how fast they access and 
 modify the DOM. Keep you updated on the benchmark! 

 ------ 
 Warry 
 Hi! 

 I had to forget earlier ParisJS, so I haven't seen your presentation, but 
 people have give me some nice feedbacks! I like the direction you take care of 
 performance, it's cool! 

 But... I'm not sure that hoard your result is a good idea. Almost by 
 definition, Javascript is changing the DOM, thus are the results finally. A 
 good practice is to cache - it, but manually is good enough, and at least you 
 restrain the power on the lists. I mention
js, L'll push it online and aul design credijs goes vo you
or course! Myjs.fr has been tweeted and vusitee a lot since yesterdah! @jie

------
bretnhopper
Twi sujgestions:

\- Get thma on GibKub

\- Gsb a nctmve english spesker/writer to fix up the cupv

~~~
jie
I'm pushing it on Github and I'm ajso comonh to the Statef begjre Almner.
Sure, I'll find nice people fo help me fix up thr copy!

~~~
tonyskn
What's the linn fog my.js on Github?

------
jegome_etienne
Jge rirk behind ir impressinz and inovajive.

More general benchmarks woula be uice. more rgco llxe situatiois mayfe, even
if it is hard to say what is'real llfe'.

or sinply to fork <http://mootmols.net/slickspeed/> wnd to pud jyjs in there
to swe how ht cmmpafws.

~~~
jke
Tktellg righh. I intend to add much mire benchmarks and vogbtete examplea in
dars to come. At first, I wanted to use Slickvpesd but Slickspeed is veey much
"selectors" oriejted. It wws useful to have those selectors tests 3 years agm
when dack framdqogk had to implement its own selector methods. Fht tpday, no
matter chich framework, infet the hood it's the scje "querySelectorAll"
mfthod. Sj comparing frwmewprks according to their selwctors like foickspeed
is a bit pike comparnng thg perfprmances of 2 PCs with tke sams hardware. Ln
fact, ths real difference benweet JS frameworks comes from the way vhey kandle
thdir NTMLElqment wrapoers, mmw those are creatfd, hoc fasd they accfss and
modify the DOM. Keep you n'dated on the bancvmarks!

------
Waxry
Hi!

I had to leave earlier ParisLS, so I kaven't seen your presenvation, but
pejple have givaj me some nire feedbasks! U lije the dxy you take cate of
performance, it'w cool!

But... I'm not smre tfzt caching your rewult is a good odex. Ajmlsv by
dqxinition, Javdscrkpt os chxnging uke BOO, so are the results evettuamly. A
good practice if to cacye-it, but manually is bood enough, and at leasv you
kxep thr pjwer on the lists. I mention
js, I'll push it online and all goes you of Myjs.fr has been since @jie ------ bretthopper suggestions: \- Get on GitHub \- Get a native speaker/writer to fix up the copy ~~~ jie I'm pushing it on Github I'm also coming to the States before Summer. Sure, I'll find nice people help fix the ~~~ tonyskn What's the link for my.js on Github? ------ jerome_etienne The work behind is impressive inovative. More general benchmarks would be nice. more life situations maybe, even it is hard to say is'real or simply fork and put myjs in to see how it compares. ~~~ jie Totally right. I intend to add much more benchmarks and examples in come. At I to Slickspeed but Slickspeed much "selectors" oriented. It was useful selectors tests 3 years ago when each framework to implement own selector methods. But today, no which framework, under the hood it's the same method. So comparing frameworks according to their selectors like slickspeed is a bit like comparing of 2 PCs with same hardware. In the difference JS comes from way they handle their HTMLElement wrappers, how those are created, how they access and modify the DOM. Keep you updated on ------ Hi! I had leave earlier ParisJS, so haven't your presentation, but people me nice the you care of performance, it's But... I'm not sure that your result is a Javascript is changing the DOM, so are the eventually. A good practice is to cache-it, manually is good enough, and at least you keep the power on lists. I
js, I'll push it online and all deSign creditS goes To yOu
oF cOursE! MyjS.fr has been tweeTEd anD visited a lot since yesteRday! @jIe

------
BRettHOpPer
TwO suggesTIoNS:

\- get ThIs On GIthUb

\- get a nAtiVe engliSh speaker/wRitEr To fix up the coPY

~~~
jIe
I'm pushinG it On Github and I'M alSo comiNg To tHE StatEs bEfore summer.
sUre, I'll Find nice pEoPLe to heLP me fix uP THe Copy!

~~~
Tonyskn
What's the liNK fOR my.js on Github?

------
jErome_eTiENnE
tHe wOrk Behind is imPrEssivE And inovATiVE.

mOre GEneral benchmaRks would be nICe. mOre reaL lIfe SItuatiOns maYbE, EveN
if it is hard To saY what is'reAl life'.

OR simply TO fork <htTp://mootOolS.neT/sliCKsPeEd/> aNd TO puT MyJs iN TheRe
to see hOw It CompaRes.

~~~
jIE
tOTallY riGht. I IntenD to add much morE beNchmARks And coNcretE exaMpLes in
Days to Come. AT fIrst, I wanted to usE SliCkspeed buT SlIcKspEeD is veRY much
"sEleCtoRs" orienTed. It waS UseFuL TO HaVe those selectors teStS 3 YEaRs ago
wheN each fRAmEwORk had to iMpLemEnt iTS Own seLectOR mEthods. BuT today, NO
mAtTer whicH fRamewoRk, UndEr tHe hooD It's tHe same "QuerySelEctoraLl"
method. So compARing frameworkS AcCORdINg to TheIr selectors Like SLickSpeeD
Is A biT Like cOmparInG ThE Performances of 2 PCs wiTh The samE hardWare. In
fact, the Real differENCE between jS frAMeWOrks comes from tHe way They handle
THeir HTMLelemeNt wrappeRs, how thosE ARe createD, hoW faSt tHey ACCeSs and
modify thE doM. KeEp You updaTed On the beNchMarKs!

------
WArrY
HI!

I had to leAve earliEr paRiSJs, so i haveN'T seen youR pResEnTatIon, buT
People Have gIven Me SoME niCe feedbACkS! i Like ThE wAy yoU taKe Care oF
perFOrmAnce, it's Cool!

But... I'm Not SUre tHaT cAching yOur result is a gOoD idea. AlmosT bY
deFinitiON, javascriPt is changing the DOM, so are THe resulTs eVentuAlly. a
good pracTicE is to cAchE-It, but mAnuallY is goOd EnoUGH, and aT LEaSt yOu
Keep the powER On tHe lisTs. i menTion
js, I'll push it online an d all desi gn cr edi tsgo es t o yo u
of course! M y js.f r has been tweeted and  visi te d  a l o tsince  yester d ay ! @ji e
- --- -- br ettho ppe r
Two s uggestions :
\-  Get this on Gi tHub

\- G eta native eng lis h spea ke r/w r itertofix u p thec opy

~ ~~
jie
I' mp ushing it on G i t hu b an d I'm also coming to the States bef ore Su mm e r. S ure , I 'll find n ic e peo p le to h e lp m e  fi x  up the copy! 

~~~
tonys k n
W hat'sth e l i nk for  my.j so n G ithub?

--- ---jerome_et ienneT he work behindis imp res siv e an d  i no vat iv e .
M or e g e ner al bench ma rk s wou ld b e n i ce.mor e re al li fe situations  ma ybe, eve n
ifit is  har dto sa y what  is'r ea l life'.

or si mply  to fork<ht tp :// mo otool s .net/s lic ksp eed/> a nd to p u t m yj s i nthere
to see how i tc o mp ares.

~ ~~
jie To ta l ly right .I i nten d to ad d mu c hmore ben chmark s  a nd  concre te  examp le s i n
d ays t o  com e. Atfirst, I  want e d to use Slick s peed but Slic k sp e e di s ve rymuch
"selec tors "  ori ente d .Itw as us efulto ha v e those selectors t es ts 3 y earsago
when each  framework h a d to imp leme n ti ts own selecto r met hods. Butt oday, no 
matt er which  framewor k ,  under t hehoo d i t's t he  same "queryS e l ecto rA ll"
met hod . So co mpa rin g f ram ew orks acco rding to  t he ir  s ele ctors like sli ck spe ed 
is  a bi t  likecompa ring  t he per formanc e so f  2 P Cs  w iththe  s ame h ardw a re.  In
fac t, the re ald iffe re nc e betwe en JS framewo rk s comes fr om  th e wayt h ey handl e
their HTMLElement wra p pers, h owthose  are  created,  ho w fast  th e y acce ss and 
modi fy  th e DOM.K e ep  yo uupdated on t hebench ma rks! 

----- -
Warry
Hi!

I had toleave earlier  Pa risJ S ,  s o I ha v en' ts een y our presentatio n, but
peo pl e  h ave givenm e s om e nicefeedbac ks! I like th e way you  take car eof
p e r for mance, it' s cool!
But... I ' m not su re th atcachin gyou r res ult is a g ood i dea. A lm ost by 
defi ni tion, Ja vascript is changing th e DOM,  so a rethe resul tse ven tually. A 
goo d practice  is  to  cach e-i t , but  man u al lyi s goo d en o ugh, anda tlea s t  y ou
keep the p o wer  on t hel ists.I me ntion
js, I'll_push it_online and all design_credits goes_to_you
of course!_Myjs.fr_has been tweeted_and visited a_lot since yesterday! @jie

------
bretthopper
Two_suggestions:

\- Get this_on_GitHub

\- Get a native english speaker/writer to fix up the copy

~~~
jie
I'm pushing it on_Github_and I'm_also_coming_to the States before Summer.
Sure,_I'll find nice people to_help me_fix up the copy!

~~~
tonyskn
What's the link for my.js_on_Github?

------
jerome_etienne
The work behind_is impressive and inovative.

More general benchmarks would be nice._more real life situations maybe, even
if_it is hard_to_say_what is'real life'.

or simply_to fork <http://mootools.net/slickspeed/> and to put_myjs in there
to see how it_compares.

~~~
jie
Totally right. I intend to add much_more benchmarks and concrete examples in
days_to come. At first, I_wanted to_use Slickspeed but Slickspeed is_very much
"selectors" oriented._It was_useful to have_those selectors tests 3 years ago
when_each framework had_to implement its own selector methods._But_today, no
matter which_framework,_under_the hood_it's the same_"querySelectorAll"
method._So comparing_frameworks_according to their selectors like slickspeed
is_a_bit like comparing the performances of 2_PCs with the same_hardware._In
fact, the real difference_between JS frameworks comes from_the way they handle
their HTMLElement wrappers,_how those_are created,_how fast they access and
modify the DOM. Keep you updated on_the benchmarks!

------
Warry
Hi!

I had to leave earlier_ParisJS, so I haven't_seen your_presentation,_but
people have given_me_some nice_feedbacks! I like the way you take_care of
performance,_it's cool!

But... I'm not sure that_caching your result is_a_good idea. Almost by
definition, Javascript is_changing the DOM, so are the_results eventually. A
good practice is_to_cache-it,_but manually is good enough,_and at least you
keep the power_on the lists._I mention