qt:motivations
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
qt:motivations [2010/12/08 22:51] – mithat | qt:motivations [2011/12/03 17:24] (current) – [Decisive factors] mithat | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Motivations ====== | ====== Motivations ====== | ||
- | I have decided that I need to teach myself **[[http:// | + | I have decided that I need to teach myself **[[http:// |
My enthusiasm for Qt had also been tempered by its licensing. In the past, it was available under a libre and gratis GPL or an expensive commercial license, and anything made with the GPL version was required to be published under a GPL-compatible license. In early 2009, Qt [[http:// | My enthusiasm for Qt had also been tempered by its licensing. In the past, it was available under a libre and gratis GPL or an expensive commercial license, and anything made with the GPL version was required to be published under a GPL-compatible license. In early 2009, Qt [[http:// | ||
Line 37: | Line 37: | ||
As far as desktop programming solutions that are not FOSS, multi-platform, | As far as desktop programming solutions that are not FOSS, multi-platform, | ||
- | ===== Decisive factors ===== | + | ===== Decisive factors |
Perhaps what really tilted the scales for me was the adoption of Qt as the native platform in [[http:// | Perhaps what really tilted the scales for me was the adoption of Qt as the native platform in [[http:// | ||
Line 44: | Line 44: | ||
===== A word on multi-platform programming in general ===== | ===== A word on multi-platform programming in general ===== | ||
- | The goal of multi-platform programming is to write once and compile anywhere. This is a huge goal, and one that not unexpectedly is essentially impossible to achieve perfectly. There are just too many differences in the way platforms work--from the OS level up all the way up to interface conventions. This leads to the following statement: | + | The goal of multi-platform programming is to write once and compile anywhere.((Or, as in the case with Java, compile once and deploy anywhere.)) |
- | **If you plan to develop your project to reach multiple platforms using one holy code base, you //must// accept compromises.** | + | **If you plan to develop your project to reach multiple platforms using //OneHolyCodeBase//™, you must accept compromises.** |
- | There are people who tell you this isn't the case. They are lying. There are people who say multi-platform development is doomed to failure. I believe they are lying as well. The simple truth is that multi-platform development based on one holy code base is possible, isn't perfect, and may not be the best (or even easiest) way for you to solve your multi-platform problem. The key is to develop an understanding of what the limitations (and strengths) of multi-platform programming are, and then apply it when it makes sense. And I can't think of anything but experience to give you this understanding. | + | There are people who tell you this isn't the case. They are lying. There are people who say multi-platform development is doomed to failure. I believe they are lying as well. The simple truth is that multi-platform development based on OneHolyCodeBase™ |
qt/motivations.1291848682.txt.gz · Last modified: 2010/12/08 22:51 by mithat