Because he (Tony) is in marketing and that is what trash marketers do. For his potential customers he is trying to puff himself up as the greatest thing since sliced bread but then under his breath mutters about how incompetent he thinks the DNN core and community to be.
I've been steering clear of any of the threads Tony speaks up in but I'm getting sick of his complete marketing garbage. He totally trashes DNN here on the forums, then tries to make it sound like he isn't trashing them in follow-up messages, then proclaims that he is using DNN 5.0 Cambrian on some hot new Windows 2008 Server machines. Yeah, what a load of BS.
I echo the same response I've seen a few times in regards to Tony's messages: if DNN is dropping the ball or falling behind Tony, do you think you could do any better in steering the mothership and moving things along? For any faults or misgivings DNN may have, for any delays on their release schedule, DNN is still a VERY good platform and does well to serve our needs for free.
Anybody in software development realizes that meeting a deadline but releasing crap is so much more damaging than completely missing a deadline but releasing a solid product. In the end, nobody will even remember the missed deadline if the release is solid, but if the release is buggy and crap people will be talking about it for years to come.
So everybody whining about the "promised" release of Q1 2008 for Cambrian (which, BTW, I was present during OpenForce as well and I never got the impression that it really would come out Q1, but that it was a soft target they were hoping for) should just take a step back and wait for a release. Their upgrade paths are typically pretty solid so you don't have to worry about creating a module right now and having it become obsolete with a 5.0 release; just get on with your lives and when the Core is ready for a 5.x release, they'll put it out there. We can all trust that they'll do their part to make sure it is a solid release (just like 4.9 being in RC for several weeks now; they have identified and fixed several issues during the RC time).