State.js 2016: JavaScript, Here and Now
While Twitter, for many individuals, has taken the place of blogging — instead, for me, it’s the place where ideas are fostered and allowed to grow before expanding into fully formed pieces of prose.
While Twitter, for many individuals, has taken the place of blogging — instead, for me, it’s the place where ideas are fostered and allowed to grow before expanding into fully formed pieces of prose.
A few weeks ago, I gave a talk at the Chicago Node.js meetup about our technology stack for The Machine. I’ve only been working with Node.js for a couple of months, but in that time, I’ve learned many difficult lessons.
One of the major challenges I’ve had to overcome with Node.js is a task that’s relatively simple in Ruby. You wouldn’t think this would be difficult, but serializing JSON can be frustrating, even though you’re working entirely in JavaScript.
In a previous life, I was a professional web developer. I’ve used JavaScript extensively throughout my career, but I always saw it as the necessary evil: a weird little language that existed solely to provide interactive features in your web browser.