The "just write this one program" philosophy always just yields one program at most. The "add software to the community" approach might add only 1/10th of a program, but with thousand people doing it you get 100 programs out of it. Which approach looks more reasonable?
Or to give another example how many people can enjoy Game of Thrones because it's written in English? (I'm German and I love it!) If it would have been written in a minority language that is only spoken in one village somewhere in central Asia it might have been more comfortable for the developer, but only few people can ever take joy in it.
They don't need to make the program work on all systems or use a fancy new language. They just need to enable the community and make use of development patterns that are flexible. Java certainly is not a fancy new language, and despite it's claim it only really works on Windows well enough out of the box. Yet Minecraft has an open community where even the developers profit from what others add to the game. When the coders of DF die in an airplane crash tomorrow DF is pretty much dead as well and that's the big problem I think. If I invest my whole life to create an awesome piece of work, then it should surpass me in number of years.
Going along with your analogy, it's very possible that if this central Asian George R. R. Martin was deterred from writing Game of Thrones in his native language because it isn't "reasonable" for others to expect to read his works, then maybe it would never have come into existence in the first place.
Look, I understand your point but sometimes when you want something done you don't mess around and care about what other people want. You just do it in whatever way is easiest for you. Saying you "hate" these people who actually have CREATED these things that have added value to people's existence seems really rather immature. It's not like lives are going to be saved because DF was open sourced.
> When the coders of DF die in an airplane crash tomorrow DF is pretty much dead as well and that's the big problem I think. If I invest my whole life to create an awesome piece of work, then it should surpass me in number of years.
What reason do you have for your belief that the community's development of DF (after the plane crash) will be according to the founder's great vision? I openly say that it's perhaps better if in this case the further development of DF is ceased than developed into a direction that is opposed to the original developer's goals.
Or to give another example how many people can enjoy Game of Thrones because it's written in English? (I'm German and I love it!) If it would have been written in a minority language that is only spoken in one village somewhere in central Asia it might have been more comfortable for the developer, but only few people can ever take joy in it.
They don't need to make the program work on all systems or use a fancy new language. They just need to enable the community and make use of development patterns that are flexible. Java certainly is not a fancy new language, and despite it's claim it only really works on Windows well enough out of the box. Yet Minecraft has an open community where even the developers profit from what others add to the game. When the coders of DF die in an airplane crash tomorrow DF is pretty much dead as well and that's the big problem I think. If I invest my whole life to create an awesome piece of work, then it should surpass me in number of years.