3 ms·

I’m so confused why people are ragging on this. Why is this considered detrimental? Looks pretty good to me…

• llbbdd 1y ago
  It's a post about web development on HN. Half the comments will rag incessantly, half will talk about how the web should go back to being a delivery mechanism for documents only like it's 1995 forever, someone will rant about Google for some reason. It's a neverending nightmare.
  • typpilol 1y ago
    Don't forget the people that have to tell us how much they hate JavaScript on every single web dev post too
• robertoandred 1y ago
  People who don’t understand the problems CSS has to solve are opposed to CSS solving those problems. Sure it can all be stuffed into Tailwind classes!!
  • ezeekqil 1y ago
    ¯\\_(ツ)_/¯
  • lerp-io 1y ago
    the problem is that if there was a tailwind-like replacement for css, nobody would ever use css again lmao.
    • djxfade 1y ago
      It is, it's called inline styles
• JadeNB 1y ago
  I'm no expert in this domain, but I suspect it's less "this is a bad problem to solve" and more "every solution to a problem moves farther away from the ideal simplicity of a markup langage." (I'm not weighing in on the validity of this position, just reporting what I perceive the position itself to be.)