ok this needs a reply... it's
not a rant, just a reply reflecting my own opinions.
Marrow wrote:It's like all the work done modifying armagetron will be for little gain because it will never be ours. He'll make a new release and all is lost. The ideas of simply telling Manuel to include new code, while a good idea and noble, is unrealistic because he does not answer his e-mails.
sorry but this is just not true. "ours"??? it's already ours!!! the source is gnu gpl = you can do whatever with it as long as you accredit the originator & don't try to restrict the code or "demand money". you guys should seriously read the gnu gpl license (you are legally bound by it wheter you read it or not).
since you/we aren't accredited developers on the project the only way for our contribution is to send Manuel the parts of the code we have changed - it's his decision if he wants to include it or not, if he doesn't you/we are free to make our own version (we are free to do this in any case as long as we abide by the gnu gpl). if the changes make sense to him he will include them, if after more contact he trusts you then you will most likely become a developer. if he is away for a long time i'd recommend a project takeover (it is not infrequent for takeovers to happen, 1-person projects suffer a high rate of burnout)
another possible solution is to take over the existing project, i've had to do this (even though i shouldn't have as my time/capacity is kind of limited) with the project i'm currently "owning" at sourceforge. you have to participate in sourceforge to do this of course, and you have to submit a request for support stating why you want to take over.
Marrow wrote:Plus, we'll always lack a true grasp of the armagetron source code, since we didn't create it.
i can't believe you said that, not really. but maybe i can understand you... hmm i don't know what experiences you have but you saw what happened with something as 'simple' as the tournaments? so... here you have a guy making a game basically all on his own & it's his first major project so
the code is atrocious, yes, it's all
spagetti and he has said so himself - but it works better than any competition at what is most important:
gameplay! so instead of figuring out the code and turning a diamond in the rough into a shining piece of excellent crystal clear code you want to start from scratch... (reinventing a wheel and making your own mistakes) i only say good luck to you and i hope you succeed - if it's better than armagetron i will play it
Richard Feynman wrote:"What I cannot create, I do not understand."
i like Feynman, i like Eric Drexler, i sometimes drop by Foresight.org
Marrow wrote:I think there is a lot of truth to this saying when it comes to programming with Manuel's code.
yes i sympathise. the point with the gnu gpl license in the first place is to modify, recreate, and improve freely on the code.
Marrow wrote:So, I'd love to see a new project. Since the licensing restrictions are so lax on both games, we could mold gltron and armagetron into one and give both manuel and the people of gltron credit in the readme file.
nice, it's a massive undertaking, but nice - please make it a sourceforge project. however calling gnu gpl "lax" is weird, gnu gpl is fair not lax.
Marrow wrote:An example that comes to mind is when people kept working on making improvements to IRCII, then finally the people made so many improvements, they just decided to give it a new name, BitchX.
ok, sounds like codesplitting (=really bad) this often kills not only one project but many as each programmer wants his own version (think about the former *nix wars). i'm the acting project administrator of Streamripper and i see how devestating this can be, sourceforge is filled with 1-programmer projects who get stuck in the mud, it's a pity if that happens to "the tron's". sometimes codesplitting is kinda "good" but most often not.
my opinions:
- cooperation makes stronger (linux developers didn't make their seperate linux'es, instead they competed at making the different parts best)
- clear code and "over the top" commenting is vital (commenting never bloats a program as you should all know) Linus Thorvalds did this and attributes much of Linux's success to this