this post was submitted on
6 points (80% like it)
8 up votes 2 down votes
all 18 comments

[–]maushu 5 points6 points ago

[–]Voidsheep 3 points4 points ago

JavaScript: The Good Parts is absolutely great. Buy it.

It tells you why JavaScript sucks and what you should avoid, but also why JavaScript is awesome and what you should take advantage of.

It's not exactly a good book to learn JavaScript syntax and how to actually do stuff, but it will save you from a lot of trouble and make programming JavaScript a better experience.

After you've done some basic DOM manipulation and gotten really frustrated, I recommend you take a look at jQuery library. DOM is a piece of shit, but jQuery makes manipulating it almost fun and eliminates a lot of manual work and cross-browser worries.

I refuse to start a single project without jQuery anymore, even if 31kb library for a couple of lines of JavaScript would be a total overkill.

[–]duniyadnd 1 point2 points ago

+1 for saying that he should still play around with DOM manipulation

[–]greim 0 points1 point ago

Read JavaScript: The Definitive Guide thoroughly and you'll be off to a good start.

[–]greut 2 points3 points ago

Don't forget MDC's: A re-introduction to JavaScript (which is not a book, but worth starting with)

[–]Amadan 1 point2 points ago

+1. Actually, I learned JavaScript from MDC - both the Guide and the Reference are a a very good read. After that, I'll second JavaScript: The Good Parts by Crockford (as suggested by Mezriss), which has some very good ideas on how to avoid the things that earned and kept JS such a bad reputation in the last decade.

[–]AlexandreMorgaut 2 points3 points ago

We add the same question on this thread of our forum http://forum.wakanda.org/showthread.php?211-Book-recommendations-on-Javascript-to-get-started

The main books for me are:

[–]moonicipal 2 points3 points ago

Offerring a slightly different opinion to Voidsheep: Try learning Mootools as a javascript library. It has more in common with native javascript syntax than jQuery does, and can do a couple more things unrelated to the DOM that jQuery can't.

Most importantly, learn to hand-write javascript! Nothing makes me turn away an applicant faster than seeing code pasted from the jQuery doc (not that it's low quality, but just that it's indicative of a copy-paste programmer)

[–]x-skeww 1 point2 points ago

[Mootools] has more in common with native javascript syntax than jQuery does

That statement doesn't make any sense. jQuery is a JavaScript library. Of course it does use the "native JavaScript syntax" - otherwise it wouldn't work.

You probably mean that Mootool's API is somewhat closer to the DOM API, but how is that a good thing? All those libraries exist, because everyone hates the DOM API.

[Mootools] can do a couple more things unrelated to the DOM that jQuery can't.

jQuery is a library for (normalized) DOM manipulation, ajax, events, and effects.

Mootools, on the other hand, is a web-application framework.

[–]moonicipal 1 point2 points ago

Ah, I knew I'd raise the ire of a jQuery developer. My apologies for the incorrect word choices.

Let me try again:

I find (in my limited experience with jQuery) that Mootools has a more sensible syntax (i.e. order of arguments) with its functions, as opposed to jQuery, where the order can vary from one function to the next. If in doubt, always check the doc, but I find that I can usually fudge my way through Mootools and get the syntax correct on the first(-ish) try.

And yes, jQuery is a library for DOM manipulation, and it's damn good at it. I just mean to say that Mootools can also do the same things jQuery can, in addition to a couple more obscure non-DOM related things.

[–]x-skeww 0 points1 point ago

I knew I'd raise the ire [...]

I merely corrected you.

jQuery developer

I don't contribute to jQuery.

My apologies for the incorrect word choices.

Are you doing this on purpose? :P

[with jQuery] the order [of arguments] can vary from one function to the next

Do you have an example? As far as I can tell, there aren't any inconsistencies.

[–]moonicipal 0 points1 point ago

Doing what, exactly?

In any case - when I say x developer, I mean a programmer who uses x... although I understand the confusion.

Examples? Not really, no. I have far too little experience with jQuery to contribute anything to a debate. I only offer my opinion on the subject. :)

[–]x-skeww 0 points1 point ago

when I say x developer, I mean a programmer who uses x

Use "x user" instead. "x developer" is someone who develops x.

I have far too little experience with jQuery to contribute anything to a debate.

But you said there is something wrong with jQuery's API and that Mootools doesn't have this particular issue.

Oh well. Whatever.

[–]moonicipal 0 points1 point ago

But on the other hand, I do use the term "PHP Developer" to refer to somebody who writes code in PHP...

[–]x-skeww -1 points0 points ago

Yes, you develop in some language and you can use some libraries/frameworks.

[–]rarkai 1 point2 points ago

Also, please read something like 'Dont Make Me Think'. Web Front End UX is very important. But yes, JS: the good parts is a great read.

[–]PrincessKneesaa 0 points1 point ago

If you want something a bit more advanced, try 'Object-Oriented JavaScript' by Stoyan Stefanov