There are several great weaknesses of DF that are not the result of the maker's vision but of their limited time and resources.
For example, it is not Toady's vision for the game to get very slow even on powerful hardware when you have a big fortress. This is perhaps a negative blowback of Toady's very laudable vision to have each dwarf be independently simulated. However, an expert in parallel programming should be able to improve this a great deal. AFAIK, DF currently runs as a single thread, and many of its processes can be split off. This is, however, not easy and probably not something Toady is able to or wants to do.
It is also not Toady's vision for the game to be controlled by a mindblowing number of complex menus and obscure key combinations. It was probably not his vision for about half the game controls to be mouse enabled and half of them not. He has admitted himself that the interface needs a lot of work. But he is obviously not working on it, but adding new features like vampires, and Indiana Jones style careening mine carts (last time I checked). I am not saying he should not add those things -- it is a free game and he should work on what is more fun for him. But if he opensourced it perhaps someone else would fix the interface for him.
It is obvious the game needs outside help. People are hacking the game in memory in order to add functionality. Last time I played, you needed to run another program called "dwarf therapist" while playing in order to be able to manage your dwarf's skills and professions. Dwarf therapist would work by directly reading and manipulating dwarf fortress data in memory. Sorry but if the game worked well, nobody would take the time to hack DF just so he can write a helper program.
If they opensourced the game, the people that wrote dwarf therapist could just add that functionality directly into the game.
I say this as someone who loves DF, but has suffered plenty from its frustrations.
Open-sourcing it dilutes their brand. It increases the likelihood that they can't fund it anymore because other people start blathering about their forks and distract from the game's actual mindshare.
> However, an expert in parallel programming should be able to improve this a great deal. AFAIK, DF currently runs as a single thread, and many of its processes can be split off
DF's simulation model is deterministic. Most aspects of it depend on prior aspects. It is a great case of Amdahl's law. Ripping that out and changing it would change the core of his game. I can't really see him wanting that if he doesn't understand it and, like Baughn's work on the graphics subsystem, I can't see him spending a lot of time to understand it. (Toady isn't a computer scientist and he isn't really a hacker as is commonly understood here. He learns what he needs to make his game and it pretty much ends there. This may sound critical but I mean it as a compliment.)
> But if he opensourced it perhaps someone else would fix the interface for him.
His supporters are content with the interface. It isn't preventing them from enjoying the game and it's not hindering their ability to fund continued development. You are suggesting that he potentially damage his revenue stream to fix problems that aren't really problems right now.
I haven't sent him any money yet, so I'm not sure if I count as a supporter - but I am damned not content with the interface. If it weren't for Dwarf Therapist, the game would be nigh unplayable.
I don't see what that has to do with using parallel programming to improve the performance of DF's simulation. If you are implying that threading implies nondeterministic behaviour in a simulation, you are mistaken. In fact, a system with such a discrete space model as DF would be quite easy to parallelize in a safe and deterministic way, with the proper expertise and forethought.
Basically, when starting the game, spawn X threads and partition the world between them so that only one thread can write to any particular world block. Then, when calculating a new frame, make a read-only copy of the previous world frame. Any reads are done from that copy; any writes obviously occur only in the blocks assigned to a particular thread. Wait for all threads to complete, then render thread. No messaging, locking, event handling or whatever needed. Just care and forethought.
But you are right that Toady likely not possessing that kind of knowledge. That's the very reason why people would like to see others involved for things like optimization and UI design and the main point these people are trying to make; Toady seems either not able or willing to do it himself, and it could improve the state of the game tremendously.
This is (arguably) great for the consumer, but as a fellow creator I understand their reluctance to open source their baby.
While I am absolutely an advocate of OSS and I do wish Tarn would go for it, the basic thing is that they dont want to and they love what they do, so deal with it, it's their game.
> They don't want to be delegators. They want to make a game.
Delegation is part of engineering (or not, since these guys have chosen not to delegate). Or part of "making a game" if you prefer. It would be genuinely weird to take the attitude that the only people who "make" a game are the programmers.
Except in indie games all over the place, right? Zeboyd, Spiderweb Software, loads of small developers do exactly this. I do it. I don't want other programmers for something I can do myself because I don't need to share my project with them. It's mine. It's part of me. Bringing more people in lessens its meaning to me.
(I wouldn't contract anything at all if I could do music and art to the level I deem required.)
> Delegation is part of engineering
Whatever gave you the notion that this is engineering? They're not frigging engineers. They're artists.