3 ms·
Tailwind CSS makes complete sense for folks who are deeply conditioned to NPM hell and stockholm-syndromed to godzilla JS build processes that makes Heavy Enter
by lenkite 6y ago
Tailwind CSS makes complete sense for folks who are deeply conditioned to NPM hell and stockholm-syndromed to godzilla JS build processes that makes Heavy Enterprise Java look like a dancing hummingbird.
The rest of us who like our lean mean HTML and CSS will stick to the old-school way of doing stuff - separating styles from our HTML with clean classes and markup with no need for a build step just to create basic stylesheets.
- corytheboyd 6y agoIgnoring your rude dismissal of the NPM ecosystem, do you actually create sizable web pages without some sort of build tool? How? Duplicating entire HTML documents and adjusting any relative paths, etc.? I’m really not trying to attack your way of doing things and “force” a “shitty” build process on you, but I often see this dismissal thrown around without any actual substance and it’s honestly getting very old.
- lenkite 6y agoOne can stick to plain and fast SSGs without bringing NPM into the picture. Maintain dependencies in your repository. I think there is extraordinary evidence been presented over the past several years to derive the judgement that NPM is terrible. It is a dismissal with very real and actual substance. One just needs to go through the several dozen critique on HN alone - all supported with a truckload of data, horrendous experiences and security vulnerabilities. Frameworks which marry themselves to this ecosystem are OK for those developers who are already in NPM hell. My apologies for your suffering - but the rest of us don't need to join the cult of doom.