Why Nostr? What is Njump?
2023-09-06 18:52:50

ThePhD on Nostr: As I have no intention of being publicly smeared but private apologized to, I am ...

As I have no intention of being publicly smeared but private apologized to, I am writing this post as an immortal (for as long as my instance lasts, anyways) record of my response to an e-mail I have just received from David Tolnay. My response is brief and enclosed just below:

“Dear David,

     I have no intention to have a (private) video call to resolve an intensely public and, at this point, explosively volatile situation that never needed to be. I have also pulled out of the work and we will not be engaging with the Rust Specification work or anything related to compile-time reflection, so there's no reason to apologize at this point because the (metaphorical) vase is already broken.
     As I stated over 3 months ago when this first kicked off, the only thing (even if it was published anonymously, again, before this ever blew up) was a technical critique of the work presented. If you do not have a technical critique to offer, then I would like to not hear from you or anyone else on the subject material for the next few years at a minimum.

JeanHeyd”

As ever, I am consistent: the damage is done, but several people have spoken up that they would like to continue the work. If you fervently believe this was a fuck up, you will write out why the compile-time direction Shepherd Oasis wasted tons of money supporting me through and collaborated on by a dozen+ different people who are titans in their respective focuses is Bad, Actually so we can put the idea to rest and the Rust Project can go do more productive things.

It would also probably help if that response did not take a peer's work, label it a bungling failure, and then use it as a projection field to say the work would never be ready, too.

That would also be helpful.
Author Public Key
npub19pz4w2q5uvs9jz8aydmgk9pgtgpmdy6380aekuy8gdvjfvztcx0qnu862l