And that, is why you fail.
Any change in the "interface" will break compatibility with the third-party GUI. Either Toady needs to tiptoe around this so as not to upset the GUI, or he doesn't give a crap and breaks it anyway. If enough people are using this GUI, there's an uproar and people bitch and moan and nobody will play the new version until the GUI is fixed.
It's different from changing a few tiles. While I love using the graphical raws, I have no problem using the regular ASCII interface in the meantime. People who get used to a complete GUI revamp just won't want to touch the ASCII one with a 10-feet pole.
First off, you sir, don't know what you're talking about. Obviously you have no experience at all with software development. If you did you would realize that a simple well-thought out API would have no need to be broken every time Toady wanted to implement a new feature.
Oh my, a giant ad-hominem, let's address that. My good sir, you couldn't be able to figure out an API if it spat you in the eye and sodomized your dog. Obviously, you have never seen a "computor", and instead you have to resort to have your blind neighbor post these nonsense replies for you while you make cooing noises and point at the pretty pictures on the screen.
Now, with that out of the way, I just happen to make APIs for a living, I am a computer analyst and programmer and I have been since the 1980s. I've programmed in BASIC, Pascal, C, C++, 8086 assembler, C for Windows, Java, and a bunch of stupid 4 GL languages that are good for nothing. A "well-thought API" is exactly what you WOULDN'T have during the alpha stage of a fan project.
Changing the internals of a library is quite different from changing the API.
Changing the internals WITHOUT changing the API is exactly "tip-toeing". Unless you have a feature-frozen product, you don't want to distribute your API to everyone, with the (implicit) promise that future versions won't break API compatibility.
...snipped other replies to a post that apparently wasn't made, except in your imagination... strawman, I presume.
Lastly you make the incorrect assumption that everyone favors graphics over ASCII. That simply isn't the case. I personally play games that are ASCII, 2D, 3D, etc. Graphics ultimately don't matter that much to me. What does matter is having a decent interface and good gameplay. Gameplay is already covered just fine by Toady, but the interface is currently just a hack job that I would expect any developer to make until the core gameplay is implemented.
We are discussing interfaces. Application Program Interfaces, right? So anything I've said about "GUI" applies to any other kind of interface for the same reasons: people grow dependent on them. They don't just "add" to the basic gameplay in the way custom tiles or modding does. They force the developer to at least make an effort to keep backwards compatibility (we all know what good that did for Microsoft WinDOS), which is clearly, as anyone with a grain of experience with programming will know, not a good idea to do in the alpha stage of a fan project. Alpha means UNSTABLE, if you don't know (you should pick up a book about programming someday, you might learn something). Regardless of the "testing" stage, it means that ANYTHING can change. Maintaining backwards compatiblity with a poorly-thought-up API during early stages of development would only lead to a maintenance hell and slow the feature releases to a grinding halt.
That's all I've got to say about this topic. So please, any further comments about having "no experience at all with software development", you can keep them to yourself.
Cheers!