You need to realize that those new frameworks and APIs are not really new, they are just a different view on the same constraints that we all have when programm

You need to realize that those new frameworks and APIs are not really new, they are just a different view on the same constraints that we all have when programming. It's 90% marketing: a new tool promises to be 10x faster than the other in some circumstances, but forgets to mention that it has a lot of important features missing. Some frameworks compile to JS (a pain to debug), some don't (but then they have less clean CSS separation because those tools are limited in what they can do). Then there's the HTML only movement that forgets to mention that it gets complicated whenever there are dependencies between data. The problems you are facing are real, but switching to different frameworks will get you different sets of problems that you need to face. What's important is to understand what's going on behind the scenes and move forward with your project, whether it's in the framework you're using or the new one.