Structuring front-end JavaScript apps to scale

• Name : Phil Leggetter
• Twitter : @leggetter
• Github : leggetter
• Website : leggetter.co.uk

Abstract

Over the past year or so, the company I've just joined have been building a developer toolkit and lightweight front-end framework that's helped them ensure that a 200k LoC JavaScript SDK hasn't become a tangled mess of unstable spaghetti code. This SDK is then delivered to enterprise organisations who are expected to build on top of around 50k LoC example functionality that's shipped with the SDK… and not turn that into a tangled mess of unstable spaghetti code. At the same time, all this code needs to be easy to navigate, maintain, continually test, enhance and develop upon.

How is this achieved with an app of this scale, you may ask?

In this talk I won't directly discuss the toolkit itself, but instead cover the main points that have been considered when trying to achieve what might sound like the impossible.

Speaker Bio

Phil @leggetter is a Developer Evangelist at Caplin Systems where he's leading the project to open source BladeRunnerJS. He's the co-author of Realtime Web Apps, contributor to HTML5 Hacks and writes articles for Smashing Magazine, .net magazine, Programmable Web, on his own blog and anywhere else he gets an opportunity to create content. Phil's passions include developer experience, customer service and helping people realise the benefits of realtime web technologies, and then use them to build the next generation of interactive and engaging web apps.