TailwindCSS v2.0
blog.tailwindcss.com
TailwindCSS v2.0
1–10 of 474 posts
Re: TailwindCSS v2.0
#2Re: TailwindCSS v2.0
#3Re: TailwindCSS v2.0
#4Re: TailwindCSS v2.0
#5Their marketing is good, they do a primo job at conveying the message in a nice looking way, but the end result is still HTML littered with hundreds classes, that gets hard to maintain and impossible to refactor.
Re: TailwindCSS v2.0
#61. Write old school circa 2008 CSS.
2. Oh shit, it's a real pain in the ass to do layout and make a responsive grid. Let me use a framework. Sweet!
3. Hmm.. its kinda painful to write css selectors all day long. They're reusable but I am having to get out of comfy JS IDE setup to go change some CSS properties in a different file.
4. Tailwind arrives. OMG. This is awesome! Never have to leave the context. Just stack properties as you like and compose your components!
5. HTML looks completely unreadable. It's a goddamn mess.
6. I want to go back to 2005. No frameworks. Just write non-responsive CSS, one for each screen (yeah, you read that right. I don't want to compromise the layout for responsiveness. I'd rather handcraft one for each device size give or take a few pixels). Custom crafted like a piece of fine art. CSS grid/layout is a lot better with css grid and flexbox. Things have improves since the 960-grid days. No frameworks at all and its fucking liberating.
Edit: I currently use reset/reboot css to clean up default rendering + sass (only use variables + mixins). I am happy like a daisy.
Re: TailwindCSS v2.0
#7Geeze, this homepage is truly world-class. Props to the Tailwind team!
I wonder why they used a blog off-domain in the first place. blog.foo.com is so 2005. foo.com/blog makes more sense.
Re: TailwindCSS v2.0
#8For those who don't know, IE11 is the last major release of IE. Between a major frontend framework feeling confident dropping IE, and Apple dropping Intel it kind of feels like the end of an era.