You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wasn't going to complain, and I even had quite a few issues during the upgrade that I largely resolved.
However, this is something I have to complain about, I'm in lower device oriented development, but only have lower device environments in my testing sessions. Such a major compatibility change was not mentioned a single word in the upgrade docs, that it resulted in my product not being able to display the background until a second before it was about to be upgraded to the production environment. Luckily, I had a little experience with comparing and contrasting, and basically pinpointed the source of the problem, and I also happen to be good at using issue query tools like issues, so I found 15985.
That's when I realized “What? tailwindcss v4 changed the compatibility requirements, not lowering them, but raising them?”. . Yes, for the average developer using the tool, and only paying attention to things like compatibility when using it for the first time, unless it's explicitly stated when upgrading, it's assumed to be fine by default.
That's my complaint, the helplessness of an average developer.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I wasn't going to complain, and I even had quite a few issues during the upgrade that I largely resolved.
However, this is something I have to complain about, I'm in lower device oriented development, but only have lower device environments in my testing sessions. Such a major compatibility change was not mentioned a single word in the upgrade docs, that it resulted in my product not being able to display the background until a second before it was about to be upgraded to the production environment. Luckily, I had a little experience with comparing and contrasting, and basically pinpointed the source of the problem, and I also happen to be good at using issue query tools like issues, so I found 15985.
That's when I realized “What? tailwindcss v4 changed the compatibility requirements, not lowering them, but raising them?”. . Yes, for the average developer using the tool, and only paying attention to things like compatibility when using it for the first time, unless it's explicitly stated when upgrading, it's assumed to be fine by default.
That's my complaint, the helplessness of an average developer.
Beta Was this translation helpful? Give feedback.
All reactions