Learning JavaScript… Should I skip straight to the

Question

I learnt HTML/CSS a good few years back, then PHP a little later. I've recently become interesting in web development again, just started playing with frameworks like Django and RoR. I'm curious as to how much time/effort I should spend learning straight JS before looking at frameworks. I've been reading through a let of articles called Mastering AJAX by Brett McLaughlin which seems quite good, but I'm seeing a lot of stuff (such as cross browser compatibility - even for things like XMLHttpRequest) coming up which look like they would be non-issues if using a framework.

So, should I keep reading through these articles and try to build stuff using basic JS, or should I just start looking into jQuery and the like?

Also, I've been watching a few videos regarding GWT from Google I/O. I've been learning Java over the last year, built a few medium sized apps in it. I'm wondering if GWT is something that's worth going straight to, along with gQuery?

Answer 1

I think "both." Mix it up. Play around with a framework. You'll get stuck when you try to do something real, so you'll pick up some JavaScript to figure it out.

A lot of the good jQuery books teach you JavaScript along the way.

Answer 2

No.

Just as when you are learning to program you are taught first C/Pascal then Java/C++ and finally Python/Ruby/Smalltalk/Lisp, and when learning any language you start with simple language constructs, you should first learn ECMAScript, then learn DOM and finally frameworks.

Why? Because you'll have a deeper understanding of the language, and will be able to debug things that might seem odd unless you've got that learning experience.

If you are a seasoned developer, you can speed up each phase, but don't skip them, or you will have problems due to not fully understanding the small oddities.

Javascript is an interesting and fun language, but can act rather odd at times (Date has bitten me a couple of times in the ass).

Use frameworks to avoid repetitive tasks and to simplify your code, but not as a starting point. Simplicity is a final goal, not the starting point, and frameworks are for that, simplicity, not for learning a language. Frameworks are intended for simplifying things for experienced developers.

---

Learning the differences between browsers (DOM implementations) will allow you to debug your framework. That is priceless.

---

I've been learning Java over the last year...

Javascript is not Java. Never was never will.

Even if you can compile to Javascript from Java, it's still a framework, don't jump into it unless you already know what you are doing.

Answer 3

I wouldn't touch any framework in any language until I have good basic understanding of underlying technology. Worth type of coder is one that uses tool without a knowledge. JavaScript has somewhat sad history but in its latest incarnation it's surprisingly powerful and even fascinating language. I say - learn it well, then use whatever framework suits your current needs

Answer 4

This is one of the best videos for beginner javascript developers that understand how to program in other languages:

It's a talk the John Resig did last year at Northeastern, most of it is devoted to talking about core javascript, then the last quarter of the talk jumps into jQuery:

http://video.google.com/videoplay?docid=-7485992465859932389&ei=jhZUSu73OpfSrQLgyYV3&q=john+resig&hl=en

It's actually a really interesting tech talk and presentation since he does live examples and Resig is pretty good at presenting.

Like others in this question, I also highly recommend reading Javascript: The Good Parts for a better understanding.

Answer 5

Starting with the basics of JavaScript is a good idea, IMHO.

Read JavaScript: The Good Parts, by Douglas Crockford. Very, very good book.

You should also check out Douglas Crockford's web site.

I also had to come back here and mention this in an update:

Douglas Crockford presented an illuminating talk about JavaScript - past, present, future - at the Microsoft MIX10 conference earlier this year. You'll find the full video for Crockford's talk at Microsoft MIX10 - The Tale of JavaScript. I Mean ECMAScript.

Answer 6

Yes, jumping straight to framework-based programming instead of DOM is a good idea.

I started doing JS before any major frameworks like jQuery came along, and was reluctant to switch at first, but when I first started using jQuery, it felt so good to be able to write selectors and stuff and not have to worry about cross-browser compatibility.

However, there are some areas of JS where frameworks wouldn't be available. One of them is in userscripting, where you have to make your script work on a site you don't control. Another such one is the use of JavaScript in applications such as XUL.

Overall, I suggest you start with some trivial JS applications, then switch to jQuery instead of going on to the complex topic of DOM.