Isn't the example on how to make the referenced file better another contribution to the pool of "broken by default" images?
Either that or I don't get the argument.
I would argue that the comfort of using jQuery comes at the cost of speed and obfuscation. I stopped using jQuery about 2 years ago and for the most part had no problems whatsoever even when I was forced to support IE9.
Also I found that searching http://youmightnotneedjquery.com/ helps a lot when deciding how to implement certain features.
Isn't glacier the product which seems very cheap if you only look at the storage cost but is extremely expensive when retrieving the data? I remember reading an article by someone who had to pay something like 2000 USD to restore his data which wasn't even in the terrabytes.
Although I might be mistaken here.
Amazon says the original retrieval pricing matched their cost, but was hard to grok and easy to run up a huge bill if you didn't use it carefully and extract data patiently.
They realized that was a mistake and significantly streamlined the pricing, and with this Deep product it doesn't look like they've even supporting the original somewhat opaque Glacier API, just S3.
If you're patient and can wait 48 hours for data, bulk storage retrieval is cheap at $0.0025/GB and $0.025 per 1000 requests. The standard AWS $0.09/GB egress is the really big cost, but if you have enough data you can mitigate that with a Snowball. Not a big issue if you're recovering from a catastrophe that destroyed all your local backups, it looks great as insurance for those of us with modest time to recovery desires.
Today I could easily afford that. But thinking back a few decades when I was young and didn't have much money at my disposal I would say using stuff for free isn't that bad.
Especially when piracy is so much easier than getting your account suspended for using an adblocker.