↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

The future of JavaScript is (almost) now

JavaScript is now used across browsers, complex web apps, mobile development, server-side programming, and IoT. The article says its growth comes from the ecosystem around it, from frameworks and tools to new runtimes and the coming ES6 standard.

Reading notes
#

  • JavaScript moved from an Internet fad to a language used in browsers, web apps, mobile, server-side programming, and IoT.
  • Its ecosystem includes third-party and open-source libraries, frameworks, tools, implementations, and superset languages.
  • jQuery helped Web developers with client-side scripting, and later plug-ins filled gaps in the language.
  • Gartner’s Danny Brian links JavaScript’s growth to the ubiquity of the browser across desktop, mobile, native desktop apps, and IoT devices.
  • Ecma is set to release ECMAScript 6, a major update after more than 15 years without one.
  • ES6 adds modules, classes, and other changes meant to support larger and more complex Web applications.
  • Browser providers are expected to implement ES6 features and optimize them in their JavaScript engines and developer tools.
  • Angular, CoffeeScript, TypeScript, Backbone, Ember, Grunt, Cordova, Bootstrap, HTML5, Node.js, and V8 are presented as part of the wider JavaScript ecosystem.
  • Andrew Connell says JavaScript began as browser glue, but frameworks and broader adoption made it much more than that.
  • The Google and Microsoft collaboration on Angular 2 and TypeScript is described as a sign of broader cooperation around ES6 and Web components.
  • JavaScript runtimes such as V8, io.js, and Node.js support cross-platform development on desktops, servers, embedded devices, and IoT.
  • Evergreen update cycles in Chrome, Firefox, and Microsoft Edge reduce the problem of outdated browsers.
  • Enterprise adoption has been slower, but server-side developers and Microsoft developers are warming to JavaScript through TypeScript, JSLint, and JSHint.
  • The article says ES6 standardization gives teams more confidence about JavaScript’s direction, even before its long-term technical impact is fully known.