Well Veazer, we are on the same side; however, I like to think of us as a bunch of spoiled kids, for we have grown accustomed to getting what we want, when we want it from the dev team @ J River. As soon as they put the smack down and give an emphatic "No", we start to wonder "wtf"...hehe.
Let's face it: NO company gives as much reign to user input as these guys do, and they do put up with a LOT from us. I've been on both sides of the equation as a user and as a Systems Analyst developing system configurations, software, and network policies for Big Brother, and believe me, these guys bend over backward for us. We do test their limits, and eachothers at time (hence, this thread), but overall we are one big collective of enthusiasts trying to reach a common goal. I've been perusing these forums for a couple of years now and only recently started posting, and I have noticed that, although much of what we put up here is fragmented and seems to go unnoticed by anyone but moderators and ourselves, overall we get what we want -- when feasible --. The dev team is trying to take MC to the next level to stay both competitive and usable with this new release. To do so means saying goodbye to old standards in some ways, such as legacy hardware and software. It is not any inherent evil intentions on their part, but someone simply has to take the reigns and charge forward. This will piss off some people, but ultimately please everybody. Then we all band together and take them on when they try to do so. It is an unfortunate side effect of programming in the windoze environment that applications are getting to require so much horsepower and programming overhead. Don't blame J River, blame Microsoft for making such an inane, bug-ridden API. There are SO many things that Microsoft documents for developers that simply DO NOT WORK the way they are documented. I used to spend more time programming workarounds than I did actual, documented code. Things may have changed a bit in recent times, but from what I have gathered not too much has.
This thread is full of good intentions gone misinterpreted as mentioned earlier. We all want the same thing, but seem to want to protect eachother from, well, eachother. The good side of this is the inherent system of checks and balances that occurs between the userbase and the developers. Just as I mentioned it is good that they take the reigns and charge forward, it is just as good that we at times tell them to pull back and slow down. We just need to chill out and understand eachother.
Geez....I just wrote a book, didn't I? LMAO...I do that sometimes... just smack me and tell me to shut up
Cheers everyone.
-Rob-