#63031 - Palamon - Wed Dec 07, 2005 11:58 pm
Do you post the source to your games along with the completed games or do you just post the games, keeping the source and coding secrets to yourself?
and why do you do it?
I'm just curious what's everyone's perspective on this, especially on the homebrew area where it's not like people are losing their jobs over revealing their code.
#63033 - chishm - Thu Dec 08, 2005 12:03 am
I post source to most of my stuff. I tend to use other people's code for help, and feel it is only right that I contribute back to the community. When I do hold onto the code, it is either because it is very hacky, or I don't want it to fall into the wrong hands.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#63034 - DekuTree64 - Thu Dec 08, 2005 12:18 am
I always include the source to demos and tools I make. It seems like such a waste to be so secretive if you're not planning to make any money off of it anyway.
If the source is available, then it provides an example for new people to learn from, or experienced people to improve on. New people means more cool demos to play with, and improvements mean I don't have to do the work myself :)
I guess the worst that can happen is someone makes a few changes and claims it as their own, but that doesn't cause me any trouble so I don't really care.
_________________
___________
The best optimization is to do nothing at all.
Therefore a fully optimized program doesn't exist.
-Deku
#63036 - kusma - Thu Dec 08, 2005 12:57 am
i rarely release code. this has more to do with the fact that to release a piece of code, you need to clean it up and document it quite a bit before it become useful to others, than me wanting to keep secrets. let's face it, there's already enough hacky crappy sources floating around there.
#63047 - gauauu - Thu Dec 08, 2005 3:04 am
Yeah, I agree with a lot of what y'all said. I like to open things, but it really depends on what and when. What the code was for, whether, looking back, the code is NASTY, etc.
#63058 - Vich - Thu Dec 08, 2005 9:37 am
That depends on the project in my case. I have released two base libraries under OS: one is a core/system/tools library and the other is a simple portable graphics engine.
I don't mind putting those available, but I wouldn't publish the source of games I make.
I have ported the first lib completely to the NDS and probably soon also to PSP(I just got one for free :D). I am 50% finished with porting the second library to the NDS and might then make a PSP port.
#63059 - Dwedit - Thu Dec 08, 2005 10:06 am
If something is freeware, there's no point to NOT give the source code out.
_________________
"We are merely sprites that dance at the beck and call of our button pressing overlord."
#63079 - thos_thom - Thu Dec 08, 2005 3:16 pm
I would give out the source code, if i thought it would benefit anyone. Most of what i do is genuine attempts to get fun games working, not tech demos. But if i believed that anyone wanted it, i would give it out.
_________________
--------------
^thom(as)?
--------------
#63099 - kevinc - Thu Dec 08, 2005 6:10 pm
| kusma wrote: |
| this has more to do with the fact that to release a piece of code, you need to clean it up |
And that's exactly why I OS my programs, at least in my case it makes me write cleaner code :) (at least for the 3 or 4 other people who will ever read it).
#63100 - Palamon - Thu Dec 08, 2005 6:14 pm
| kevinc wrote: |
| kusma wrote: | | this has more to do with the fact that to release a piece of code, you need to clean it up |
And that's exactly why I OS my programs, at least in my case it makes me write cleaner code :) (at least for the 3 or 4 other people who will ever read it). |
What do you mean by OS your programs?
#63103 - Palamon - Thu Dec 08, 2005 6:21 pm
| Vich wrote: |
but I wouldn't publish the source of games I make.
|
Why wouldn't you release the source to the games you make?
Don't want people taking it, changing it around a bit for their own game, then giving you no credit? :-)
As for my opinion, I'm more inclined to share the source openly if I really like the result of the program and it is somewhat readable,
otherwise I'd feel kind of embarrassed letting others see my sloppy work, or worse yet, have them comment on poor programming techniques.
But if someone asked for source or help, I'd let them go right ahead.
#63106 - Vich - Thu Dec 08, 2005 6:28 pm
| Palamon wrote: |
| Vich wrote: | but I wouldn't publish the source of games I make.
|
Why wouldn't you release the source to the games you make?
Don't want people taking it, changing it around a bit for their own game, then giving you no credit? :-)
|
Yes, that's one reason. Also, because people might be able to make hacks and cheats more easily and because the game becomes commercially unattractive. Of course I'm not saying that there are big commercial opportunities, but even if the chance is 1%, it's still worth keeping the source scret, considering the other arguments.
| Quote: |
As for my opinion, I'm more inclined to share the source openly if I really like the result of the program and it is somewhat readable,
otherwise I'd feel kind of embarrassed letting others see my sloppy work, or worse yet, have them comment on poor programming techniques.
But if someone asked for source or help, I'd let them go right ahead. |
Ok, that's fair: If someone asks me parts of code of the game, I might send it personally(depending on who's asking what). Of course you can see the difference with just putting it all publicly availalble on a website :)
I like open-source a lot, as long as the benefit of the other people is bigger compared to the benefit for me keeping it closed source.