Quote: "We will not shy away from the truth and will meet issues head on."
From a developer's point of view. While we have done well in Classic; have sold developments in classic; and still work in classic, there are some things that we hope do not get carried over onto this development:
* lack of technical support- we had emailed support over an issue one time and got some mumbo-jumbo response that really did not help. I had to email the man himself. I guess that was our bad thinking the people answering the emails actually know the product. And now you have BETA's out of the gate and no real way to report issues or track bugs yet. Take a look on your classic side- how many issues go unanswered? A lot. Why? Because either A) you do not know the answer; B) people told to upgrade (yes, upgrading is the magical answer that solves everything). Are we going to see the same on Reloaded side now? Are each issue going to get the same fair response that others will receive? In other words, for once I would like to hear a valid reply to an issue that will not require the need to "patch" my install with two versions or upgrade.
* lack of knowledge with versions- again, this is a big issue to us. We still work in v1.17 and had a major issue during a development. When we inquired about this (even providing screens, videos, etc), what did we get as a response? "We're beyond that version and unable to assist you in why it is happening". In other words, I would need to scrap the development and upgrade (v1.19 at the time). However, we fixed the issue ourselves.
* lack of finishing- this is a big one for us. We've spent countless hours showing our associates your software, and I know for a fact a few of them bought it and those same people are "humming and hawing" over whether they want to invest into Reloaded or move on. What am I referring to? The fact you left classic in the state it is in. You moved onto Reloaded, clone-stamped your "the focus is on Reloaded now" comment, and classic was being worked on by two community members. Oh wait, as of the other day s4real stated they had no time to work on updates (and those are the unofficial). What about compiling a final finished official so that users can use it? Some of the people I spoke of earlier are still in BETA waiting and waiting, while one has downgraded, and another is contemplating moving on. While we use v1.17, we have a development we're about to start and are wondering if we should at least upgrade to the final version (v1.20). But it's still stuck in limbo after how long? Can you guarantee that Reloaded will not suffer the same fate? Convince me that it is worthwhile to move all developments from classic to Reloaded and that there will be a finished "workable" version.
Quote: "Perhaps people can moan in a more positive way? "
I am sorry, but from where I stand it is really hard to moan in a "positive way" when we've had to deal with the above. It seems that only a "select few" get heard and the rest get ignored. So how would you like us to be positive? Shall I tell our associates "don't bother investing; I'm positive we're all better off using something else", or does our money not matter. While our moans have to do with Classic, I hope that these habits are not carried over into Reloaded. I don't want to have to deal with these same issues if I and my associates I spoke of invest money and years into this only to see it all repeated. We're not anti-TGC and have always been proud showing our work and such with it, but please understand that these items I mentioned may seem small and insignificant to some, they are big things to small developers like us and our associates. Our team is small- it consists of myself, my wife, my daughter, and a couple others. We have to do all our own work, and we have invested a lot of time in our developments. We get opportunities to present our work to other companies and clients. And we do talk to other companies- in other words, word of mouth goes a long way.
There's no problem that can't be solved without applying a little scripting.