I'm inclined to agree. Having a good foundation of JavaScript before adopting any library will do these students a much greater service than simply teaching them an API that is already relatively easy to learn. Teach them JS, and in places where is really matters, show them how JQ (or the other libraries, no need to be biased in an academic setting right?) supplement JS and/or the DOM to work around the pain points you have shown them.
Regards, Peter Hggins On Thu, Jan 8, 2009 at 4:38 PM, Klaus Hartl <klaus.ha...@googlemail.com> wrote: > > jQuery is JavaScript, and at some point you need to know JavaScript. > > I would never hire anyone who claims to know jQuery but not > JavaScript. > > my 0.02$ > > --Klaus > > On 8 Jan., 22:23, pixeline <aplennev...@gmail.com> wrote: >> Hello mates, >> >> I will start to teach web usability to freshly graduated youngsters in >> a graphic design school _ web dept, web dept. >> The Board recently proposed me to also take over javascript. Now i >> intend to them i'm not literate enough in javascript to actually teach >> it. But i proposed instead to teach jquery, with the main argument >> being: it's a 3-year programme, it's not with 2 hours a week that most >> kids will get professionnal level javascript skills. Teaching jquery >> on the other hand, may give these junior designers a useful knowledge >> and discover scripting from a starting point that they understand _ >> not the (with all due respect:) ) geek's "code is poetry" point of >> view, but from the "in your face" designer point of view. >> >> I would like to know what you guys think of my argument: is teaching >> the usage of a specific javascript framework relevant to the business >> world? Would you hire a freshman that cannot program pure javascript >> but can pretty much achieve the same result, in less time, with >> jquery? >> >> Looking forward to reading your thoughts ! >> >> Cheers, >> >> Alexandre