Linked by Thom Holwerda on Mon 13th Dec 2010 19:27 UTC, submitted by lemur2
Mono Project For the most time, I've been firmly in the largest camp when it comes to the Mono debate - the 'I don't care'-camp. With patent lawsuits being hotter than Lady Gaga right now, that changed. For good reason, so it seems; while firmly in the 'ZOMG-MICROSOFT-IS-T3H-EVILL!1!!ONE!'-camp, The-Source.com investigated the five most popular Mono applications, and the conclusion is clear: all of them implement a lot of namespaces which are not covered by Microsoft's community promise thing.
Thread beginning with comment 453545
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Evil Companies
by fury on Tue 14th Dec 2010 18:48 UTC in reply to "RE[3]: Evil Companies"
fury
Member since:
2005-09-23

KDE is the largest user, and most distros default to GNOME.


I think that was argued ad nauseum in the previous comments, with the conclusion being half of the distributions include GNOME and half include KDE.


C++ is "good enough", esp. when you use Qt framework. I don't see huge advantages with using C#; notably, Qt does memory management for you so GC is no biggie. Closures would be nice to have, but we will have them in c++0x.


Whoa, Qt does not do memory management "for you". You still have to delete just like any C++ framework.


Again, developers picking up Qt would increase development more than yet another new language that remains fashionable for a while, without ever growing to commercial relevance.


I have no problem with Qt, but C++ with or without it is no substitute for a true, managed, statically-typed language.

Reply Parent Score: 1

RE[5]: Evil Companies
by vivainio on Tue 14th Dec 2010 19:24 in reply to "RE[4]: Evil Companies"
vivainio Member since:
2008-12-26


Whoa, Qt does not do memory management "for you". You still have to delete just like any C++ framework.


With modern C++, delete is for amateurs ;-).

RAII, QObject hierarchy and Implicit Sharing are enough for most development work.

Reply Parent Score: 2

RE[5]: Evil Companies
by flynn on Tue 14th Dec 2010 19:41 in reply to "RE[4]: Evil Companies"
flynn Member since:
2009-03-19

Whoa, Qt does not do memory management "for you". You still have to delete just like any C++ framework.

If I recall correctly all the Qt classes take a parent pointer as a constructor argument. The parent keeps track of all it's children and deletes them when the parent gets deleted. While not the panacea of memory management, it does help a lot. For other things there are always auto_ptr and shared_ptr to ensure proper deletion when resources go out of scope.

Reply Parent Score: 2

RE[6]: Evil Companies
by TheGZeus on Tue 14th Dec 2010 20:28 in reply to "RE[5]: Evil Companies"
TheGZeus Member since:
2010-05-19

Again, people voted this down??

"Oh, here's some helpful information."
"FUCK YOU!"

???

Reply Parent Score: 2

RE[6]: Evil Companies
by vivainio on Tue 14th Dec 2010 20:33 in reply to "RE[5]: Evil Companies"
vivainio Member since:
2008-12-26

For other things there are always auto_ptr and shared_ptr to ensure proper deletion when resources go out of scope.


Those are usually not needed in Qt programs, Implicit Sharing is the real productivity booster:

http://doc.qt.nokia.com/4.6.2/implicit-sharing.html

QPixmap p1, p2;
p1.load("image.bmp");
p2 = p1; // p1 and p2 share data

QPainter paint;
paint.begin(&p2); // cuts p2 loose from p1
paint.drawText(0,50, "Hi");
paint.end();

Reply Parent Score: 3