But a package manager is a hundred-ton hammer when all you need is to decorate your little html page that you hand-edit and push with rsync.
You wanted a fun website but what you got is a dependency manager with a production CI/CD pipeline taking 15 min to check that yes, the sentence you wrote can in fact be written.
Package managers work, but isn't there some middle ground that doesn't involve depending on a runtime that itself is continuously updated ?
> isn't there some middle ground that doesn't involve depending on a runtime that itself is continuously updated ?
jsDelivr is pretty nimble in the regard. It mirrors GitHub and npm (and caches and (optionally) minifies the result) so depending on the project, you can get a specific release, or just pull from the master branch, by simply changing the URL of the CSS file.
>But a package manager is a hundred-ton hammer when all you need is
Unfortunately, this is the state of much of software development today. It's why most webpages are enormous. It's why massive increases to speed, processing power, and communication bandwidth have resulted in no real net increase to web-browsing speed for the last 10 years.
It's why massive increases to speed, processing power,
and communication bandwidth have resulted in no real
net increase to web-browsing speed for the last 10 years.
nor to developer productivity, either. I feel that has massively decreased in the last decade.
There are clearly cases where complex build/CI/CD pipelines make sense, but people now believe they need big enterprisey FAANG-scale solutions even when they don't.
You wanted a fun website but what you got is a dependency manager with a production CI/CD pipeline taking 15 min to check that yes, the sentence you wrote can in fact be written.
Package managers work, but isn't there some middle ground that doesn't involve depending on a runtime that itself is continuously updated ?