I wonder if cdnjs rates are any better. It's too bad more sites don't use CDNs. Nothing loads faster than a warm cache and they remove the unnecessary added co

I wonder if cdnjs rates are any better. It's too bad more sites don't use CDNs. Nothing loads faster than a warm cache and they remove the unnecessary added complexity of managing third-party scripts in source control. It would help if the Open Source dev community could revise their versioning practices to include long-term releases and post those to a CDN. Unfortunately, the current standard is to backward-compatibility-breaking API changes in major versions. API changes that will likely introduce new bugs. It would be cool if we started using a convention where the last update prior to a new major version release is marked as final; thereby deprecating all previous minor versions in that series. OSS developer library projects usually don't have the time/resources to waste maintaining old code anyway. For example use something like a bang to mark the final version. So, when major version 2.0 is released the final major version 1.x gets released as 1! for long-term support and everything previous gets deprecated. It's a win/win. Bang versions get marked as for long term support (ideal for production environments) and everybody who depends on that API version get consolidated into using a single stable branch.