top | item 35355975

(no title)

Okawari | 2 years ago

It does feel radically different from the more traditional way of doing things, but I think it is for the better. I wouldn't call it abusing.

Tailwind together with view components has changed how I structure my code and it creates quite a bit less work than my company's old more BEM centric approach where we would create lots of tightly coupled CSS code controlled by variables and such. I find it easier to grok as well, because I don't need to reference SCSS files to determine the implications of applied classes when debugging or similar.

Now most of the component requirements can be codified in a few classes in our view component instead. Does it look kinda ugly, yeah sure. But I'm sure it has saved quite a few hours for me since I switched over.

This might just be because old process was even worse, regardless it has been a very positive change for me personally.

discuss

order

No comments yet.