Learn More
Resend Email
7
null-pointer-ex
7d

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
  • 3
    7d
    Slowly we'll go back building shit ourselves again and we'll actually code instead of googling the manual. What I hate the most about frameworks is they they did the fun part.
  • 1
    6d
    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.
  • 1
    6d
    Tailwind is cancer
  • 0
    6d
    @hjk101 years=tests & same=sane

    Swipe without proof reading fail😅
  • 0
    5d
    Things like this make me want to toss my laptop into a lake and open a bakery.
  • 0
    3d
    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.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment