Good JavaScript programming book?

Sup, /p/?

I'm learning how to program in JS, and wondering if y'all could suggest a good book for it. I've already blazed through JavaScript: The Good Parts. Guess I need to learn about the bad parts now...

>>1
Having to declare functions,vars and other minor syntax quirks(if x!=null && x.prop!=null && x.prop.prop!=null)
Lack of typed variables, Layers of cruft/security/bureacracy which make ArrayBuffer and IntXArrays hard to use or integrate into other parts. 
Lack of system integration: the bureaucracy layers of JS which involve security in any form are lovecraftian
Lots of browser-specific code,alot of cool stuff is only available for recent FF/Chrome/Opera builds
DOM performance limits, WebGL not working half the time
Errors can be silently supressed and script will just not run(it will stop at error, but will not display anything to error console)

http://www.chatbots.org/book/ai4u/

(Artificial Intelligence for You) is a book about coding

http://www.scn.org/~mentifex/AiMind.html

Ai in JavaScript for Microsoft Internet Explorer (MSIE).

JavaScript still lacks macros or preprocessor define

>>3
Damn', that is some beautiful grade A madness. Nice to see a FORTH implementation too. There's a language I already know and love.

>>3,5
How credible, stupid spammer of worthless shit...

>>1
That would be: JavaScript: The definitive guide.

http://eloquentjavascript.net/
It's an `interactive' book; you can play with and test the examples as you go along.

>>4

I haven't tried, but I bet you can do it pretty easily with eval. It opens up security holes, but that's probably not such a big deal with java script running in someones browser.

using javascript over python

Open error console
Create a webpage
save to disk
edit webpage
reload webpage in browser
Read-eval-print for free.

For some scripts i even have window.timeOut(update,10000) so it reloads the latest version of the script automatically(with selectable intervals).
so its really write-view results

>>1
start off by reading through some of the pages on quirksmode to get a feel of how terrible javascript used to be due to browser incompatibilities.

lucky for you, things have changed since the dark old days and JavaScript got formalised as ECMAscript. so ... you might want to read through the reference to ensure you know of all its features.

the browser API's got standardized by W3C and there's a metric shitton of them (http://www.w3.org/standards/techs/js). the HTML5 team is also creating new API's. Not everything is supported everywhere so code accordingly.

NB: the web is full of shitty javascript that got copy pasted from site to site. stay away from those shitty tutorial sites, the only site i really use is MDN.

>>12
cool

>>13
https://developer.mozilla.org/en/DOM

Question: I've hear document.writeln is a bad practice, but what alternatives?

not op btw just hijacking

>>15
try document.body.innerHTML+=content or element.innerHTML+=content

try document.body.appendChild(document.createElement('h1').appendChild(document.createTextNode('herp n derp')))

>>17
Its vastly slower than altering raw HTML. A script could construct a dozen of pages on the fly(string/array join ops) while you much with structure of childNodes/parentNode and wait for redraw(since HTML is reparsed each time you insert a node)

>>18
STFU. noone cares about your micro optimizations, ``faggot''. We do this shit for a living: other programmers have to be able to quickly understand/debug our code. so we use the DOM. your priorities betray your inexperience in the Real World.

(also: you can simply use document fragments to avoid a redraw, n00b)

>>19
But Real World VROOM OMG OPTIMIZED must be fast.

>>20
U MENA GENTOO OPTIMIZED?

YO! DAWG CFLAGS JUST KICKED IN!!!

Multiplication is associative (κ·μ)·ν = κ·(μ·ν).