Originally posted by pingufunkybeat
View Post
Announcement
Collapse
No announcement yet.
MonoDevelop vs. Xamarin Studio IDEs
Collapse
X
-
Originally posted by funkSTAR View PostSo you deny that I can call Digia and exchange $$$ for a Qt-edition stripped of some copyleft terms AKA Qt Commercial? LOL you are really cornering yourself now
Comment
-
Originally posted by jayrulez View PostSo you deny that I can head over to qt-project.org and obtain a LGPL edition of Qt AKA Qt Free? LOL you are really cornering yourself now
I develop with MonoDevelop and I see no problem for most of my cross-platform development to use VS as main IDE and to import flawlessly to MD and to do the build, etc.
The worst part is that MonoDevelop is soon to be a 10 years old project and people did not care much in Linux world about it (and Mono in general), so the parent company will spend more development time to profitable tools.
I'm curious Digia if it will develop with the same pace still (as Nokia did) to QtCreator and their Qt stack.
One part which I really don't understand: why Qt is compared with Mono most of the times? I'm an ex-Qt developer and I'm an C# developer. I see weaknesses and strength of both frameworks.
In many ways I see MonoDevelop having an edge for quick&dirty project that will grow, compared with Qt. With C# you don't have to play with macros for QObject, slots, and such, you have a GC and some services with very few libraries, which themselves are a breeze to work with C# (I talk here about Xml+Reflection, Dependency Injection, Database connectivity, or a simple web server). So, if you have a database application or a web service, you can import it from C#/Visual studio, you recompile with Mono and you add Gtk# UI on it. This looks to me a natural path of development of Mono applications to Linux (or Mac OS X). The code in C# is in many cases smaller and more clear than the C++ equivalent and a great experience (that can be given by Visual Studio + a plugin like JustCode, Resharper or CodeRush) in writing this code.
Qt has other advantages, mostly: you know upfront that the application has to look the same (or very similar) in all platforms and performance is a concern. I see Qt to enrich a huge C++ codebase with a fancy UI, but if you have to start from scrach and the raw performance is not your ultimate concern, I don't see any company to pick Qt for a desktop application. Developers can create the UI with QML and QWidgets, and write in C++ all the performance sensitive code. After that you're good to go and recompile on every platform Qt is supported. Even Qt will start a bit slower to develop with, is a bit more verbose (because of C++), but at the end, it is modular, it has fairly few bugs and as C++ is the core of the language, sensitive algorithms (like for example a picture processing algorithm) can give the snappiness most users may want.Last edited by ciplogic; 22 February 2013, 03:54 AM.
Comment
-
Originally posted by jayrulez View PostSo you deny that I can head over to qt-project.org and obtain a LGPL edition of Qt AKA Qt Free? LOL you are really cornering yourself nowLast edited by funkSTAR; 22 February 2013, 04:13 AM.
Comment
-
Originally posted by ciplogic View PostOne part which I really don't understand: why Qt is compared with Mono most of the times? I'm an ex-Qt developer and I'm an C# developer.
Both requires assignment of broad license or copyright.
Both are increasingly focusing on nonlinux markets to increase volume.
Both offer customer support to avoid GPL/LGPL/free software licenses.
Both offer premium versions to paying customers; Thus discriminating against free users.
Both makes closed source add in modules.
Both have business models depending on this madness to continue.
Both have track records of making disruptive changes to their business models. Often to the worse.
The trust level is extremely low.
Comment
-
Originally posted by funkSTAR View PostTechnical differences aside there is more similarty than you think.
Both requires assignment of broad license or copyright.
Both are increasingly focusing on nonlinux markets to increase volume.
Both offer customer support to avoid GPL/LGPL/free software licenses.
Both offer premium versions to paying customers; Thus discriminating against free users.
Both makes closed source add in modules.
Both have business models depending on this madness to continue.
Both have track records of making disruptive changes to their business models. Often to the worse.
The trust level is extremely low.
Comment
-
Comment