I found that a good way to pick a framework or make architecture decisions is to borrow ideas from ATAM [1] In a nutshell: specify some important scenarios bas

I found that a good way to pick a framework or make architecture decisions is to borrow ideas from ATAM [1] In a nutshell: specify some important scenarios based on your requirements; for each scenario make a list of desired quality attributes and a way to measure them; use this combination of (scenario, quality attributes) to evaluate each option. It’s a simple and obvious method, but for some reason is barely used. A critique to the article: the evaluation criteria doesn’t seem to take into account any real scenario. For example why 15kb? Are they planning to serve people with very low bandwidth? Is the speed of the FCP more important that time to interactive (TTI)? Regarding frameworks. A difficult metric to measure is hiring: if you are planning to grow your team, a popular, nice to use framework is another point to attract talent (eg choosing Backbone,jQuery,and CoffeeScript may fit your quality attributes but in 2022 is not very attractive for a job description). [1]: https://en.wikipedia.org/wiki/Architecture_tradeoff_analysis_method https://en.wikipedia.org/wiki/Architecture_tradeoff_analysis...