Different kinds of files

Not a single executable, Large assemblage of files

Clean up of resources

Transpile

Bundle

Minify

CSS Preprocessors

CSS Postprocessors / Style transforms

Cache busting - hashes in filenames

Separate dev & prod configs / env / pipeline

webpack

grunt

jspm

coffee

yeoman

jenkins

gulp

broccoli

babel

traceur

cssi

browserify

uglifyjs

VirtualCSS

css in js

brunch

postcss

sass

autoprefixer

less

cssnext

express

node-haste

jest

mocha

jshint

requirejs

systemjs

selenium

phantomjs

istanbul

jsdom

chai

eslint

jscs

When will this stabilize?

When can I start writing code without any of these tools?

The only time you can say that the Web is “good enough” is when you’re building for yesterday’s Web

- Sebastian Markbåge

Tooling is not the problem of the Web.

Tooling is the future of the Web

https://medium.com/@sebmarkbage/tooling-is-not-the-problem-of-the-web-cb0ae1fdbbc6

The conundrum: My framework is better than your framework

Sideways data loading

Deprecating JSTransform and react-tools

React 0.14 release

Relay & GraphQL

React Native

https://github.com/reactjs/react-future

Multi build support - DLL

output: {
  path: path.join(__dirname, "build"),
  filename: "MyDll.[name].js",
  library: "[name]_[hash]"
},
plugins: [
  new webpack.DllPlugin({
    path: path.join(__dirname, "build", "[name]-manifest.json"),
    name: "[name]_[hash]"
  })
]

new webpack.DllReferencePlugin({
  context: path.join(__dirname, "..", "dll"),
  manifest: require("../dll/js/alpha-manifest.json")
}),

https://github.com/webpack/webpack/tree/master/examples/dll-user

https://github.com/webpack/webpack/tree/master/examples/dll

Value

Promise

Iterable

Observable

var a = 1;
var b = 2;

var p = fibonocciGenerator()
  .filter(i => i !== 0)
  .map(i => 5/i);
p.forEach( // ...

a = asyncA()
  .then(() => ...)
b = asyncB()
  .then(() => ...)

var p = fibonocciAsync()
  .filter(i => i !== 0)
  .map(i => 5/i);
p.forEach( // ...

Sure, we'd want that. And sweet.js can handle a lot (it handled classes, destructuring, and other ES6 features before they were implemented in popular engines). This may take a while. Best way to ensure this outcome: more people learning, using, and helping improve sweet.js.

- Brenden Eich (es-discuss) 

Is it becoming a spec?

When will macros get into JavaScript?

Will the core get slimmed in favour of macro-definitions?

Boopathi Rajaa

@heisenbugger