← Back to context

Comment by eviks

5 hours ago

> It's pretty easy. Open the inspector, select an element and you will find all the styles that apply.

Of course it's not easy, 80% of that list will be some garbage like global variables I would only need when I actually see them in a style value, not all the time.

The names are often unintuitive, and search is primitive anyway, so that's of little help. And the values are just as bad, with --vars() and !important needless verbosity in this aborted attempt of a programming language

Then there is this potentiality more useful "Computed" styles tab, but even for the most primitive property: Width, it often fails and is not able to click-to-find where the style is coming from

> Also styles are semantics like:

That's another myth. You style could just be. ReactComponentModel.ReactComponentSubmodel.hkjgsrtio.VeryImportantToIncludeHash.List.BipBop.Sub

What does that inspire in you when you read it?

Someone is using Tailwind (and the likes) and/or CSS-in-JS. Which I dump squarely in the weird tools.

  • What do you dump the other 99% of the poor designs and papercuts on? But at any rate, shifting blame doesn't help you make a hard system easy by citing a broken tool