Linked by Thom Holwerda on Tue 7th Jul 2009 08:51 UTC, submitted by PLan
Thread beginning with comment 372119
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
"So GNOME will have the covered parts of Mono installed by default ... that is almost a guaranteed outcome now.
What this does is to allow decisions regarding the covered portions to be made on a technical basis. Mono has some problems on that front; Notably, resource usage. But those issues have, so far, mostly gotten lost in the heated political debate. This will quite possibly cause some defections from GNOME.
Ever the KDE troll, huh, Hal? An alternative, or perhaps complementary view, would be of an influx of devs who prefer a safer, managed language to the buffer overflow minefield that is C++. I'm hardly an enthusiastic Mono/C# fan. But at least this legally binding promise, and clear separation of code, will neutralize the political doomsayers and allow the debate to move on to matters of technical merit. " http://techbase.kde.org/Development/Languages/Qyoto
http://techbase.kde.org/Development/Languages/Smoke
Edited 2009-07-08 01:43 UTC




Member since:
2005-07-24
What this does is to allow decisions regarding the covered portions to be made on a technical basis. Mono has some problems on that front; Notably, resource usage. But those issues have, so far, mostly gotten lost in the heated political debate.
Ever the KDE troll, huh, Hal? An alternative, or perhaps complementary view, would be of an influx of devs who prefer a safer, managed language to the buffer overflow minefield that is C++.
I'm hardly an enthusiastic Mono/C# fan. But at least this legally binding promise, and clear separation of code, will neutralize the political doomsayers and allow the debate to move on to matters of technical merit.
Edited 2009-07-07 16:18 UTC