On Tue, Sep 1, 2009 at 11:45 AM, DBJDBJ<dbj...@gmail.com> wrote: > > @dz No offence, but why are you taking part in this "pointless > discussion" ?
Because if there *is* a significant speed increase, it's valid and therefore interesting. There's a lot of sound and fury, but not a lot of data. > 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. People have been using them for years -- but not blindly. jQuery just recently made a move towards feature detection rather than browser detection. Separating out non-IE code is a step backwards towards browser detection. If that step is to be taken, you need to show measurable gains beyond screams of "it's better!" and beyond generic appeals to tradition and authority. This isn't cargo cult mysticism. If there are gains, create some test cases and show them. > (one very relevant and recent example : > http://dean.edwards.name/weblog/2008/01/ie7-2/) How in the world is that relevant? His javascript does not use: 1. Jscript conditionals 2. conditional compilation His front-end code uses HTML conditional comments, but that's a completely tangential issue, and has no parallel to what is being discussed in this thread. > 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 ... Then take it to the jQuery UI forum. You do realize you're on the jQuery mailing list? Although, I'd wager a fairly large sum of money that after all the work in separating it out, you'll not help those people with IE6/7/8 issues one bit. Most, if not all, of the issues are not because the IE branches are together with non-IE branches. > 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 You're conflating problem domains. It muddles your point and confuses the hell out of everyone. HTML conditional comments were used because it was the *only* way to properly ascertain browser version without resorting to CSS hacks, which could change with each new browser. This isn't analogous to the code branching inside jQuery, especially after it switched to feature detection. > 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. Then stop saying, and I quote, "This kind of delivery, would show measurable benefits (in spead increase and stability)." -- dz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
