Perhaps surprising: I agree with @slightlylate that the discussion we're having about web performance isn't helping us move forward as a community.
-
-
import() is a nice primitive, but asking every dev to use it manually is asking people to deprioritize it. It's great that the tooling is getting support that we can use in frameworks.
-
That’ll always be tricky. Maybe some Babel plugin that takes <Route> <Component> and rewrites it using an async middle man? Tough to get right.
-
There's already in-framework async points inside of the routing layer. The framework can take one of those points and automatically fetch code associated with a route using import() and some registry or naming convention.
End of conversation
New conversation -
-
-
The best tools are already shipping solutions: https://sapper.svelte.technology/guide#routing https://polymer.github.io/pwa-starter-kit/configuring-and-personalizing/ … https://nextjs.org/docs/#automatic-code-splitting … https://ionicframework.com/pwa/toolkit https://github.com/developit/preact-cli … etc. etc.
-
Yes, there's great work people are doing to flesh it out. As
@AdamRackis said on another subthread, getting everyone standardized around loose modules and putting focus on last-mile tools delivers the biggest benefit to the most users.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.


