@lemo Stating that you think something that you have never had to use is the laziest way to do something is pretty irrelevant. Your statement does not have any bearing on how useful debugging is, only on your lack of experience with it. Debugging is how you find bugs. Make sense, the name says it all. Can't figure out why something in your physics isn't quite right, look at the output of the calculations in the debugger. Can figure out where a variable is being set in your 30+ event sheets with 1000's of events, set a global watch on the variable and step through the code to watch where the variable changes.
There are millions of reasons that a debugger would actually make all the other features easier to implement as well as easier to troubleshoot when something doesn't work. How many times a day do we get someone saying check my capx because I can figure out why X or Y is happening. A debugger is the way to best hunt down and troubleshoot these issues.
The number one feature of the best developer tools is their debugging capabilities. Writing code is easy, figuring out where it's not working and why is hard. Saying that debugging is lazy is like saying that having a mechanic fix your car is the laziest way to maintain your car.
I am not trying to be mean, but making a blanket statement about debugging while having zero experience with it and hence no context around the statement does not help the statement at all. Feel free to express what you feel is the feature you would want them to work on next, but try to avoid making unqualified bashes on the features that others may want. It does not add anything of use to the conversation.
I have spent the past 10 years working as a developer at a very large software company and without debuggers 90% of the bugs or other issues you find in very day software would never get fixed.
If you write it correctly the first time you don't need a debugger is also a very skewed statement. Someone who wants to divide by zero can write the code for it correctly very easily, that doesn't mean that trying to do it won't crash the application. There are many ways to do something the "right way" that will still cause problems elsewhere. You can write code just fine to bring images and resources into your game, but if you are getting out of memory exceptions, you may want to find out what object is using all the memory in your game. These are just a couple of ways that writing something the right way does not avoid the issue.
Anyway, sorry for the long rant. The right way to promote the idea you want them to focus on is not to bash the others, especially you have no experience with them.BluePhaze2013-04-23 00:59:05