Because: - UX is important to the average software developer - UX within popular email clients targeting the task of code review is non-existent - UX within

Because: - UX is important to the average software developer - UX within popular email clients targeting the task of code review is non-existent - UX within IDEs for code review is better but: (a) send-email integrations are less polished/mature than they could be (largely due to the dominance of PR/MR flows) and (b) IDE code-review UX is still, despite everything, lagging Web UI code review UX TL;DR: open distributed specs are what we need ideally, but you can't escape the fact that they'll always need much more work to overcome feature inconsistency and niche uses --- I'm really rooting for sourcehut in this battle as I think if it got some adoption we could start seeing improvements to the above problems (they're all surmountable), but I think the biggest thing that's going to help that adoption is sourcehut adding a (good) web UI for their flow, per https://todo.sr.ht/~sircmpwn/lists.sr.ht/111 https://todo.sr.ht/~sircmpwn/lists.sr.ht/111