He did write a bit about the status of the book back in July, if anyone is interested: http://ejohn.org/blog/secret-omens/
edit: John just tweeted: https://twitter.com/jeresig/status/285858421029347328
I plan on writing up a full blog post once I have my copy of the book.
In another life I wrote technical books, which at the time were only available in physical formats. That didn't stop electronic versions of the more popular books from appearing on usenet.
Because the people downloading it are not necessarily the same people who'd have bought it otherwise.
Plus exposure. I pirate a lot of stuff. At the same time I buy more books and music than anyone else I know.
"Ironically working on the book (or not working on it, however you look at it) actually compelled me to NOT blog more as every time I wanted to write a technical blog post I was forcing myself to make the decision “I’m writing about 1000 words on a technical matter, shouldn’t this just be going towards my uncompleted book?” and would just end up writing nothing as a result."
I'm not sure just how relevant it will be, now that the JS ecosystem has exploded -- seriously, 4 years is _eons_ in the JS world, I think the Jaxer server was still the new tech and NodeJS wasn't even heard of at the time -- and there are 10x's as many JS devs now than there was in 2008 (not to mention that the average competency seems to have greatly improved as well). And I could be wrong, but I think he's mostly disconnected from jQuery itself now, too; I'm clumsy with git/github, but I can't even find his last commit to jQuery, and I know that all of the blog posts on jQuery.com have long since been done by other team members. While he's a really talented dev, his name is pretty rare when it comes to JS news and topics these days.
I also feel extremely confident that the technical work that I've done with the Khan Academy CS platform continues to be unlike anything else done by other development platforms.
Happy New Year!
I won't argue that there isn't still a ton of education that needs to happen! I've been battling this at work, as few candidates have much JS experience at all (I think all of the good ones are involved in the hot projects).
I'd also concede that educating future coders is possibly not only more important, but more fulfilling. I've been following your blog for awhile, and though I do miss the geeky JS topics such as the precision (or lack thereof) of setInterval/setTimeout, how great documentFragment's are, etc. I've also enjoyed the posts about Kahn.
Thank you for the kind works regarding my blog - I really hope to begin writing again. Perhaps that'll make for a good new years resolution :)
As I think John eluded to, there's a number of developers that don't fall into any of these buckets and a book like this would certainly be useful to them. I was with John on the jQuery team and I know that I'll be picking up a copy of this since I'm sure I'll find some nugget of awesomeness in there that will make it worth the price.
It is just amazing to see how much it has exploded in the last few years. Serverside js and client side mvc will keep me excited at least for another year.
* asynchronous concerns such as callback hell (and other focus areas as addressed by Async.js)
* the MV* hysteria
Thanks for the reply, and good luck with the book! I do plan to check it out.
Perhaps you should learn what you're criticizing before you criticize it; CommonJS has put forth a lot of effort to try and standardize API's across platforms (browser, server). API's for things like...promises. And modules, plus many more. Ironically, several of these could very well end up in ES Harmony, and so to discuss them now wouldn't be too much of a risk because the problems they solve exist today.
Yes, but if you work with JS in any capacity today, then there's a good chance you'll be working with either or both of those technologies.
> not on canvas , webgl, requireJS or Express or Backbone
I didn't mention any of those...
The title still sucks. I don't get this idea of (ninja|rockstar|etc) and it's extremely disrespectful to those that practice those disciplines.
How about Shaolin Monk JS? Hung Ga JS? Hung Fut JS?
Is the absurdity getting through your brain yet?
And if you're talking "Evangelist," where the fuck is your church?
I looked up ninja (http://zillyninja.blogspot.ie/2011/02/origin-of-word-ninja.h...) and apparently it can mean "a person skilled in stealth" or "one who endures." while the ninja themselves were spies for the samurai but haven't been around for a long time (http://web-japan.org/kidsweb/explore/history/q4.html).
Expert comes from the latin word expertus ( past participle of experīrī to try, experience)
(http://dictionary.reference.com/browse/expert?s=t) and presumably someone had to import it to english and later on someone else used it in a new unorthodox way.
BTW I looked it up and the word evangelist comes from greek and means 'bearer of good tidings', so it isn't something that has to be tied solely to religion
If you want to do that, go write fiction. If you're as adept at writing in the English language as Anthony Burgess or James Joyce, you can feel free to even make up words as you go along, not just new uses for existing words.
"Clothing used was similar to that of the samurai, but loose garments (such as leggings) were tucked into trousers or secured with belts."
The purpose of those flags is to signal who and where you are. Neither of those goals aligns very well with what ninja do.
You can order it through them rather than Amazon to get the eBook directly.
I wish authors would produce for various platforms, rather than targeting just one, even if it is the de facto market leader.
Edit: of course after I posted this, I see that it is available in PDF format from Manning's site: http://www.manning.com/resig/
Ouch! For John's sake I hope Amazon gets the category corrected.
Though something tells me you weren't looking at the Bible.
The fact that writers can and will sell to a niche audience willing to part with a lot of money ultimately leads to a field sparsely populated with accessible topic literature...
It's a good read though, and now that it's finally released, I'll take a look at it again.
The JS ecosystem has changed a lot though, but this book, if I remember it correctly, explains a lot of the rationale of why it's good to program JS a certain way.
I guess I've been spoiled by the grace of the past 10-15 years of technical book buying, but that is insane.
Side Note: It's now 2013 and we're still doing that.
Congrats on finishing it. Book writing is hard.
That said, despite the retarded title, I have no doubt that Resig has some good secrets to share. Mad respect for a brilliant developer with a terrible editor (book editor not vim).
Not to mention idiotic.