The Dev, The Stack, And The Framework - Which tooling is the best to use?

Thomas |

04. Mai 2022 |

- min Lesezeit

The Dev, The Stack, And The Framework - Which tooling is the best to use?

There’s a crucial question that almost every development project starts with: Opinionated or not - Which framework is best to use?

Opinionated vs Unopinionated Frameworks: How to decide?

With this fundamental decision, you either take the freedom to go with your custom solutions, along with the related obstacles. Or you take the chance to adopt smart defaults that allow you to move swiftly, while hiding a variety of resolutions and putting you on a prescriptive path.

Choosing whether to utilize an opinionated framework (such as Angular) or unopinionated library (such as React) will have far-reaching consequences - both in terms of delivering the product to market on time, and in the long run, for maintenance and scalability.

In the latest episode of Digital Log by DPM, Thomas May, Senior Software Engineer, along with Thomas Limp, Lead Software Architect, debate the pros and cons of taking those decisions.

Watch the full episode to learn why Thomas and Thomas have a hard time to agree on one school of thought and what factors you need to consider when choosing for a suitable tech stack:

What means Opinionated and Unopinionated Development?
What are the pros and cons of each approach?
Why there is no framework that is truly unopinionated, according to Thomas Limp?
How do we at DPM decide on a suitable tech stack for our clients? And factors to consider when deciding on one framework or the other.

Watch the episode on YouTube or listen to it on Spotify (or wherever you get your podcasts).

From my perspective, there is no distinction between opinionated and unopinionated frameworks. I would even go so far as to say that there are no unopinionated tools in the technology space since every tool we are using has been created by a person, and that person brings in their opinion.

Play