Software is required to "help" with CSS. Only seems reasonable that you'd need to install said software. Installing the Tailwind package provides the Tailwind software. So when you build your website that uses the `block` class, that class actually exists somewhere - because you pulled it in with the installation via the package manager.
Surely we can agree that distributing shared libraries via a package manager is a good practice, no?
CSS is text. What's wrong with copying the required CSS stylesheets over and including (importing) them from your own stylesheets?
Surely we don't need a "package manager" and a "build chain" for this?
Then again, I'm a person that writes any web-related code (HTML, JS, CSS, etc.) by hand.
Where did we take the left-turn of not understanding how things work on the actual tech level? These tools hide all of the actually required steps to npm-infested bloat.
x86 ASM is text but we don't build software by copying and pasting it. While the underlying thing we ship is CSS, that doesn't mean we can't add tooling layers to make it easier or more efficient. While it's totally allowed to write by hand, most frontend web developers I know are very comfortable with NPM, and indeed having dependencies consumed from a package manager is often preferred.
> Surely we can agree that distributing shared libraries via a package manager is a good practice, no?
At one point, long ago, you could just download a file, reference it in your index.html, and use it without ever having to worry about updating this package. It had its flaws, but it also had many advantages compared to having an external dependency that might conflict with your version of Typescript, or being highjacked by bad actors.
I don't diss the concept of package managers at all, but there are lots of case where vendoring an external package is preferable than adding it as a dependency.
The latter one is the most plausible explanation I’ve read yet. Basically, they can’t give away the keys to the kingdom because they’re for the entire kingdom, not just the unsold inventory.
I have an experimental aircraft, a Vans RV-14, that I've been working on for far too long. I have all the expensive parts on hand, I just need to finally finish putting them together.
Surely we can agree that distributing shared libraries via a package manager is a good practice, no?
reply