so. coming back to this because as of this week, there's credible new information on the who and what and why . . . and *if* it is true, then the whole issue was not just an example of a project having a blunder because they grew beyond what its initial leadership structure could handle, but was the result of somebody having personal beef with thephd's proposal and leveraging personal connections to try and squash it
new information
the new information comes from this comment by whitequark on serde's recent change to not use an unverified binary blob as part of its macros, who claims:
The reason I think it’s reasonable to consider something deeper to be going on is: every single Rust controversy I’ve discussed with key Rust people had a lot more going on than was there on the surface. Case in point: dtolnay was also the one thus far unnamed by anyone speaking for the project person who was involved in ThePHD’s talk being downgraded from a keynote. If I see someone acting surreptitiously in one case I will expect that to repeat.
(emphasis added to relevant section).
now you may see this as credible or not. for our part, whitequark is someone who we have enough mutual friends with to respect, so we believe this information to be credible but do consider it on its own merits for yourselves, the personal connection there is a known blind spot of ours. however, thephd has also since stated that others have corroborated this to them privately
why does this matter?
there's a better (and lengthier) write-up of this here by pyrex but for brevity:
- david (dtolnay, maintainer of serde) would have has significant portions of his work affected by any addition of compile time reflection to the language, as large parts of serde rely on making up for this core language deficiency with macros
- if this move was done by him, it stands to reason that his motivations would have come from that impact to his work
- which leaves the question of why *wouldn't* he respond to the compile time reflection efforts via the established technical process?
- pyrex's write-up above posits that this was to protect his position in the community, and we think this analysis holds up:
I believe David Tolnay is trying to release really good code, but I also think these are the behaviors of someone who quite enjoys being a central, load-bearing figure and who likes to be able to make changes basically without review.
anyways, that's the latest happenings in this saga as we understand it, interested if anyone else has any thoughts