we use snapengage on our site and it's a pretty smooth experience. Very happy with it.

Kinda cool. While covering basic topics I don't know if this really the best guide for beginners. REPL is just not a term a beginner needs to know. Also while the console is awesome It's hard for a beginner to take the knowledge and apply it to something they can immediately do on their own.

good call, I took the REPL section out. the whole thing is also on github in case you wanna help out https://github.com/maxogden/javascript-for-cats

Seems like there are still lots of references to REPL. Potentially remove them all? Why not just call it a console?

Oh hahah I forgot I had used it so much

also a good call. my god github is amazing. again good job.

the browser crashing problem just shows it's still such a new paradigm that programmers still are not tackling the problem correctly. many libraries are already being written to better handle this problem.

I've never been much a fan of native themes. Also I really like the design of Sublime text.

don't they have till the 2nd? I have a hard time believing they will bother doing anything useful until the last possible second.

I'm a big gui guy and vim has just been too much a pain to learn. Something tells me if you have been using vim for that long there is really no good reason to switch.

I use it and love it. If you ever tried 1.x and have not tried 2.x then you should give it another try. It's worlds better.

donated. easy choice. I uses quirksmode often.

as much as I'm sure it's not a trap it's still a pretty bad practice. In theory your site could also get hacked and people could start collecting new usernames and emails not in the database.

As I've stated several times, my site doesn't store any details like these, it uses OpenInviter, they authenticate the credentials, pull back the list of contacts, I process the list of contacts and check it against the database of EXISTING hacked email addresses. The credentials you supply and the email addresses I pull back are NOT stored anywhere.

To be honest. With firebug's ability to tell me what line and css files the style on an element is coming from I don't find spending a lot of time on organization to have a ton of benefit.

While I love Firebug, I'd have to counter that organization with CSS is actually quite important (and does have its benefits!)

This is especially true when you're working either in a team environment or on a large site. The very nature of CSS (and how things cascade down) can become a nightmare when organization isn't taken into account from the start.

I agree completely, especially on a web app that is constantly growing. 2 on-the-job things that help me the most are:

1. Using the 960 grid system (or your preferred grid flavor) 2. Grouping by the following:

Body Typography Forms (Other global stuff like links and buttons) /* Layout Element 1 / ID1 {} ID2 {} class1 {} class2 {} / Layout Element 2 */ ID3 {} ID4 {} class3 {} class4 {}

I also write my styles on one line, but that's just personal preference. I find it easier to scan down for the selector, then across for the property I want. I definitely don't do it for aesthetics or file size ;)