4 ms·
I think you're confused. What they're saying is it's a reinvention of ```css .card { ... } ``` ```html <div class="card" /> ``` RATHER t
by culi 3y ago
I think you're confused. What they're saying is it's a reinvention of
```css
.card {
...
}
```
```html
<div class="card" />
```
RATHER than a reinvention of
```html
<div style="..." />
```
- matheusmoreira 3y agoI meant this tailwind framework looks like a reinvention of style="..." inline styles. <div class="block">...</div> <div style="display: block;">...</div> https://tailwindcss.com/docs/display https://tailwindcss.com/docs/display So we've gone from inline styling to separating markup and presentation with CSS but now we've gone back to inline styling.
- porridgeraisin 3y agoThe whole separating markup from presentation doesn't quite work for any non trivial web-app type of webpage. Because the presentation affects markup. You'll have to add wrapping divs to accomplish any kind of complex layout for example. Once you can't separate it in your mental space, it doesn't matter that its in two different files.
- matheusmoreira 3y agoBut the solution is to turn CSS into inline styles? > You'll have to add wrapping divs to accomplish any kind of complex layout for example. I don't know about that. I think selectors are pretty powerful. Have managed to avoid littering the HTML with structural nodes by using them creatively. CSS has gained a huge number of features since I first learned it, there's even better ways to do stuff now.