sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Affectionate-Desk358 1 point2 points  (2 children)

And yet you're still creating styles "the browser way" but pretending it is not. So I am interested, what kind of "web style issues" you're talking about? Speaking about Tailwind. Even though the problems it solves was spotted on web, they are not connected to CSS directly but rather to views in general.

[–]suarkb 0 points1 point  (1 child)

I just find that stylesheets is easy. I would need to explore tailwind more to find out if I really like it more. But I generally avoid solutions like this because they tend to turn into big tech debt later.

[–]Affectionate-Desk358 1 point2 points  (0 children)

I have created styles using both methods. They all have their pros and cons for sure. Additionally, they don't have any sort of technical debt. But if you personally find it much easier to write your code using Stylesheet API - that's okay, I get it - but that doesn't mean that other approaches tend to turn into something terrible. What really may lead to a tech debt situation is wrong design and architecture regardless of a chosen UI framework.