Review: Best Javascript book EVER.

Douglas Crockford's "Javascript: the Good Parts" - go get it. Its concise, and takes you through the semantics of Javascript from first principles. Unlike most such books, which try to make learning JS easier by over-analogizing to other languages, Doug's book also highlights the differences from the very beginning - building a much better foundation for understanding the language, pros and cons.

Heartilty recommended regardless of your level of sophistication or intimacy with Javascript. At a minimum, you'll come away with a better framework for approaching your web applications. And if you're language geek, you'll just like it.

Plus, its concise.

Probably my favorite programming book since the red book (level 1, natch).

Practical Joke?

I read this headline on Slashdot:
Halliburton Applies For Patent-Trolling Patent

It's GOT to be joke... see the original article: http://www.techdirt.com/articles/20081107/0118162765.shtml


Is it April 1 somewhere in the world? *Somebody's* got to be kidding... please?

Election '08 (that's a wrap)

"There's no question about it - In the next 40 years a Negro can achieve the same position that my brother had."  - Robert F. Kennedy, 1968.  

Google Chrome Review in 25 words

Pros: Great UI (not break-through, but very nice), Fast

Cons: Memory hog, Crashes a lot, not quite as compatible

Summary: Its my default browser - go figure!

Google Chrome: Quick Browser Benchmark

Update: IE 7 was not included because it took too damn long to finish and I got bored.

Using Dromaeo.

Firefox 3_____2042 ms
Safari 3.1.2__2561 ms
Chrome 0.2:____540 ms

Actual product thoughts forthcoming after a few days of usage... but my "first 10 minutes" review is: nice, but nothing that would make me switch (from Firefox).

New Browser: Google Chrome -Launching Tomorrow! (maybe?)

Update: Official statement.

Lots of information available at blogoscoped. Of particular interest is how it looks like its going to be introduced: using an online graphic novel by Scout McCloud.

The new JavaScript VM should be interesting - I've certainly felt you could achieve 5-10X current JavaScript without resorting to a JIT for dynamic languages. Too much is made of the process isolation (IMHO) - though there is something nice in the idea that each tab is a "reboot" of your browser.

They also outline some UI design choices which I think are appropriate - we did them quite intentionally on AOL Explorer, and (forgive the sense of vindication but) two items I feel particularly that I pushed (larger back button and tabs above the address bar) look like they're mainstreaming... pity we blinked so often back then.

Hopefully there will be more in "Google Chrome" - a rethought browser is looooong over due. Definitely read Scott's comic commentary as to why.

Probably unfair to juedge without a test drive, but what I see in screenshots is still pretty incremental (as was AOL Explorer) - it would be a continued sign of corporate hubris to imagine success by tweaking a successful formula and sticking their brand on it.

(Note that I'm not saying it won't work.... :P)

I'll post some thoughts when I try it out.