Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Coming to Terms with Tailwind

johanronsse.be

Post reply on HN
Print view View original

81–90 of 117 posts

Re: Coming to Terms with Tailwind

#81

Post by nickjj »

If anyone is on the fence with pre-made UI components around Tailwind I just put out a video the other day reviewing Tailkit (it has 300+ Tailwind components, layouts and pages). The author was also kind enough to giveaway 2 copies which is covered in the video. That giveaway ends Saturday July 10th.

The video is here: https://nickjanetakis.com/blog/reviewing-tailkit-300-tailwin...

I've been using it in a few projects and it's really nice. There's no affiliate links or kick backs for promoting Tailkit either, I'm just a happy user.

Re: Coming to Terms with Tailwind

#82

Post by sgt »

mrcwinn wrote: post #32

As someone who's building an MVP, I just want to express how unbelievably grateful I am for Tailwindcss, Tailwindui, Heroicons, and HeadlessUi. Fantastic work.

Agreed. I bought TailwindUI not because I am interested in how the UI actually works or even writing custom components from the start, but rather because I wanted to get a professional look initially and focus on the business logic of the app. UI isn't the most important thing, after all.

Re: Coming to Terms with Tailwind

#83

Post by sgt »

shams93 wrote: post #13

Well I have to support legacy browsers so I won't be using tailwind, but that doesn't mean I won't "cheat" on css by using material design lite. I literally have a 14 day deadline with no designer on hand. I know I need a framework its just in my case the less sexy MDL is more useful because it has great support for legacy browsers.

Most people who think they need to support legacy browsers don't actually need to. Evergreen browsers upgrade themselves. Clients should also know that running an ancient browser poses a security risk, so you could use that as reasoning, too.

Re: Coming to Terms with Tailwind

#84

Post by kjksf »

Wolfr_ wrote: post #61
leephillips wrote: post #26

One sentence in the article suggested that, ideally, people making websites would just learn CSS , but since that‘s an unrealistic expectation (why?), Tailwind can be useful if you have big team of “front-end engineers” who don’t quite understand the markup languages that they use in their jobs. I can’t argue with that. But it suggests that if you work alone or in a small group, actually learning CSS might make more…

I'll try and clarify what I mean here. Tailwind seems to appeal to devs who feel they never fully grasped CSS + design. Because it provides a copy-pastable subset of reliable classes where you end result will look good. As a company we are often hired to fill a knowledge gap (exactly in design and front-end). The nature of agency work is to leave a deliverable for the client to work with. My idea is that when the pro…

Thanks.

What I needed today is for a rando on the internet to call me stupid, a dev who doesn't fully grasp CSS + design.

I use tailwindcss and so do other devs. Many of those devs are better than me and you.

Instead of assuming that everyone who disagrees with your choices is stupid, maybe reflect on popularity of tailwindcss and assume, in an Ockham's Razor kind of way, that it's a good technology. Even if it's not a technology that you personally want to use.

Re: Coming to Terms with Tailwind

#85

Post by lloydatkinson »

> after I wrote a bit of criticism that got popular.

Nah, you was just jumping on the bandwagon of hating on Tailwind without even trying to understand the fact you are meant to use components with it.

Given that this bandwagon regularly attacks Tailwind (or anything modern in fact) and the fact that you tweeted completely antagonistic and unneeded "refactor tailwind out of your codebase" to someone who was showing an interesting way of doing animation in Vue, I can't blame them for blocking all the N number of accounts that are harassing them. Anyone is in their rights to block someone that is antagonistic or nasty or just generally hurtful on a constant basis to them.

Arguing against something knowingly in bad faith (e.g. stating incorrect facts about X to hate on X) is 100% antagonistic. Actions have consequences?

https://twitter.com/wolfr_2/status/1280949237820383232

