So in a nutshell, the game is proceeding in development hell.
There, I condensed your handwavey comment into something rather more representative of where CIG is with Star Citizen's development.
Also, the fact that you can look at that dog's dinner of a "schedule" CIG posted a couple of days ago and say, with a straight face, that "Everything is awesome and going according to plan!", is rather telling really.
But sure, do get your wallet out again to financially back Roberts' Vision, he'll be very glad of your unwavering support.
[Edit]: I mean, it's not like Chris Roberts, during CitizenCon last year, didn't get up on stage and produce a list of the features that will be in 3.0, along with a flashy (buggy as heck and stealing from as many sci-fi movie/book franchises as it could do) demo showing backers what it would look and "play" like. And it isn't like they put a date up there during the presentation stating that it would be mostly ready for backers to play-test by December 2016.
Oh.... that's right... He DID!
So how is it, now 4 months past the time 3/0 was supposed to drop, have CIG only just NOW produced a *schedule* of the work they'll have to do to make 3.0 a reality? On top of that, why are several of the key features that were mentioned to be part of 3.0 last December have now been pushed back until much later this year, or have been completely omitted from this hacked job of a schedule altogether?
[Edit 2]: Also, why do you continually insist on calling what is currently available in Star Citizen an "Alpha"? From what is currently playable for backers and the public (during free flight weekends), what is there would qualify as a tech demonstration at best. The only reason folks could sorta make the claim that it's an Alpha is due to the quality of the object assets used in the PU, Arena Commander, Hangar module and Star Marine.
However NONE of those modes have enough working content and a stable enough platform to justify the "Alpha" moniker. So no, people *can* mention the crippling bugs quite correctly and wonder why some of them that have affected the PU since it's release in 2015 are STILL showing up in 2.6.3... along with rafts of new bugs as well.