Even though it’s always good to have options, everyone can think of a time when the sheer number of choices becomes overwhelming. Whether it’s choosing a place to eat with family or picking out a color to paint a room in a new house, it’s clear that adding more options doesn’t make decision-making easier. Even in the software development field, where dozens of decisions can be made by a single team manager on any given day, companies find themselves gridlocked over the choice of what tools to use for their projects.
What Goes into Choosing a Framework
For example, some frameworks are easier to use for programmers more accustomed to object-oriented programming patterns. Some frameworks enforce project file structure and development tooling, which may be preferred for teams that like to focus on writing code. Conversely, other frameworks are virtually agnostic in concerns to this type of structure. These frameworks are ideal for the more independent team.
To keep SPEC granular but general enough for anyone to use, I distilled the plethora of factors to 4 major concerns: speed, productivity, ecosystem, and compatibility. Speed and compatibility assess how frameworks will impact your end-product. Productivity gives insight to the level of workflow integration you want your tools to have. While the ecosystem concern also relates to the development cycle, it focuses more on the community surrounding a framework itself.
Learning More about Frameworks