4 ms·
Ironic that Steve Klabnik jumped in on the ridiculing, when he a) Complains all the time about people mocking Rust, and b) supported the various "rewrite in Rus
by lelanthran 4y ago
Ironic that Steve Klabnik jumped in on the ridiculing, when he a) Complains all the time about people mocking Rust, and b) supported the various "rewrite in Rust for no good reason" projects.
- simplotek 4y ago> Ironic that Steve Klabnik jumped in on the ridiculing, when he a) Complains all the time about people mocking Rust, and b) supported the various "rewrite in Rust for no good reason" projects. To be fair, this tweet was close to a decade ago, and Steve Klabnik posted an apology at the time. People do make mistakes from time to time, and Twitter is prone to post unfiltered brainfarts.
- chris_wot 4y agoHe did acknowledge it later: https://steveklabnik.com/writing/trolling-is-a-art https://steveklabnik.com/writing/trolling-is-a-art
- maverwa 4y agoThis is dated "September 24, 2010", so this would be earlier, not later, right? Or is the date stamp off?
- maverwa 4y agoI also buy his "Twitter makes it so hard not to accidentally be an asshole" claim. Its really hard to make a complex argument in 140 characters (as it was back in 2013), even if he wanted to. The short format really invites these "just a few word" opinion pieces. I think its easy to see how this, given the right ingredients, can trigger a misunderstanding or at least an incomplete understanding. Text lacks a lot of context humans usually communicate via voice and facial expressions. Lowering the information even more by restricting the amount of text can make it hard to convey the intent. I am not saying "his tweet was fine, just misunderstood" here btw. I do not know his indent when writing this tweet. And I think its on the author to make sure their message can reasonably be understood as intended. But I also see how something like this can happen without malintent on the authors side.
- rpigab 4y agoI didn't use Twitter much, but each time I did, it was so frustrating to limit what I wanted to express in less than 280 characters, and splitting felt stupid. So I removed the less important words, replaced long words with short ones, then when it finally fit the limit, I didn't press send, just read it again, and hated it because it was oversimplified, limited my vocabulary, made generalizations without caution, etc. I can easily see how it can turn normal people into dumb assholes, especially since there's the dopamine rewards of having tons of likes, retweets and comments, incentive to be extreme, by being extremely positive or extremely negative.
- throwaway_au_1 4y agoTo add: I find the "Twitter makes it hard" remarks a total cop-out in this instance. One is responsible for ones conduct whether it's via Twitter, in person, or a series of smoke signals. Am I supposed to believe that a character limit is in some way an excuse for being an arsehole? Those tweets lacked _any_ attempt at nuance so to respond by saying "oh it's hard to express myself accurately with only n characters and this time I came off as a prick" is just utterly ridiculous.
- BlueTemplar 4y agoThere is that, but the systemic issue holds too : my rule of thumb is that if you use Twitter, then you are an an angry asshole or idiot (until proven otherwise).
- maxbond 4y agoTo be fair though, this was a decade ago, and he also published an apology; personally when I see people treating others badly, in a way I've treated others badly, it bothers me more than it otherwise would've, so it's entirely possible experiences like this are why a.) bothers him.
- pinkcan 4y ago"rewrite in Rust for no good reason" `sudo` just had an array-out-of-bounds CVE https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-43995 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4399...
- lelanthran 4y ago> `sudo` just had an array-out-of-bounds CVE https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4399 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4399... So? Sudo is so notorious for being a mess that the BSD people made their own - doas. Rewriting sudo is "for no reason" when doas already exists. You're effectively rewriting doas.
- rpigab 4y agoThis sounds oversimplified. sudo is complex, and people had a simpler usecase, so they used a simpler alternative. Some people need the complex features, and it's fine, and maybe they're fine with the risk of a difficult to audit codebase and risk of catastrophic failure, and we don't need any new alternative, so they can continue to use sudo as it is. "The core of the problem was really that some people like to use sudo to build elaborate sysadmin infrastructures with highly refined sets of permissions and checks and balances" -- tedu https://flak.tedunangst.com/post/doas https://flak.tedunangst.com/post/doas So a rewrite of sudo is Rust could add value by allowing it to add complex features, and keeping memory safety, even if code auditing would stay complex, and small logic errors can have catastrophic outcomes.