Forum Replies Created
-
Posts
-
Hey jbusspx,
I gave up using vgdb a while ago. I got tired of all of the many quirks that happen during the development process with this tool. It came to a head when after I had gotten very far and then another weird quirk happened, and I was faced with a choice of starting back over from scratch again, OR abandon vgdb entirely and take a new route. I finally wised up and went on to Visual Code Studio. I’ve been with VSCode for more than 6 months, and I have much better progress.
One of the chief issues – and it IS a big issue even though the support person doesn’t want to admit it – is that many of the tutorials were written for older versions of the vgdb/sysprogs tools that have gone thru considerable changes that no longer correspond with the tutorials. I have mentioned that to him that they need to re-do the tutorials to match up with what the current toolset looks like, to which I got the reply that that was too much work. I completely sympathize that perhaps they are severely understaffed, but that’s no comfort to me or other developers who have been getting headaches from all of the quirks, and getting told that the onus is on us dumb users. They are going to turn off a lot of users with that stance. They need to take a step back and try and look at it from the users’ perspective. I think it can become a very good product, but they need to realize that patience is a two way street.
Cheers,
G
Also, please stop with the insinuation that developers are “making multiple changes to the settings” – this is not the case, and you are definitely turning off customers with that kind of cavalier judgement. Not a good thing.
G
I will do what you suggest, but I can tell you that re-doing things from scratch is precisely what I want to avoid
I can truthfully tell you that always putting the onus for unraveling the problems on the user is a sure fire way of insuring that developers will try to find an alternative to VisualGDB. And given that a good deal of the tutorials were written for previous versions of your toolset has already contributed to a lot of confusion and misunderstandings in your developer community. (there are several examples where the tools have changed significantly, and hence can lead to enormous confusion). And I’ve seen many posts that seem to indicate a reluctance on your part to re-do any of the tutorials.
Perhaps you have a strong customer base with a great deal of knowledge about VisualGDB – good! But right now, I know that I’m not exactly in that same boat, and I wonder how many others there are like me?
But thanks anyhow.
George
