41–50 of 318 posts
Earlier quoted context omitted.
Is jumping between files supposed to be difficult or something?
Is staying in one file supposed to be difficult or something?
Because Tailwind is so low-level, it never encourages you to design the same site twice. Some of your favorite sites are built with Tailwind, and you probably had no idea.
2015 is good enough. For example instead of grid center, one can use flex and margin auto. If you are building really nation-wide products, there are still a lot of guys in corporate with old windows (where even chrome stopped updating like win7). Or, you know, old or poor people with PC from 2008. Also don’t forget guys with mobile phones: not like one could easily install a browser there. Especially on phones which…
It would be utterly negligent to still be running IE in a corporate environment. It’s a huge security risk.
CSS in 2025: Let's write html inlined styles as if it was 2005 and separation of formatting/representation was never invented. I talk of tailwind, of course.
Earlier quoted context omitted.
Wait until you see React & JSX... At least html and CSS are both presentation. React/JSX now confuses presentation and business logic.
React is great for MVVM indeed. Who is still using MVC in 2026?
Earlier quoted context omitted.
If you move the data (the M and the C) entirely out of react, and only pass it in via props, there would be only one place — the root react node — where the props could get into react. Is this what you have in mind? Or are you envisioning multiple root nodes?
With signals you can avoid the prop drilling. I think signals can help a lot with this approach
So where are we at with utility libs (tailwind/tachyon) vs inline css in js vs preprocessors (sass/scss) vs vanilla modern css?
Tailwind works for your team? Go for it.
Inline CSS for your solo project? By all means.
Still stuck on SASS? It'll keep working just fine.
All in on modern CSS? More power to ya!Earlier quoted context omitted.
Wait until you see React & JSX... At least html and CSS are both presentation. React/JSX now confuses presentation and business logic.
React is great for MVVM indeed. Who is still using MVC in 2026?
CSS in 2025: Let's write html inlined styles as if it was 2005 and separation of formatting/representation was never invented. I talk of tailwind, of course.
The deadest horse in web development is the myth of “separation of concerns”
It admittedly does not do a good job at being very DRY but I think that’s poorly applied to HTML/CSS in general, and the most DRY css is often over abstracted to the point of becoming nigh uninterpretable.