I, for one, do not hail our new TPP overlords. I vote nay.

I laughed. (In a good way.)

http://www.slideshare.net/kenbot/imagine-a-world-without-mocks

"Wherever you look in good Smalltalk code to see how something is done, it always seems like the work must be being done somewhere else."

Snowballs are merrily melting in hell.

http://www.oracle.com/technetwork/articles/java/jf14-nashorn-2126515.html

A really nice overview, and hopeful look forward regarding error handling.

I'd like to know what the subset of JavaScript is that causes the least performance problems. Like, I wish all programming languages came with a big wall chart of onion layers, showing "oh this core kernel nugget is the fastest (and probably least expressive) subset; and then this next outer layer adds a feature that when used incurs a penalty; and then the next layer out from that; and then 'eval' just dooms us utterly." Then we could as humans better understand our own code, and we could also try to train our compilers to know.

so far, this has been a good book for us: Secret Coders. i do recommend the book!

but -- and, oh lordy, why does there always have to be a but? -- things kinda go pear shaped from there:

• They say they have videos. As in, plural. Uh, yeah - no. Not really. And they don't say when any more will appear. That's just bad user experience.
• They suggest you use UCB's Logo. Which is all broken links, since apparently the site's server no longer supports https. Or something. So that's genius.
• If you figure out the trick of removing the "s" from the https in the urls, you can get the program...
• ...only to find out it is sort of a piece of junk, frankly. Just a completely terrible UX overall, and it also gets thrashy and hoggy and just plain broken.
• Then I went out to try to find other versions of Logo, and I gotta tell ya, it is a wasteland out there. Just a complete UX wasteland.