New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Register at CDN to increase ease of deployment #233

Open
holtkamp opened this Issue Aug 1, 2017 · 4 comments

Comments

Projects
None yet
4 participants
@holtkamp

holtkamp commented Aug 1, 2017

To stimulate adoption and increase ease of deployment during production, registration of the dist (minified, related: #232) files at a CDN like http://www.cdnjs.com is useful.

Will try to submit it to http://www.cdnjs.com and report back here

@csswizardry

This comment has been minimized.

Show comment
Hide comment
@csswizardry

csswizardry Aug 31, 2017

Whilst not a bad idea, I worry about putting critical (as in, on the critical path, as opposed to ‘important’) code on an external domain. The network overhead (DNS, TCP, TLS), particularly on high-latency connections, could introduce a slowdown greater than the one loadCSS is trying to mitigate.

It is in my opinion—and past experience—that critical resources such as these should be served from the host domain whose connection is already open. I’d be very interested in the discussion around this, though!

csswizardry commented Aug 31, 2017

Whilst not a bad idea, I worry about putting critical (as in, on the critical path, as opposed to ‘important’) code on an external domain. The network overhead (DNS, TCP, TLS), particularly on high-latency connections, could introduce a slowdown greater than the one loadCSS is trying to mitigate.

It is in my opinion—and past experience—that critical resources such as these should be served from the host domain whose connection is already open. I’d be very interested in the discussion around this, though!

@evromalarkey

This comment has been minimized.

Show comment
Hide comment

evromalarkey commented Dec 28, 2017

@odahcam

This comment has been minimized.

Show comment
Hide comment
@odahcam

odahcam Dec 28, 2017

All NPM packages are automatically included in some CDNs, like UNPKG.

Example:

My opinion: this implementation shouldn't be a critical thing and if anyone wants to use the lib from a CDN this person can use, but also should know (maybe a note in the readme could do this) the colateral effects pointed by @csswizardry.

odahcam commented Dec 28, 2017

All NPM packages are automatically included in some CDNs, like UNPKG.

Example:

My opinion: this implementation shouldn't be a critical thing and if anyone wants to use the lib from a CDN this person can use, but also should know (maybe a note in the readme could do this) the colateral effects pointed by @csswizardry.

@evromalarkey

This comment has been minimized.

Show comment
Hide comment
@evromalarkey

evromalarkey Dec 28, 2017

yeah, I'm using it only to fetch it with php and inline as css (or you can http/2 push it), it's much easier to maintain versions this way.

evromalarkey commented Dec 28, 2017

yeah, I'm using it only to fetch it with php and inline as css (or you can http/2 push it), it's much easier to maintain versions this way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment