
By konc3pt
Tue Apr 29, 2014 4:28 pm
this dude trapped in time warp rockin classic mpcs and gear with tags still on it...that shit was early 2000 


fdodds wrote:They wouldn't be rewriting everything, they would need to do some rewriting for how the mixing is handled and how automation is handled, but that doesn't mean rewriting everything. Software is inherently flexible, if a development team is professional and following 'good practice' it is simple to change things on the fly, add features, tweak features etc.
It's ridiculous to expect/demand super strict development cycle times. As a user it's easy to say ".1 .2 .3" updates should be super quick but as a developer the reality is that these things take as long as they take. I really feel like it's a bratty attitude - think about if you're hiring a contractor. They can give you an initial quote of how much it costs, but until they get into your house and start actually working on the problem they can't be certain how long the repair will take. Software development is ongoing, you are constantly repairing old problems while also building new features and making them play nice with the pre-existing structures, that's a reality of software and any complaining or ideas about how it should be won't change that.
Louie lou wrote:Anything .1, .2, .3, etc should be released often. any 2.0, 3.0, etc should not take more than 180 days to release.

