Thinking outside the compiler for a second...maybe a minute....

Because it's not just about the compiler what it can do and how it manages to do it. It's about the reasons why QB64 even exists in the first place.

1. It was not created to compete with FB so everyone get that out of your heads.
2. It was not created solely for the purpose of running any QB code though this is it's most noble reason.
3. Galleon happens to think FB is straying from it's original goal, he decided to do something about that. And the problem with that is? Cause I can't see any. ;-).

Thinking outside the compiler, have you looked at the feature set added that has nothing to do with QB Compatibility so far? And the rest of what's planned to be added atop QB Compatibility without breaking it's compatibility?

Also, take a look around everywhere. Look at the millions of lines of code, good code, exists for QB and the likes. Very useful routines and algorithms, tools, utilities and complete programs. Let's not forget the GUI projects too. NOt sure about you, but I don't wanna see that disappear or archived to be admired, I wanna see how they work, see what I can learn from them (no matter how old the samples may be.

I've never seen you complain this much about FB either (cept maybe when 0.16 came out ;), some, but still not as bad). Galleon chose to show us the progress as it happens, vi1c chose to wait until a minimum set of stuff was done. It's a choice, it's not a right or wrong way to present your project to people. Aside Paired programming, he's following every piece of extreme programming ;-) You can read up on that here:

http://en.wikipedia.org/wiki/Extreme_Programming

What you choose to use for a language/compiler is of course your choice alone. What others choose to use is their choice alone to. I think that's where it needs to stop. People aren't idiot for making a choice.