Like @Antoine said:
I was also very surprised by the very heavy changes made from V3 to V4. Is ok to introduce breaking changes, but V4 broke everything .
I feel this so much. At the time we upgraded to the then current v4 version, we had to rework way too much stuff that was not mentioned in the migration guides.
We had localization issues, the way to populate objects changed (populate deep), lifecycle hooks, we reworked fileuploads and much more things. We even had to do workarounds for some existing bugs.
Now with some workarounds and custom changes we feel like we can use strapi v4 now. But we are heavily worried to upgrade even patch and minor versions within v4, breaking our workarounds/changes that we made to finally use strapi as intended.
I hope the v5 version will not break everything again
Most of our developer team liked strapi and still like it however some of us are missing the “good old v3 days” where stuff was more straight forward and worked out of the box.