We have been coding Javascript since its earliest versions, and have enjoyed tracking its evolution over time. By default we deliver jQuery-based code, but code just as well in native Javascript if required.

The tradeoff using a framework like jQuery is well-known: development time vs. execution speed. Native Javascript will run faster, and generally in fewer lines of code. But the jQuery layer rapidly addresses common goals such as cross-browser compatibility, DOM manipulation, and Ajax calls.

Like a majority of developers, we enthusiastically choose jQuery for most website development, and reserve native Javascript for specialized cases, which either don't fit the typical jQuery scenario, or require more efficiency. Games, physics simulation, or advanced image morphing, might be some examples where developing a set of classes in native Javascript makes a lot of sense.

Whether native or jQuery, our javascript code always follows best practices:

  • Unobtrusive
  • Object-Oriented
  • Packaged as a plugin when applicable


Most sites we launch involve at least some jQuery programming, at the minimum providing elegant client-side form validation or cosmetic enhancements such as tooltips or accordions.

We enjoy taking things further, really getting the best User Experience possible with Ajax, lazy loading of images, unobtrusively delivering a rich experience without jamming too much bandwidth on page load, etc. We take pride in what we do with the jQuery framework, pushing the limits of UI.

Native JavascriptjQuery
Faster executionFaster development
Lighter (no library to load)Provides more features ready for use (slides, etc...)
Supporting older browser requires custom codeStandardized library, common to many sites around the world

Still curious?

Would you like to discuss options for your site? For other projects?

Contact us