My NYC CodeCamp Talks – Javascript and Node.js

Yesterday I did a couple of talks at the NYC CodeCamp which Lab49 was sponsoring. It was a great event and I really enjoyed meeting many of the 400 developers who attended. My one regret was that due to presenting myself I missed great talks from my fellow Lab49’s Scott Weinstein and Doug Finke.

My first talk was an introduction to Javascript where I explained that despite JavaScript looking an awful lot like C# and Java, it’s in fact not much like them at all. But don’t panic – it’s an extremely simple language and once you understand it’s basics (prototype based inheritance, hoisting, functions, etc..), you’ll be able to understand most JavaScript code out there.

My second talk was an introduction to node.js and how running JavaScript on the server is in fact far from the worst idea. The intention of the talk was not to try to convert a room full of ASP.NET developers to Node, but to explain where node is innovating in the web platform space and how we’ll probably see a lot more of these techniques in the future on every platform (code sharing between client & server, simple API’s for real-time web communication). The demo’s I did during the talk can be found on GitHub.

I’d be really happy to give these talks again so please get in touch with me if you’d be interested in having me speak at any development groups.


6 thoughts on “My NYC CodeCamp Talks – Javascript and Node.js

    1. WebSharper has been on my list of things to look at for a while. I’m always a little skeptical of these frameworks that attempt to let developers write and work with libraries in js without having to write or understand js or the web (*cough* WebForms *cough*). As my presentation above was trying to explain, js is not hard stuff and you’ll write better write applications as a result.

      However I’m open to the idea of more productive frameworks and assuming they’re flexible enough then they could be really useful. I’m also a big F# fan so I wouldn’t mind writing more in that language. I’m not so excited about trying to add type safety to js, I’ve found the most productive thing to do in js applications is to do quite the opposite and exploit it’s dynamic nature. Where I think F# could be a big win is using it to help ease some of the difficulties dealing with large asynchronous workflows (callbacks to callbacks to callbacks…).

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s