JavaScript Console API – Browser Differences

Recently I was asked by a client to if using console.log() would be appropriate in enterprise web applications.

Not everyone agrees with me, but my opinion is simple: Production applications should rarely, if ever, use the console API. I don’t think these statements should ever be checked into version control – they clutter your code, and ultimately make debugging more difficult (because you have to ignore console messages unrelated to a given problem).

Additionally, I have seen errors reported in Internet Explorer by the console object – runtime errors that are in effect bugs in your code.

We went on to discuss the console API and how it offers more than just the standard console.log() method. That got me thinking… even though the major browsers seem to support a consistent console API, are there any actual differences in the implementations?

LintRoller – Because no one likes lint

A little more than a year ago, I began playing with Phantom.js. It’s an awesome platform for doing a variety of JavaScript-y things… and not long afterwards I created a tool called PhantomLint to automate testing my code against JSLint.

This solution worked well for the past 12 months, but like most developers I wasn’t satisfied with my own work.

First Thoughts on Windows 8, Visual Studio, and ExtJS

As a developer, I have probably 1000 things on my personal list of “things/technologies I need to learn”. One of those items was to build a Windows 8 app using HTML5, and over the past few days I’ve successfully managed to build a crappy sample app!

As Windows 8 is scheduled for release soon, I figure many HTML5 developers have not had the time to download/install the pre-release versions. Before I dive into some specifics of getting an ExtJS app to run natively on Windows 8, I wanted to share some general thoughts.