And even now you continue with "Now, getting blocked by a person, that’s one thing. I guess Adam’s coping strategy with criticism was an “I don’t want to hear it.”. Yeah, again, I can see why he blocks accounts of people like this. Flippantly phrasing it as "Oh, I guess they don't like being criticised" shows a lack of appreciation for why someone might block someone. Because they just don't want to put up with someone's shit. Who can blame them?

> I don’t know if I was entirely productive at first because I first had to shake up my dev stack to add in support for PostCSS, PurgeCSS and figure out all kinds of Tailwind specific things.

Fortunately you don't need to purge anymore, as it instead creates the CSS file you need upfront instead of purging it after.

Re: Coming to Terms with Tailwind

#86

Post by tshaddox »

sli wrote: post #78
echelon wrote: post #74

Earlier quoted context omitted.

This is a conscious decision. I think Twitter is engineered to make people angry at each other.

Simply logout or use a private browsing window if you want to see the public posts of someone who's blocked you. It's really, really not a big deal at all.

That's why it's a stupid decision from Twitter. Twitter could say "type your username backwards to see this tweet" and you could say "just type your username backwards, it's really not a big deal." It would still be a stupid decision from Twitter.

Re: Coming to Terms with Tailwind

#87

Post by pantulis »

leephillips wrote: post #70
cageface wrote: post #62

Earlier quoted context omitted.

Here's a tip: if a lot of smart, informed people have a very positive view of a technology but it doesn't click for you, it may not be the right tool for you but it very likely is not a "sign of dementia".

Oh yeah? What about C++?

C++ will gladly create the dementia for you.

Re: Coming to Terms with Tailwind

#88

Post by soneca »

cldellow wrote: post #14

> Then there comes the point where I have to use Tailwind for work and I am blocked by an offical account and – that feels kind of stupid? Getting blocked by a company entity for having an opinion is kind of… strange? I don't understand comments like this. You still have access to tailwindcss.com for documentation. The company doesn't owe you space in their social media conversations. The company has real customers a…

I agree. I see nothing “strange” of a very small company blocking criticism on Twitter (even if it is a fair criticism). A bank have thousands of employees, tens of which (maybe even hired agencies) have a full time job handling social media.

A small company has zero people whose full time job is to handle social media, so it makes sense for them to clean their feed up anyway they like it. I also see zero effect on their business.

Not sure why the author made a big thing out of this block too. It is not a big deal for neither involved

Re: Coming to Terms with Tailwind

#89

Post by yohannparis »

kjksf wrote: post #84
Wolfr_ wrote: post #61

Earlier quoted context omitted.

I'll try and clarify what I mean here. Tailwind seems to appeal to devs who feel they never fully grasped CSS + design. Because it provides a copy-pastable subset of reliable classes where you end result will look good. As a company we are often hired to fill a knowledge gap (exactly in design and front-end). The nature of agency work is to leave a deliverable for the client to work with. My idea is that when the pro…

Thanks. What I needed today is for a rando on the internet to call me stupid, a dev who doesn't fully grasp CSS + design. I use tailwindcss and so do other devs. Many of those devs are better than me and you. Instead of assuming that everyone who disagrees with your choices is stupid, maybe reflect on popularity of tailwindcss and assume, in an Ockham's Razor kind of way, that it's a good technology. Even if it's not…

That went bad quickly! You are putting words in the mouth of the original comments for no reason. "a dev who doesn't fully grasp CSS + design" does not mean a stupid dev; it can be a dev who decides that he doesn't need to fully grasp CSS + design to do a great job. Why is that weird that the owner of an App design service agency prefers pure CSS over a library?

Re: Coming to Terms with Tailwind

#90

Post by croes »

chrisseaton wrote: post #58
croes wrote: post #41

Earlier quoted context omitted.

He just disagrees if using tailwind is a good idea. Where is the problem that justifies blocking?

> Where is the problem that justifies blocking? You can block anyone on social media for any reason or no reason at all and you don’t have to justify it to anyone.

You can, but should you? Doesn't that look unprofessional?
Post reply on HN