Ask HN: What's the biggest problem you've faced with SPA JavaScript frameworks?
Every developer has faced some limitations or barriers when using SPA JavaScript frameworks and wished for a new feature to solve their problems.
This is a discussion thread to post limitations you face with JS frameworks/libraries like React, Vue, Angular, Svelte, Next, etc. so that we developers can use this information for developing tools that address these problems. These frameworks spend a tremendous effort trying to solve ridiculously simple problems. The most obvious example is state management. Here is how I solve for state management in a few easy steps: https://github.com/prettydiff/wisdom/blob/master/state_manag... With that approach I can have full state restoration on a full OS GUI running in the browser that loads in 0.3 seconds with state fully restored: There are some many problems with large SPA frameworks. These are basically risk mitigation strategies for large employers as architectures in a box. These frameworks mitigate some level of decision making capacity which supposedly eases hiring but really eliminates employer training and development of junior developers. That’s the biggest problem: low confidence people building shitty products that are unnecessarily massive in size and super slow. The employer saving money by eliminating training time and instead pushes the resulting costs onto its users with a shitty product.