From the buzz on Twitter and blog posts, you could feel that ECMAScript 6 was finally coming. It has many things we’ve wished for for years, so it makes sense to start new projects with it in mind.
Others have written in depth about various ECMAScript 6 features. I’d like to focus just on one: module loading. There is no common way to load your ES6 modules natively in the browsers. For example babel, has support for three different module loaders. There was a
System dynamic module loader included in the ES6 specification, but in the end it was removed and work continued as WhatWG loader spec. Yes, you can define modules, classes, export them, and import them, but there is no way how to load them across files. This also means that the
Getting your API launched can be a big challenge – and not just technically! Often there are open strategy, technical, business model and other questions which need answers before you can take the plunge. Or maybe you have an API and you’d like it to fly higher!
To help work through these questions and give you the best start possible, sign up for 3scale before the end of the weekend and you’ll get a FREE API Strategy Session with key people from the 3scale team. We’ll share experiences from the field and drill down into specific challenges you want to cover (guaranteed no sales pitches!).
Sign up (accounts are Free) before the end of Sunday 1st of July to take advantage of this offer!
We can cover:
Overall API Strategy: What is worth releasing, when and how – how to generate value rather than simply extra cost + how to communicate …