380 karma · joined November 20, 2019
The approach worked for me and I learned some neat things about vanilla CSS and JS features, but I would also rather start new projects with a boilerplate or framework, because even small projects easily grow in scope and it’s nice to be prepared for the eventuality.
That being said, I’m sure the salaries in Europe aren’t so great, but that goes for many things and other sectors definitely have it worse than tech workers (e.g. healthcare workers).
And it sounds like you could try working for smaller companies that are more agile and don’t have such annoying management issues! (At least in Germany they also tend to pay better or equally well as big corporations.)
And it doesn’t seem like there’s a lot of hope for the future of 3rd-party Twitter apps anyway.
It’s good to see that many (if not most) of these affected developers are already working on premium Mastodon clients.
You shouldn’t need react-router or other routing-related third-party libraries because Next’s router (and its file-based navigation system) should be enough(?). I’d also say that React itself has powerful-enough state management options (useState hook plus React context, if needed).
The only annoyance I ran into was getting proper i18n working and integrated with Next (with i18next). There were some issues with Next’s newer releases and a redesigned i18n setup that broke a lot of things for me and I regretted the dependence of multiple libraries and frameworks needing to work together. (Storybook is another library that kept breaking.)