The criticisms against #tailwindcss are deserved in most cases.
But the put-downs against developers who use tailwind make me cringe. Things like "they use tw bc they couldn't be bothered to learn the cascade" that I see repeated over and over on here are bad. It paints a picture of the purist #CSS community as completely oblivious and uninterested in why tw came about in the first place.
Guess what: Tailwind is a cry for help. Blaming #webdev that use it isn't the win you think it is.
Hey! I’m a senior front-end developer looking for my next medium- to long-term freelance role.
I have 14 years of experience working along the full web development stack, usually with #JavaScript, #TypeScript, #ReactJS, #NextJS and #TailwindCSS. I often work with e-commerce and healthcare clients. Once, I helped turn a household appliance into a smart IoT prototype.
My website/blog has always had dedicated light and dark themes (thanks to using Tailwind from the ground up). It came to my realization, however, that the proper theme may not render by default based on people's OS preferences. That's why I added this small cosmetic touch that will hopefully help a bit.
I’ve been working the last couple of days on a side project using #golango#htmx and #tailwindcss. It is so refreshing to build a web app without all the fuzz. No frameworks, no package manager, no front-end server and most importantly, no JavaScript. My build process, if you can call it that, is a four line Makefile. Just me fighting #css and hand crafting REST request to #couchdb.
My portfolio got a visual and functional refresh during our recent workation in Denmark. Looking at it now, I feel excited to make this the home for all my educational content going forward.
I might have to take the timestamps off until then.
Planning a new article on #Kotlin, #Javalin, #HTMX, #TailwindCSS, #Playwright. Probably #Gradle, although I'm more and more interested in rediscovering #Maven. Maybe #RetroFit to include some OHS/ACL (#DDD Context Mapping), but maybe this is already a lot to combine just for an exploration.
Both #TailwindCSS and #TachyonsCSS take an atomic approach to #CSS. However, I am trying to understand why the former is more popular when if I want to see an example of say a button, it expects me to pay for access to #TailwindUI, whilst the latter has loads of free examples in the documentation, or have I missed something?
I realised it has taken about 8 years to finally find a tech stack that I am settled on and happy with so that I am not looking around and wondering if there is something better.
I fear that a LOT of people are going to start using #HTMX for the same reason they use #TailwindCSS; it saves them from having to learn a language they don't like. #javaScript#css
After a few months on my first Tailwind project I can say it has lived up to my expectations: nice framework for those without prior CSS experience, or for JS or backend devs, but not my thing. I can live with it but I’d rather not if given the choice. Maybe cause I’ve been pro CSS since the beginning, I don’t know. Just seems to not click with the vibe of what CSS really stands for #webdev#css#frontend#tailwindcss
@jeffsheets I find that it’s just a different way of accomplishing the same things. You also really need to understand the fundamentals of #css to get the full benefit of #tailwindcss. You still need to grasp the concepts like padding, margins, backgrounds, borders, flex, grid, etc. I have a fairly extensive background in CSS and I really like Tailwind. Maybe I’m just an outlier.
🤔 Armon Dadgar announces #HashiCorp's #BSL future
🏆 Matt Rickard on why #TailwindCSS won
🕴️ WarpStream is like #Kafka directly on top of #S3
🧩 Vadim Kravcenko’s guide to managing difficult devs
📢 Russ Cox gives an update on #golang 2
🎙 hosted by @jerod
"HyperUI è una raccolta di componenti CSS Tailwind che possono essere utilizzati nel vostro prossimo progetto. Con questa serie di componenti, potrete costruire il vostro prossimo sito web di marketing, la vostra dashboard di amministrazione, il vostro negozio di e-commerce e molto altro ancora."
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.
The most tiresome thing in #webdev is picking the techstack. So many choices to make: plain #javascipt or a more restricive language like #typescript , which ofc is often depending on the overall frontend framework to use: #svelte , #react , #preact , #solidjs ?
Or do one completly deviate from the classical way and use rather a techstack via #wasm , such as #rust with #dioxus ?
So many questions to answer and that still is only the js side of things, you then have to think about your css framework (if you want to use something like #tailwindcss ), your font choices, and ofc if and what styling library you actually use ontop of our frontend framework; e.g. #bootstrap , #blueprintjs , #tabler.io and so on.... which also often depends on your framework of choice!
I regrettably was unable to attend the second day of #nbpy and am sad to have missed it, but I thoroughly enjoyed my first day there.
My talk "Back to the Future of Hypermedia in Python" is now online. I provide an overview into a hypermedia-driven web application and introduce the PyHAT stack (python hypermedia tailwind).