This is simply untrue. Many developers have supported 8.33kHz spacing for years now, and many that didn’t have had no issue implementing it within a few weeks after this trial was announced (precisely because the community asked them to) - and while I’m not a software engineer, it generally sounds like an arbitrary thing to update.
PMDG is simply an unreliable developer who even promised 8.33kHz support for all their aircraft beginning with P3D v5 over three years ago. It’s not VATSIM’s fault that they lie to their customers and don’t implement long-standing aviation standards even after repeated requests from various people.
Where are you getting this misinformation from? VATSIM clearly stated in the announcement that there are some simulators and/or addons that don’t (yet) support 8.33kHz spacing, so members who made a little bit of an effort to stay informed on any new developments on the network were quickly aware of this trial and had a good idea if it would mean that something changes for them.
And from the discussion on this topic that took place on the VATSIM Discord, it seems clear to me that VATSIM did reach out to developers about this trial (although PMDG apparently gave them the silent treatment).
As I’ve already said above, this has been a looooooong process. VATSIM took its sweet time to make sure only a minimum amount of its users would be adversely affected.
What’s a disgrace is that you are spewing out misinformation and false allegations against the people who sacrifice large parts of their free time to make this network possible for all of us without having any idea about the processes involved in the background. Like Torben says: you’re on a rant. Might not be a bad idea to take a break and come back to this with a fresh and more open mind in a bit.