Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Large Scale JS Engines

Large Scale JS Engines

A presentation back from 2011, be gentle

Thanos Polychronakis

March 04, 2011
Tweet

More Decks by Thanos Polychronakis

Other Decks in Programming

Transcript

  1. LARGE SCALE JS ENGINES @THANPOLAS WHAT IS A LARGE SCALE

    JS ENGINE? • Implements our API • One page load • It’s a framework
  2. LARGE SCALE JS ENGINES @THANPOLAS CHALLENGES BUILDING LSJSE • Name

    spacing • Templating • Facilities • Data Objects Handling • Source Tree • “Compiling”
  3. LARGE SCALE JS ENGINES @THANPOLAS GOOGLE CLOSURE LIBRARY Not Another

    Framework Closure library is a LANGUAGE ENHANCER
  4. LARGE SCALE JS ENGINES @THANPOLAS WHAT IS CLOSURE LIBRARY? Components

    • Core Library • Compiler • Templating System • Closure Linter • Server agnostic • UI / UX / DOM • Cross-browser • Very Light! Highlights
  5. LARGE SCALE JS ENGINES @THANPOLAS LSJSE ARCHITECTURE Name Space Properly

    Do yourself a favor web.user.signup.ui.start = function(){};
  6. LARGE SCALE JS ENGINES @THANPOLAS LSJSE ARCHITECTURE Shortcut Assign Variables

    web.user.signup.ui.start = function() { var ui = web.user.signup.ui;
  7. LARGE SCALE JS ENGINES @THANPOLAS LSJSE ARCHITECTURE Separate Core API

    From UI/UX Keep it platform agnostic core.user.register(params);
  8. LARGE SCALE JS ENGINES @THANPOLAS LSJSE ARCHITECTURE Abstract Abstract Abstract

    Create your framework core.analytics.logPageView(‘/contacts’);
  9. LARGE SCALE JS ENGINES @THANPOLAS LSJSE CONS • Steep Learning

    Curve • Long Implementation Time • Slow Initial Page Load • Not SEO Friendly
  10. LARGE SCALE JS ENGINES @THANPOLAS LSJSE PROS • Can Reuse

    In Multiple Platforms • With Node.js Reuse Server Side • Faster / Better UX • Smaller Server Load