@dz  No offence, but why are you taking part in this "pointless
discussion" ?

I am really puzzled on what arises a certain ammount of confusion
here? JScript conditional comments, IE html conditional comments, etc
are nothing new. People have been using them for years. And the whole
"conditional compilation" concept is decades old.

(one very relevant and recent example : 
http://dean.edwards.name/weblog/2008/01/ie7-2/
)

One good example of a measurable benefit. Not in speed but in
stability would be jQ UI. They would benefit even more from separating
IE vs NON-IE code. The amount of greef (it seems to me) they are
getting because of IE, is v.large. Most of the discussions in jQ UI
forum are formed arround IE 6,7,8 issues ...

Ah, yes, and yet another no-brainer is CSS. CSS comunity has solved
(is solving) many difficult issues by separating IE vs NON-IE CSS ,
mostly through conditional HTML inclusion. I think this is very
measurable benefit in the context of web apps stability. I do not know
what was before, but it seems no one "over there" is confused with the
beenefits of using

<![if !IE]>
<!--  my not ie css styling -->
<![else]>
<!-- my ie css workarrounds -->
<![endif]>

Lastly. Of course tests need to be done. What makes you think I do not
think so? But please understand the conceptual advancement here which
is not going to be measurable just in the terms of raw-speed.

--DBJ

On Sep 1, 2:56 pm, David Zhou <da...@nodnod.net> wrote:
> Then run some tests! Take your no brainers, apply them to a recent
> checkout of jQuery, and record some data!
>
> You said that separating out IE stuff from jQuery into a separate
> branch would show "measurable benefits (in spead increase and
> stability)."
>
> I'll repeat, because you seem to have missed the point: *until* we get
> numbers -- from you or whoever else -- this is a pointless discussion.
>
> -- dz
>
> On Mon, Aug 31, 2009 at 8:39 PM, DBJDBJ<dbj...@gmail.com> wrote:
>
> > @dz "no brainer" is not a title here ... that much is obvious.
>
> > For me personaly it is a "no brainer" to do (for example) this :
>
> >  // Handle memory leak *only* in IE
> > /*cc_on
> > script.onload = script.onreadystatechange = null;
> > head.removeChild(script);
> > @*/
>
> > Instead of this :
>
> >  // Handle memory leak in IE
> > script.onload = script.onreadystatechange = null;
> > head.removeChild(script);
>
> > I mean this practically, not hypothetically.
>
> > --DBJ
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to 
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to