Choosing a Software Stack - Is Qt Right for Your Project? - Video

One of the most difficult choices when starting any new software project is selecting the programming language and framework your team will use to create it. Should you stick with Qt because it’s the best tool for the job? Should you switch to something using web-based technology or designed explicitly for mobile? Is Python a better choice to integrate in machine-learning capabilities?

The initial software selection process is so crucial because it shapes how your software is created, its natural limitations and capabilities, the third-party resources you’re able to use, who is qualified to work on it, and how long the software will be easily maintained.

However, determining the right framework can be very difficult. Web resources often provide conflicting guidance or are subjectively based on a single developer’s perspective. Rarely does anyone create a substantial program in multiple frameworks that would allow a true comparison – creating a completely duplicate program of any complexity is very difficult and time consuming. As a result, software stack comparisons are really too shallow to allow readers to understand the true consequences of a choice, especially when applied to the specifics of your project. It’s not surprising then that developers often follow the course of least resistance. Without a clear reason to switch, they default to the same language and framework as their previous project, reusing software that is already familiar.

Since the choice of a software stack is so important to guiding the project’s future course, it’s worth treating initial software selection as a strategic decision rather than the unconscious assumption that it can sometimes be. T

This video briefly introduces some of the main considerations and offers a comprehensive whitepaper where you can dive into the details: https://www.kdab.com/qt-and-software-stack-choices/