On Saturday 12 November 2005 03:00 pm, Steve Graegert wrote:
What would be the rationale behind using C++ in .NET?
C++/CLI is an ECMA standardization effort.
It's ironic that Microsoft is not touting this technology when a few years back they went out of their way to destroy the browser market for a company that had the lead in platform abstraction. http://www.mozilla.org/projects/nspr/reference/html/index.html
Don't see any parallelism here. Could you please elaborate on your thoughts.
It's a platform abstraction layer. To some extent Mozilla - which is what the Netscape browser has always been called - provides a programming environment in which code can be run portably. At the time Microsoft dumped IE on the market to starve Netscape Communications of development capital the actual "(compile once) run anywhere" was implemented with Java, and JavaScript. But the ability to port C and C++ code between platforms, and the idea of a platform-independent component interface are very much like what the CLI provides.
Qt also provides some of the same functionality the CLI provides.
Really? What would that be? Are you talking about language bindings?
No. I'm talking about portability features, and more.
Besides Windows Forms, which has a eliminated a lot of the Swing problems, Java is one of the most powerful and easy to use platforms for GUI development. While Qt and C++ can't compete in this discipline, speed of execution is unmatched, of course.
I really can't agree with that. I find Qt very easy to work with. Then again over the past two years I read TC++PL, and several other books on C++ carefully.
IMHO, for development of native UNIX applications, C/C++ is still the one and only tool, although I prefer GTK+ over Qt, but that is another issue.
Gtk+ is not C++. Qt _is_ C++. Steven