Full Stack Javascript June 2011

I’m tired of using a gajillion languages in one stack. A few years ago, it made sense, and there was no better way of doing things. But in the last five years or so there have been a number of wonderful innovations that are (fortunately) rendering this old pattern of using many languages in one stack (LAMP, for example) obsolete:

Using a full JS stack, we can just pass JSON objects around all day long, and never have to worry about data types or formatting. Forget toArray() or toJson()! Such a stack would only need to include Mongo and Node.

With that said, it’s easy to see the benefits from a developer perspective. But there’s another advantage to having a full JS stack that any CTO or Project Manager should get exited about: you would only ever need to worry about hiring JavaScript developers. Your team would all speak the same language, and it would be easy to move developers around from one area to another.

Update: This article directly supports my ideas for the development team benefits of using full stack JS.