Conversation

Notices

Embed this notice
Paul Cantrell (inthehands@hachyderm.io)'s status on Monday, 29-May-2023 14:12:16 JST Paul Cantrell
in reply to
- wakame
- Dana Fried
- Vrimj
@wakame @Vrimj @tess
The obligatory form: “This language has a toxic purity culture!” “Feh, whatever, LISP had that 30 years ago”

In conversation Monday, 29-May-2023 14:12:16 JST from hachyderm.io permalink
- Embed this notice
  wakame (wakame@tech.lgbt)'s status on Monday, 29-May-2023 14:12:17 JST wakame
  in reply to
  - Dana Fried
  - Vrimj
  @Vrimj @tess
  What? LISP doesn't have a toxic purity culture. We can't even decide which implementation is the best one...
  
  In conversation Monday, 29-May-2023 14:12:17 JST permalink
- Embed this notice
  Vrimj (vrimj@mastodon.sandwich.net)'s status on Monday, 29-May-2023 14:12:18 JST Vrimj
  in reply to
  - Dana Fried
  @tess Has rust finally outstripped LISP as the language with the most toxic purity culture?
  
  In conversation Monday, 29-May-2023 14:12:18 JST permalink
- Embed this notice
  Dana Fried (tess@mastodon.social)'s status on Monday, 29-May-2023 14:12:19 JST Dana Fried
  
  Context: https://pony.social/@thephd/110446817486174177
  In conversation Monday, 29-May-2023 14:12:19 JST permalink
  Attachments
  1. "We should improve society meme" except that it says: "We should improve rust somewhat." "And yet you program in rust. Curious. You are uninvited from rustconf."
    https://files.mastodon.social/media_attachments/files/110/447/727/430/893/483/original/5369b66acd06ac4c.jpg
  2. No result found on File_thumbnail lookup.
    
    ThePhD (@thephd@pony.social)
    
    from ThePhD
    
    So, after a full day and a lot of back and forth, a few very important things have come to light. I'll try to summarize them here because I've been posting primarily in the Bad Places® rather than the Good Places™, so that nobody's lost. - It looks like somebody from inside the Rust Project, but not with the consensus of all leadership, tried to downgrade my talk (or perhaps have it outright retracted) because they did not like the direction the compile-time work I was doing. (Learned from: https://www.jntrnr.com/why-i-left-rust/) - The decision to downgrade my talk, once it was known I was going to talk about Compile-Time Reflection in Rust, came anywhere from 4 to 8 days before I was actually told this past Friday and had to release the blog post stepping away. However, as evidenced by much of the public statements from existing, ex, and now-ex Rust Project members, the decision to unilaterally downgrade was not known to many of them until they read my post. - Downgrading the keynote was NEVER voted on like inviting me to do the keynote in the first place. All in all, this reeks of someone trying to run-around the consensus of the Rust Project because they don't like Shepherd Oasis's or my work (detailed here: https://soasis.org/posts/a-mirror-for-rust-a-plan-for-generic-compile-time-introspection-in-rust/). I don't know how to handle this going forward. The Rust Project has effectively ultimate commit rights to rustc and all of the projects our work would touch are under the control of the organization that did this. Even if we do the work, they could effectively unwind and undo a lot of our work, or indefinitely block it with an endless slew of "reasonable concerns" from ranking project members who seem to have problems but don't want to communicate them except by taking potshots at the status of my now-gone RustConf talk. I don't know what to do. I'm pretty lost, it's Sunday, and I have a shitload of things I still need to do, not including this whole trainwreck.

Public

Conversation

Notices

Feeds