Earlier quoted context omitted.
> and yet we both conclude it is blockable Extremely polarizing language for something that is way more a scale to me, and I don't agree that this technology is blockable. I already elaborated some scenarios where hosting can respawn easily, with no coupling to any particular infrastructure. That to me is pretty unblockable. There's other resilliencies offered here. The story keeps getting better, given all the resil…
Please don't argue in the flamewar style on HN. We want curious conversation here. https://news.ycombinator.com/newsguidelines.html
I very much think resolving this conversation is of the utmost importance, is absolutely core to the topic at hand. There should at least be some idea of what the criticism here is. I would really like to see that.
I have not at all been perfect. But I have tried to surface technics, to get to the heart of the technical matters at hand. To illuminate & increase the information here, in the core topics at hand.
I respect your intervention here dang & agree this is going bad. And I could improve. But I think I am very very very narrowly not-passing here, and this seems like an essential defense to me. I've been wanting very badly to get to the real topic, to affirm & help us to work with the next HN rule after "Eschew flamebait":
> Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.