The next version of Adobe's apps will require you to pay that $21/month Pantone fee, or any Pantone-defined colors in your images will render as black. That's true whether you created the file last week or 20 years ago.

Doubtless, Adobe will blame Pantone for this, and it's true that Pantone's greed is the root cause here. But this is an utterly foreseeable result of Adobe's SaaS strategy.

Again I thought about going the JavaScript route, but I’m trying to keep to the Web’s slower pace layers as much as possible in this project for maximum compatibility over time and technology.

then I thought I heard about people using npm to do the same thing for client-side code. “That can’t be right!” I thought. I must’ve misunderstood. So I talked to someone from npm and explained how I must be misunderstanding something. But it turned out that people really were treating client-side JavaScript no different than server-side JavaScript. People really were pulling in megabytes of other people’s code to ship to end users so that they could, I dunno, left pad numbers or something. Listen, I don’t care what you get up to in the privacy of your own codebase. But don’t poison the well of the web with profligate client-side JavaScript.