| Even the article notes that mindless server-side is not good software engineering. (Note the use of the phrase "can cause problems" instead of "does cause problems".): > If you do choose to use client-side JavaScript frameworks, be aware that although they can be helpful when building a service with a complex user interface, they can introduce problems. > Using a client-side JavaScript framework can: > - increase the overall size of your code base and push processing to the client-side, causing performance issues for users with a slower network connection or lower powered device > - create a reliance on third-party code that your developers do not have control over, requiring you to make major changes to your service in order to stay up to date with changes in the framework > - make it difficult to find people with the skills required to maintain the code, if the frameworkâs loses popularity over time > If you use a JavaScript framework you should: > - be able to justify with evidence, how using JavaScript would benefit users > - be aware of any negative impacts and be able to mitigate them > - consider whether the benefits of using it outweigh the potential problems > - only use the framework for parts of the user interface that cannot be built using HTML and CSS alone > - design each part of the user interface as a separate component > Having separate components means that if the JavaScript fails to load, it will only be that single component that fails. The rest of the page will load as normal. |