Reading ‘Why Tailwind CSS Won’ and was caught off-guard by this comment from Matt Rickard “few developers are writing HTML (instead, they are writing JSX or TSX).” What do you write mostly?
🏳️ Matt Asay declares #OSS#licensing war over
💅 A perfect #Tailwind#UI for your #AI
🔌 Ivan Kuleshov makes a #PoE Mac mini
🤝 #Apple joins the #OpenUSD alliance
🔧 John D. Cook on picking the worst tool for the job
🎙 hosted by @jerod
Some people criticize #tailwind/#tailwindcss, but I still think that it's great and even a good way to learn #css. It solves one fundamental problem of CSS (for me):
You can't go all-in with inline. What about transitions, states, etc?
The docs are also great and help you understand CSS. The docs may even be better than #mdn. Maybe not as comprehensive, but just as clear with good examples.
Another good addition to the corpus of why #Tailwind#CSS is bad news for #WebDev and is actually an indication of deeper concerns about our industry, by Jeff Sandberg:
w koncu wrzucę release mojego self-projektu rowerowo-podróżniczego :) ... i bede musiał zmienić UI. z #tailwind na coś znacznie lekkiego i łatwego w utrzymaniu.
I like Bootstrap, but I also find it funny that the purpose of CSS was to separate styling code away from semantic code (html), only for Bootstrap to shove all that back into the html again.
I started trying out #React and #Tailwind and am overwhelmed how fast I was able to design a website structure. 🤩 I think I will be on the other side of no/low-code.
Maybe it's just the algorithm but it's crazy how all the #webDev "influencers" who are still on Elon Musk's right-wing hate-site are talking about #tailwindcss
@bersling@brad_frost this is all super true. I have used tailwind on a few projects to dial the interface in before a real designer cleaned it up, and it still did look passable.
I've been working on a huge re-make of my whole website!
Among the planned features: a full portfolio/résumé, a technical blog, PDF documentations about various IT domains... and all of that with internationalisation!
😉
Technical stack I'm using: Svelte+SvelteKit on the front-end, Directus and PostgreSQL running in Docker on Alpine Linux for the back-end.
I don't know yet what target I'll use for SvelteKit, maybe bun or deno if either of them works fine :)
It's taking more time than expected, working on so (too!) many stuff in parallel...
I made a few stress tests and asked friends with fast internet if things load quick (everything is a hassle to load for my poor broadband internet BUT my website loads quite fast anyway on it compared to most websites); and I can confirm I'll keep this tech stack: #Tailwind + #Svelte / #SvelteKit + API on #Directus. The SvelteKit part ran like a charm on a #RaspberryPi.
OC Nike Tailwind IV Skepta