jQuery is open source. even if all the developers who have contributed to
it took off on a space ship, there would still be jquery!

I understand your pain because you fell for Microsoft hype. You put your
trust in the untrustworthy!

jQuery is understandable; every bit of code I write , I know pretty much
what it's actually doing. I chose jQuery, not because I couldn't do the
work, but because it's easier, more fun, and really really works. And I
don't want to debug the weirdnesses of Microsoft Internet Explorer!


Does that mean it's future proof? I don't know. But in jQuery I trust.



On 4/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


I am starting an asp.net project, and I would like to use javascript
and client-side
xml processing to make for a more responsive interface. Initial
prototypes look good,
but actually getting the xml using asp.net seems a bit tricky. A <xml>
data island worked well,
but this element is dropped from msxml6. It seems like there will be
browser issues even in a pure IE shop. The proposed solutions I found
for these problems have almost scared me off client-side processing.
Does jQuery promise any future-proofing along these lines? -- Dave




--
Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ

Reply via email to