3 ms·
Here is my take on this, very subjective and also very biased as I worked mostly as backend dev or Rails dev. I say this with a focus on the long term maintaina
by gls2ro 3y ago
Here is my take on this, very subjective and also very biased as I worked mostly as backend dev or Rails dev. I say this with a focus on the long term maintainability:
In general dont start your web app as a SPA.
Probably (99% of cases) your web app does not need to be fully SPA. If you need live data/reactivity sprinkle part of SSR pages with whatever FE framework you feel is good.
HTML and Vanilla JS are very maintainable over long term. So is being able to share a web URL and see the exact information without doing anything extra to make it work.
Try to resist the urge to use a fancy framework as much as possible. JS + HTML will go a long way.
Push back to designers asking you to do things that needs you to architect a full SPA. Most of the times the users dont want that. Ask what is the actual need that should be solved.
As we are on this subject: please dont start with infinite scrolling. It adds do many case to be handled.