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

Tailwind and slop apps

briandouglas.ie

Post reply on HN
Print view View original

81–85 of 85 posts

Re: Tailwind and slop apps

#81

Post by vitamark »

Induane wrote: post #71
vitamark wrote: post #60

Tailwind, IMHO, doesn't bring any real value to the developer or the codebase. It's just a weird way to write CSS right in the classes. We have a tool for that, it's called "writing CSS", and it actually has classes that allow sharing style choices across various components (which somehow is marketed as feature of TW) In other words, I don't see how Tailwind is just "I want to write my CSS in obscure way in the wrong…

There are a couple of things: 1. Locality of behavior - the classes are the description of the style once you know tailwind, and they live where the thing they're styling is. I can look at a template and know pretty well how it is going to look without having to go lookup a sites personal bespoke CSS and match what's written there to the markup. 2. It's the same classes as you move from project to project. I have ton…

I see the point, but really this is solved better by having a solid foundation of UI components (might be an existing UI-kit or own thing, a piece of CSS anyway), and then you can use the same-ish classes over many sites.

What I find with any site is that without a good foundation you're bound to repeat same styles over and over, and with one you don't get any point with Tailwind.

Re: Tailwind and slop apps

#82

Post by rcxdude »

gibbitz wrote: post #63
homebrewer wrote: post #62

Earlier quoted context omitted.

And for some reason you're describing it as it's a bad thing. I don't care much for tailwind, but bootstrap is still used for intranet applications, and is an excellent pick in that category. Why waste time writing CSS, reimplementing what has been done millions of times before you, when working on an application where function has strict precedence over form? I'd rather listen to users who fill hundreds of forms dai…

Muzak isn't what most people choose to listen to. I'm not bemoaning the use/existence of the tool, I'm bemoaning what it did to the internet and taste making. We accept boring competence in web design like we accept weird outlet placement in our homes. The signal it sends is that it doesn't matter and as a result many in this thread (and web users in general) believe it. We've been bemoaning the death of the internet…

I would personally like a little more consistency and a little less creativity in my UIs, TBH. Most UIs should be boring and effectively invisible, because if I'm paying attention to the UI, it's a distraction from the task or content that I actually care about. The web and electron have hastened a trend which I intensely dislike of every single application looking and acting completely differently for what is fundamentally the same thing. It's not that this variation doesn't matter: it's actively bad. (Not that UI design doesn't matter. Good UI design is important. But part of what makes UI design good is consistency and that's what web designers seem to actively dislike)

(more precisely, I long for the days of a standard and customizable UI toolkit. I should be the one who can adjust what the UI looks like, not hundreds of different designers with different concepts of how to 'stand out')

Re: Tailwind and slop apps

#84

Post by ryanbrunner »

wild_egg wrote: post #48
crooked-v wrote: post #38

Earlier quoted context omitted.

Writing CSS from scratch sucks. I'm glad we've left those days far behind.

Modern CSS is actually really quite pleasant.

It's great for document formatting. For app layout, it's very easy for the cascading aspect to shoot you in the foot if you're not careful (which is why even the most purist CSS writers will tend to layer abstractions or rules on top of it, even if it's only convention based ones without technology like BEM.

Re: Tailwind and slop apps

#85

Post by wild_egg »

ryanbrunner wrote: post #84
wild_egg wrote: post #48

Earlier quoted context omitted.

Modern CSS is actually really quite pleasant.

It's great for document formatting. For app layout, it's very easy for the cascading aspect to shoot you in the foot if you're not careful (which is why even the most purist CSS writers will tend to layer abstractions or rules on top of it, even if it's only convention based ones without technology like BEM.

Emphasis on the modern CSS. @layer, @scope, etc. go a long way in fixing the footguns.
Post reply on HN