3 ms·
It's missing a "P" – it should be "PPRPL": Prerender, Push, Render, Pre-cache, Lazy-load But of course Polymer doesn't do prerender, so it doesn't fit the Goo
by jehna1 10y ago
It's missing a "P" – it should be "PPRPL":
Prerender, Push, Render, Pre-cache, Lazy-load
But of course Polymer doesn't do prerender, so it doesn't fit the Google's image.
It really bugs me that you'll have to load and parse a huge amount of code to get anything rendered on the screen with Polymer.
- ebidel 10y agoIf your app uses a huge amount of code, then yes. But that's really the fault of the app developer. Not the library. What developers often do is pull in a ton of components from the web components catalog and not realize that every component comes with a cost. It's no different than working with libraries. Know the tradeoffs. There are plenty of examples of fast rendering apps that written with Polymer. Check out https://shop.polymer-project.org/ https://shop.polymer-project.org/ and https://www.chromestatus.com/features https://www.chromestatus.com/features, to name two. https://ebidel.github.io/polymer-experiments/polymersummit/fouc/appshell.html https://ebidel.github.io/polymer-experiments/polymersummit/f... is another example that shows how to utilize the "upgrade" feature [1] of the custom elements API. IOW, the browser can render markup without JS ever running. Unfortunately, this is not something that Polymer leverages very much. It requires more work and is less friendly to new developers. [1]: https://developers.google.com/web/fundamentals/getting-started/primers/customelements#upgrades https://developers.google.com/web/fundamentals/getting-start...
- camel_Snake 10y agoThe approach I've seen is to just draw up a skeleton in place of the actual content. It's an older video though: https://youtu.be/g7f1Az5fxgU?t=6m42s https://youtu.be/g7f1Az5fxgU?t=6m42s