What is the next big thing in frontend development?

stereobooster - Sep 13 '18 - - Dev Community

Photo by Joshua Earle on Unsplash

I had some thoughts about this post quite some time but wasn't sure how to frame it. This tweet helped me

Subseconds build time

Did you see OCaml (you may know it as ResonML or BuckleScript) compiler in action? It caches everything as binary, so consequent builds are like 20 milliseconds. This is totally astonishing. Can not wait to see something like this for JS.

Maybe https://pax.js.org/? Who knows...

Automatic code splitting

Related Parcel RFC

This will pair nicely with React Suspense

Per browser builds

@sitnikcode started this crusade called browserslist (correct me if I'm wrong). Imagine you specify which browser you want to support and compiler (transpiler) will provide builds for each browser in the list with all required polyfills with all required changes to CSS and you can use small script in Lambda@Edge or Cloudflare-Worker to serve appropriate assets at the edge of CDN. Or compiler will fail if your code is not compilable (transpilable) for given browsers.

Also, it would be nice if it would compile it down to ES6

For the reference, here is how builds per browse can look like preact-hn webpack config

What do you dream about?

What is the most expected thing for you?

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .