3 ms·

Never going to happen. There's zero time to do any of that while running HN. pg barely was able to do it, and he cared a lot about whether the world wanted to

Never going to happen. There's zero time to do any of that while running HN. pg barely was able to do it, and he cared a lot about whether the world wanted to use arc. > it would really benefit from having the real latest version (or as close to that as is possible). I independently implemented almost every feature in HN. But it exists in a repository that gets autokilled whenever I link to it here, so, that's about par for arc's progress in modern times. Took so much work to get all the features done. Even implemented Dan's thread-local state ideas. Never gonna see the light of day. The fact is, Arc's progress stopped with pg. It's best to accept that and move on. It's tempting to think you need the latest in order to understand arc's power. But take it from a decade-long arc veteran: that's not true. All you need is to tug at the question, "why did pg do it this way? out of all possible ways, why this?" And then realize that HN today could not have happened if pg had done it any other way. If you care enough about this question, you'll come to respect arc. Especially what was left out, as much as what was implemented. Less is more. Over the years I've implemented at least 5 different flavors of arc, including a fusion of lumen and arc, both on lumen (javascript-based) and in arc (racket-based). I always come back to vanilla arc and vanilla lumen as starting points. And there's a reason for that. The more you add, the more you lose. The flexibility is the power, and the flexibility is a result of arc's smallness. By the way, pg did exactly what you said, in the original release of arc. If you grep the codebase for "defhook", those are all the spots where the secret code was refactored out.

skissane 5y ago
> Never going to happen. There's zero time to do any of that while running HN. What if someone volunteered to do it? I assume it would have to be someone whom dang/YC/etc knew and trusted, since they'd learn the "secret sauce" in the process. I don't know if any such person exists right now, but even if they don't, maybe they will in the future (neither motivation nor trust are static quantities.) > But it exists in a repository that gets autokilled whenever I link to it here, Strange. How about you put the link in a reply to this comment, and we'll see if it "gets autokilled" (tagged dead). I'm assuming that if that is happening, it is some kind of false positive, not an intentional moderator decision – in which case, someone should be able to vouch your comment and undead it. > By the way, pg did exactly what you said, in the original release of arc. If you grep the codebase for "defhook", those are all the spots where the secret code was refactored out. I get the impression it hasn't been kept so clean in the current codebase – because I've heard the work involved in separating the secret bits from the public bits is the main reason there hasn't been another public source release. If the current code base kept the secret and public bits clearly separated, then that justification doesn't make any sense.
- sillysaurusx 5y ago
  > Strange. How about you put the link in a reply to this comment, and we'll see if it "gets autokilled" (tagged dead). Here it is: https://github.com/laarc/laarc https://github.com/laarc/laarc I put years of work into it. As I said, this comment is dead: https://i.imgur.com/JmMdQ8i.png https://i.imgur.com/JmMdQ8i.png I'm pretty sure this comment can't be vouched, too. > I'm assuming that if that is happening, it is some kind of false positive, not an intentional moderator decision – in which case, someone should be able to vouch your comment and undead it. Heh. It was intentional. Though if Dan ever reverses the decision, he might try to claim otherwise, since technically the goal was to ban mentions of our HN competitor. Feel free to DM me on twitter if you want to discuss it further. https://twitter.com/theshawwn https://twitter.com/theshawwn
- sillysaurusx 5y ago
  >How about you put the link in a reply to this comment, and we'll see if it "gets autokilled" (tagged dead). Okay, here you go: https://news.ycombinator.com/edit?id=30576525 https://news.ycombinator.com/edit?id=30576525 The reason this took four hours is because every time this topic comes up, I get terrified, and I can't bring myself to check HN at all. So I didn't see your request till now. (The fear is much the same as his: https://www.youtube.com/watch?v=QxTMbIxEj-E&t=16s&ab_channel=TheTwilightZone https://www.youtube.com/watch?v=QxTMbIxEj-E&t=16s&ab_channel...) As I mentioned there, you can contact me via Twitter (https://twitter.com/theshawwn https://twitter.com/theshawwn) or by email (shawnpresser@gmail.com). I recently started using Telegram too. It's pretty nice. (https://t.me/theshawwn https://t.me/theshawwn) Otherwise, it looks like there's no way to reach you, so I'll simply say that I hope you have a wonderful week. Take care.
  - skissane 5y ago
    I can only guess at what is going on in Dan's head, but I think he banned mention of your "fork" of the HN community because people felt that it was being promoted in a "spammy" way. I don't think he is banning it simply because he hates competition and doesn't want its existence mentioned - if that was his reason, why are people allowed to freely discuss and link to another such "fork community", lobste.rs? [0] The fact that your fork of the Arc language and HN forum software has the same name means the same autokill applies to it as well. I suppose if you changed the name of the language/software fork to something else, it would no longer be subject to the ban. (I am assuming the intended target of the ban is the website not the language/software which runs it.) [0] https://news.ycombinator.com/from?site=lobste.rs https://news.ycombinator.com/from?site=lobste.rs

skissane 5y ago

> Never going to happen. There's zero time to do any of that while running HN. What if someone volunteered to do it? I assume it would have to be someone whom dang/YC/etc knew and trusted, since they'd learn the "secret sauce" in the process. I don't know if any such person exists right now, but even if they don't, maybe they will in the future (neither motivation nor trust are static quantities.) > But it exists in a repository that gets autokilled whenever I link to it here, Strange. How about you put the link in a reply to this comment, and we'll see if it "gets autokilled" (tagged dead). I'm assuming that if that is happening, it is some kind of false positive, not an intentional moderator decision – in which case, someone should be able to vouch your comment and undead it. > By the way, pg did exactly what you said, in the original release of arc. If you grep the codebase for "defhook", those are all the spots where the secret code was refactored out. I get the impression it hasn't been kept so clean in the current codebase – because I've heard the work involved in separating the secret bits from the public bits is the main reason there hasn't been another public source release. If the current code base kept the secret and public bits clearly separated, then that justification doesn't make any sense.

sillysaurusx 5y ago
> Strange. How about you put the link in a reply to this comment, and we'll see if it "gets autokilled" (tagged dead). Here it is: https://github.com/laarc/laarc https://github.com/laarc/laarc I put years of work into it. As I said, this comment is dead: https://i.imgur.com/JmMdQ8i.png https://i.imgur.com/JmMdQ8i.png I'm pretty sure this comment can't be vouched, too. > I'm assuming that if that is happening, it is some kind of false positive, not an intentional moderator decision – in which case, someone should be able to vouch your comment and undead it. Heh. It was intentional. Though if Dan ever reverses the decision, he might try to claim otherwise, since technically the goal was to ban mentions of our HN competitor. Feel free to DM me on twitter if you want to discuss it further. https://twitter.com/theshawwn https://twitter.com/theshawwn
sillysaurusx 5y ago
>How about you put the link in a reply to this comment, and we'll see if it "gets autokilled" (tagged dead). Okay, here you go: https://news.ycombinator.com/edit?id=30576525 https://news.ycombinator.com/edit?id=30576525 The reason this took four hours is because every time this topic comes up, I get terrified, and I can't bring myself to check HN at all. So I didn't see your request till now. (The fear is much the same as his: https://www.youtube.com/watch?v=QxTMbIxEj-E&t=16s&ab_channel=TheTwilightZone https://www.youtube.com/watch?v=QxTMbIxEj-E&t=16s&ab_channel...) As I mentioned there, you can contact me via Twitter (https://twitter.com/theshawwn https://twitter.com/theshawwn) or by email (shawnpresser@gmail.com). I recently started using Telegram too. It's pretty nice. (https://t.me/theshawwn https://t.me/theshawwn) Otherwise, it looks like there's no way to reach you, so I'll simply say that I hope you have a wonderful week. Take care.
- skissane 5y ago
  I can only guess at what is going on in Dan's head, but I think he banned mention of your "fork" of the HN community because people felt that it was being promoted in a "spammy" way. I don't think he is banning it simply because he hates competition and doesn't want its existence mentioned - if that was his reason, why are people allowed to freely discuss and link to another such "fork community", lobste.rs? [0] The fact that your fork of the Arc language and HN forum software has the same name means the same autokill applies to it as well. I suppose if you changed the name of the language/software fork to something else, it would no longer be subject to the ban. (I am assuming the intended target of the ban is the website not the language/software which runs it.) [0] https://news.ycombinator.com/from?site=lobste.rs https://news.ycombinator.com/from?site=lobste.rs