currently there are 4 CDNs that are being called for different javascript libraries. this means that there are 4 different third-party requests being made on each load.
why do it?
the advantage of unifying all of the libraries from a single provider is that all of the requests can be served off a single connection if the connection is made over HTTP/2 essentially making the load times at least 2 times faster.
why jsDelivr?
jsDelivr has a wide network spanning multiple caching network providers whereas the other providers rely on a single caching network ( unpkg, cdnjs - cloudflare, github - fastly ). while technically all the requests could probably be served from the same backend cache, since the requests are being proxied via different domains, naturally, they have to go through different connections. if all the requests are proxied through the same
domain and via HTTP/2, the requests can all be served via the same connection making the page load faster.
other changes
~- synced the library version for ace/ext-language_tools with the loaded ace.js library`~
updated frontend libraries - ace and react to latest versions
vendored in corresponding scripts for-offline
removed an irrelevant check for non-macs in scripts/build/build-offline-dev.sh ( tested on ubuntu 20.04 LTS and debian 10 buster ).
~### room for improvement~
~- react and babel-polyfill libraries could be upgraded to the latest major versions. since I wasn't sure whether this would cause any breakage in the application, I didn't attempt an upgrade. I just used the already existing version but just changed the provider URL. Maybe a minor version upgrade ( react ) would do much harm? ( I didn't want to take the risk since it was react )~
~I could however attempt to upgrade to the latest versions if given approval. I just don't know the application well enough to know where to look for breakages.~
currently there are 4 CDNs that are being called for different javascript libraries. this means that there are 4 different third-party requests being made on each load.
why do it?
the advantage of unifying all of the libraries from a single provider is that all of the requests can be served off a single connection if the connection is made over HTTP/2 essentially making the load times at least 2 times faster.
why jsDelivr?
jsDelivr has a wide network spanning multiple caching network providers whereas the other providers rely on a single caching network ( unpkg, cdnjs - cloudflare, github - fastly ). while technically all the requests could probably be served from the same backend cache, since the requests are being proxied via different domains, naturally, they have to go through different connections. if all the requests are proxied through the same domain and via HTTP/2, the requests can all be served via the same connection making the page load faster.
other changes
~- synced the library version for
ace/ext-language_toolswith the loadedace.jslibrary`~aceandreactto latest versionsfor-offlinescripts/build/build-offline-dev.sh( tested on ubuntu 20.04 LTS and debian 10 buster ).~### room for improvement~ ~-
reactandbabel-polyfilllibraries could be upgraded to the latest major versions. since I wasn't sure whether this would cause any breakage in the application, I didn't attempt an upgrade. I just used the already existing version but just changed the provider URL. Maybe a minor version upgrade ( react ) would do much harm? ( I didn't want to take the risk since it was react )~ ~I could however attempt to upgrade to the latest versions if given approval. I just don't know the application well enough to know where to look for breakages.~related : https://github.com/tddbin/katas/issues/105