3 ms·
I’d love to poke at this if you don’t mind. One advantage of downloading everything is that you only download it once. If the user is enabling/disabling feature
by gcr 3y ago
I’d love to poke at this if you don’t mind. One advantage of downloading everything is that you only download it once. If the user is enabling/disabling features, you’ll have to then re-ship a new js bundle, no?
- eddd-ddde 3y agoAlso my thoughts. With something like Qwik you get tiny chunks that you only download when needed and are highly cacheable. All automated!
- fastest963 3y agoNot impossible for us to use something like that but remember that we are a vendor that sits on customer sites with very limited objectives we aren't powering a full-on webapp or multi-page experience. Typically we want to load our experience/component as quickly as possible after some sort of user interaction and the user interaction might have been from the customer's app/website.
- eddd-ddde 3y agoAh I see, that makes a lot of sense.
- fastest963 3y agoAt the scale we operate at we would probably have billions, if not tens or hundreds of billions, of downloads before any feature status is changed. Typically our customers are not turning on and off features very frequently.