Learn More
Resend Email
6
null-pointer-ex
21d

For fuck's sake, what are the creators of tailwind thinking? So, I made the mistake of upgrading to tailwind v4 and now my site is broken. Who in the fuck thought removing half the features is an "improvement"?.

wE've mAde ConFiGUraTion EaSier with CSS.

Sure, let's see. It sounds neat on paper, a "CSS-first" approach. But when you've got existing projects with a meticulously crafted tailwind.config.ts file, it's not simplified at all, it's a migration nightmare. Suddenly, my custom colors and breakpoints are all gone or behaving unpredictably because the new system decides to interpret them differently.

Do these people actually work on any project that is long-term or is everything they work on just green-field?

Because when you have hundreds of pages and custom built rules, and now eveything is broken for no goddamn reason, it's not fun, is it?

I've now wasted days on this shit when I should have shipped so many features.

I simply can't wait to switch my career to something else. Like, this stuff is just so bad man. Come on.

rant

css

tailwind

tailwindcss

typescript

javascript

svelte
Favorite
Ranter
Comments
  • 1
    21d
    It's a major version upgrade. Your auto updater should have created a separate branch for it and your end to end years should have failed.

    This is the only way I've found a somewhat same way to maintain dependency heavy frontends.
  • 2
    20d
    Tailwind is cancer
  • 0
    20d
    @hjk101 years=tests & same=sane

    Swipe without proof reading fail😅
  • 0
    19d
    Things like this make me want to toss my laptop into a lake and open a bakery.
  • 0
    17d
    Why are you updating packages in ongoing project, lock it in so it doesn't update major versions.

    You should be building the app instead of updating the dependencies.

    Breaking changes be breaking, nothing new to see here...

    I get the frustration, but seriously, just lock in the version and work with that. Any dependency update that introduces breaking changes will break so ask managers for more time when they ask for new, shinier, version.
  • 0
    6d
    I just had to jump into a tailwind project because one of our engineers straight up had enough of trying to fix it and quit - and having done so, I no longer blame him for leaving us in the lurch.

    I can see how it'd be quick and fun to prototype with, but nobody should ship a site with this shit in it unless they plan to be the only person maintaining it. I generally let our devs choose their own tools, stack etc, but now we have one rule:

    No tailwind, ever.
  • 0
    5d
    @MM83 i don't get it, i have fucked up codebases on a client project where i updated tailwind to the last version because we introduced latest shadcn/ui canary and all the other buzzworded shit that is trendy right now.

    It took me maybe 2 fucking hours to read the documentation, drink a coffee and fix the shit in multiple repos.

    Don't get me wrong, if it is not the skill issue, then you have codemonkeys in a team who glouriously failed by using it wrong - no matter how hard it is to use it wrong.

    It's a fucking tool and i am genuinely interested why did you had to update it - was it developer vanity or marketing/pm/ceo decisionor something completely else. Also v4 works fine with old configuration files or you just add it as a vite plugins and inject the config file there.
  • 0
    5d
    @devJs I didn't update it, I binned it and banned it. Writing inline CSS is "how to break a design pattern 101" even if it's just a few instances, encouraging people to build an entire site like this is fucking madness.
  • 0
    5d
    @MM83 email programmers: and I took that personally.
  • 1
    5d
    @kiki been a while, hope you're good.

    Took what personally?
  • 1
    5d
    @MM83 those email devs be inlining all their css because they still think that some people use that old cursed version of ms outlook that used ms word html engine to render web pages instead of internet explorer
  • 0
    4d
    @MM83 every friggin person who came to me with the same argument of having classitis in the html/template

    Did you read the documentation? I know you didn't.
    https://tailwindcss.com/docs/...

    Inlining CSS with TW is good ONLY for getting the shit done right BEFORE YOU MOVE IT TO THE @apply inside the class

    You get smaller footprint and pure css inside the class after compiling!

    But you do you, just don't blame the tool you didn't invest time to learn.
  • 0
    4d
    @devJs if you say so, mate.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment