Thanks for the comments Joe.

The point I wa...

2007-11-13T20:57:00.000-05:00

Thanks for the comments Joe.

The point I was trying to make with not abandoning C was basically choose the applications based on features not on the language. It isn't so much that I think GNOME should stick with C or move to any other language. I don't think any 'language' is the answer. At the same time I'm also concerned with the extra bloat that comes with all of the different languages and runtime that are required for a the current complete GNOME Desktop.

I think that without having something like a common runtime (Mono) what you end up with is an extreme amount of work being done over and over again. I understand that GTK+ using the GObject as a base lends itself to easy wrapping but it still seems like a lot of repetitious work is going into writing those wrappers.

I still think that the choices available in open source are the key to it's success and what makes each Linux distro unique but this is a complex problem that needs to be addressed.

Hi Greg,

I agree to an extent that using C ...

2007-11-08T11:46:00.000-05:00

Hi Greg,

I agree to an extent that using C for platform libraries is a good idea, and I certainly wouldn't advocate eliminating the ability to write in C by requiring that functionality to be in something like Python or C#.

Also, I totally agree with your conclusion that the issue with Python is a programmer discipline issue than an issue with Python itself. Apparently a lot of people misinterpreted me to think that testing was somehow unnecessary.

Agree wholeheartedly on the FUD thing. For all the benefits that Mono gives one in development, it's been more or less neutralized by the hassle with its acceptance in the community and the harsh reactions.

Thanks,
Joe

Comments on GC Blog: Monotonous?

Thanks for the comments Joe.The point I wa...

Hi Greg,I agree to an extent that using C ...

Thanks for the comments Joe.

The point I wa...

Hi Greg,

I agree to an extent that using C ...