Skip to main content

JavaScript as Assembly – Exploring CoffeeScript & Dart


Just agreed to a talk on Monday, June 18 for UpFront KC. Here is a quick summary:

JavaScript as Assembly – Exploring CoffeeScript & Dart

JavaScript can be both awesome and terrible. We’ll talk about the history of generating JavaScript and then work through some quick exercises in two languages that can produce JavaScript as output: CoffeeScript and Dart. Then, we’ll compare the two and look where they are headed.

This is an interactive talk, so plan to bring a laptop and code along. At the end, you'll at least have run a bit of CoffeeScript and Dart. You don’t have to be an experienced developer, as we’ll keep it super-high level.

About your presenter:

By day, David Mitchell is a mild mannered Group Technical Director at VML, where he is more likely to review JavaScript code than write it. By night, David is a polygot programmer, exploring languages like JavaScript, Smalltalk, and Lisp. David has presented nationally and at regional conferences and has taught programming at Sprint, Centriq, and at workshops for kids through local schools and homeschool groups.

Comments

Popular posts from this blog

Pride and Shame: A simple code review format for developing developers

Gave this talk at BarCamp Omaha this September. Thanks to TechOmaha for recording!

Iowa Code Camp 5 on May 1, 2010

The site is still showing ICC4 info, but the countdown clock has been updated to a new date! Looks like I need to free up a spring day for some hacking! While browsing the site, found a picture of me presenting Seaside at ICC4. The book in the picture is Learning Programming with Robots. I think I was answering a question about Alice.

Refactoring – Ruby Ed.

The original Refactoring book by Martin Fowler had a big impact on how I thought about writing software. I’d used the refactoring tools in Smalltalk, but the book changed the way I thought about refactoring and gave names to many new refactorings. This Ruby edition of the book is highly anticipated. I received my copy at a drawing in our local Ruby user’s group. Part of the deal was you had to write a review (you are reading it) in exchange for the book. Nearly everyone at the meeting wanted a crack at the book. The authors suggest that if you have the original work, you probably shouldn’t purchase this new edition. I don’t agree. There is plenty of new content with around 20 new refactorings and a few new code smells to make the difference worthwhile. There is a tremendous amount of thoughtful Ruby code snippets inserted throughout the text. In fact, this is one of those books that is great for everyone on a team to have a copy. It is the kind of book that can be used to raise t