this post was submitted on 04 Feb 2025
39 points (93.3% liked)

Programming Circlejerk

299 readers
1 users here now

Community to talk about enlightened programming takes

Rules:

founded 1 year ago
MODERATORS
top 22 comments
sorted by: hot top controversial new old
[–] GTG3000@programming.dev 18 points 1 year ago (1 children)

Typescript is delightful to ensure that everything works and you don't get surprises. Tailwind though...

...it's certainly faster in the development but it's not nearly as nice as CSS can be, especially since now any browser supports nesting.

[–] brian@programming.dev 3 points 1 year ago (1 children)

idk if nesting is the reason people used tailwind. imo it's more that css itself is a lot of complexity and overhead to write if you already have nesting and reuse in whatever you're using to produce html, ex react. I'd rather not have to maintain a css tree and a component tree when it can all be colocated.

writing raw html? yeah tw doesn't make any sense

[–] GTG3000@programming.dev 2 points 1 year ago (1 children)

Well, I meant the opposite - in CSS you can make the styles cleaner with nesting and such. TW always ends up with a ton of copy-pasting.

Though I will be fair, I don't think the projects I've seen it in used the themes properly.

[–] brian@programming.dev 1 points 1 year ago

if you're copypasting you're not using the code reuse tools of your component library. the nesting in normal css is component nesting with tailwind. and if you're copypasting things that aren't just the same component styles but something else shared, it's just a string you can stick it in a variable.

[–] crmsnbleyd@sopuli.xyz 8 points 1 year ago

uploaded image instead of just the link because linkedin sucks

[–] nick@midwest.social 4 points 1 year ago (2 children)

Fuck typescript, fuck tailwind, fuck this idiot.

[–] Marthirial@lemmy.world 9 points 1 year ago

I like TW and TS but I also agree with your passionate hatred for hipster siloing.

[–] spartanatreyu@programming.dev 5 points 1 year ago* (last edited 1 year ago)

Typescript has made the js ecosystem better.

Tailwind is the epitome of someone trying to make one tool that does everything then tries to sell you on buying only that one tool. As the old saying goes: When all you have is a hammer, everything looks like a nail. Sure you can hammer a screw into a wall, but if you used the right tool for the job to begin with, you could also unscrew the screw and replace it later without needing to fill the old hole or make another hole in the wall.

Tailwind exists purely because developers keep trying to learn CSS the wrong way from people who don't know how to use it, then get frustrated when it doesn't work out.

The problem is that when you're starting out, you don't know the difference between good and bad teachers.

[–] LodeMike@lemmy.today 3 points 1 year ago (1 children)

You can say this about literally everything.

[–] BatmanAoD@programming.dev 3 points 1 year ago (1 children)

...no? I have heard (or made) plenty of complaints about various languages from people who know and/or use them professionally.

[–] LodeMike@lemmy.today 2 points 1 year ago (1 children)

I don't really understand your comment. I meant the statement in the image.

[–] BatmanAoD@programming.dev 3 points 1 year ago (1 children)

The statement is "only developers who have never used them or aren't skilled with them dislike them or prefer [the primary alternative]". Is that what you mean could be applied to "literally everything"?

[–] LodeMike@lemmy.today 2 points 1 year ago (1 children)
[–] BatmanAoD@programming.dev 2 points 1 year ago* (last edited 1 year ago) (1 children)

Okay, so I'm saying that there are lots of languages for which that's not true, i.e. people who use the language do dislike them.

[–] LodeMike@lemmy.today 2 points 1 year ago (1 children)
[–] BatmanAoD@programming.dev 3 points 1 year ago (1 children)

I think you might just be misreading the original post. It could be rephrased as: "all developers who dislike TypeScript and Tailwind either haven't used them or aren't skilled with them." If you could say that about anything, it would mean that developers never dislike tools with which they are skilled. I'm saying that's clearly not the case.

[–] LodeMike@lemmy.today 1 points 1 year ago (1 children)

Ohhhhh

I'm not agreeing with the person in the image. I'm saying something like "people say that about everything" or "for every language thete is someone in the world who will say that for the language."

Not "this is true for every language"

[–] BatmanAoD@programming.dev 1 points 1 year ago

So...I'm not sure what that implies about the statement? "Someone probably believes X about Y" isn't just true for any Y, it's true for any X.

[–] NostraDavid@programming.dev 3 points 1 year ago (1 children)

Why use many lib when few lib do trick? *shrug*

[–] SirQuackTheDuck@lemmy.world 2 points 1 year ago

The bigger your node_modules, the more right you are.

[–] BB_C@programming.dev 3 points 1 year ago (1 children)
[–] crmsnbleyd@sopuli.xyz 2 points 1 year ago

modding you right this second