But it's par for the course, that's where my growing frustration lies. I can think of two immediate examples off the top of my head because they were two features I heavily lobbied for. The first was reading volume names of USB devices. That came out in v8, but it translated spaces into ASCI "%20". The second was this equalizer (although I suggested a 10-band, 5-band is great). Neither are life threatening by any stretch, but I think it speaks volumes about how the testing process is done. All anyone would have needed to do is take the car home for night to see the equalizer problem, and use all the standard Windows/Mac characters that are allowed for file naming in a couple test scenarios to see if there was an issue in displaying.
I mean really, the list goes on about the bugs still in v8, and they only get worse on the scale of "distracting the driver from driving".
And quite frankly, I'm sick and tired of people accepting less than 100% when it comes to software. This is 5000lb killing machine people, the expectation should be 100%. Then maybe if you miss the mark one a couple things, just fix them ASAP instead of letting them fester for months/years on end. It's one thing to have bugs and not know they exist or how they are caused. But the forum here can usually identify both within 24hrs. And some of the more talented programmers can even offer up causes/solutions without ever looking at the source code. That's talent right there, and it's being wasted currently.
