As your fellow developer, if perhaps at a different level of the stack, I've found that when my runtime performs in ways I didn't expect it too, the eventual so

As your fellow developer, if perhaps at a different level of the stack, I've found that when my runtime performs in ways I didn't expect it too, the eventual solution almost always involves me questioning my own assumptions. The microcontroller didnt get statically discharged, my power rail is pulled to ground with an incorrect resistor. I didn't discover a compiler bug, I put a semicolon after my while statement, but before the curly brace. I've also found that my ability to acknowledge this fact is linearly proportional to the time it takes to solve the bug. My point is that the maintainers of VLC sit atop a mountain of software, used by tons of people with oodles of different use cases. The only methodology that ever allowed them to grow to their current stature has been to do whats right by the project. At some point, the large behemoths of Amazon, Google, et al, have to make compromises as well. If they hire enough support staff to have a personal relationship with every client, at the level of service you get from your local credit union, that becomes prohibitively expensive. In lieu of providing good service, they've settled for efficient service. VLC is Kobe Beef. If Amazon wants to carry Kobe Beef, perhaps they should provide the level of service that Kobe Beef consumers demand. Lots of other folks love to advertise Kobe Beef, but balk at all of the transparency that an authentic Kobe Beef retailer has. Amazon loves to throw its weight around, and claim its for the greater good. But to the extent they can't get what they want, they pull their top selling products from their shelves. They've even done this with books, the one of the markets they dominate to the highest degree. But if we all demand that we be recognized as the one true expert in our fields, compromise becomes a four letter word.