Hi Vest,
yeah, we prefer Vala. The main problem is, that we always fear that the original developer won't be the maintainer forever. This is now the case for all our games. The barrier for entry is very high for C. Any programmer's experience with Java or C# (one or both should be taught to a reasonable degree at every University) is a good starting point. The amount of C I finished my bachelor's degree with was next to nothing. Look at this bug: https://bugzilla.gnome.org/show_bug.cgi?id=613077 This was open for four years. My resolution ( https://git.gnome.org/browse/gnome-robots/commit/?id=ab5caae53dc4dfa71f242b7e83a40e650e825baf) changed the position of one line. Usually, one would hope, that such a bug would have been fixed at least by a drive-by-patch (during the 4-year-period). We do believe that everyone who proposes a game (and has it written) is proficient in that language. But no one can guarantee that the original developer is around next year when changes have to be made (like the general inclusion of header bars for toolbars during the last months). With that in mind it is easier for the maintainers to have a single language the codebase is in and a core set of used libraries (the gtk-stack) instead of language and library fragmentation (like the original poster with "hamster" as a drawing library). I maintain 5 of the 15 games and it is a lot of work as it is. Again, nobody is denying that "your" C is good. But "our" C is bad and "we" fear that "we" will be the ones who end up supporting the application once "you" are gone. I hope you understand our reasoning behind this :) Mario Am 16.04.2014 09:53, schrieb Vest V.:
|