3 ms·

Good: Fuck plain-text email. We should stop relying on duct-taped solutions from the 70s. Web-based code review solutions are vastly better.

by kanox 6y ago

santoshalper 6y ago
Agree. The problem with github is not that it is web-based instead of email-based. The problem is that it is a proprietary walled garden. An open source direct competitor to github is what's needed, not going back to email as the UX for development.
- kanox 6y ago
  I don't see a shortage of github competitors. For example GitLab works well and also allows for self-hosting.
  - bccdee 6y ago
    But Gitlab is its own walled garden (albeit an open-source one). What we'd ideally have is a platform-agnostic PR protocol. Sadly, we're not likely to get one. That being said, I agree that "let's all use plain-text email" isn't a very good alternative. It's perfectly possible to use Gitlab or Gitea and have the web UI experience without marrying yourself to a proprietary ecosystem.
    - sreevisakh 6y ago
      Is the plain-text the problem? Because Gitlab/hub use them too - as markdown. Their UI layer is built on top of it. Why not do the same thing for emails? Plain-text in SMTP as a communication layer, but a rich UI layer on top of that at client level? Make a combined mail + list + git client?
      - bccdee 6y ago
        I don't have any inherent problem with plain text, I just think that the pull/push/PR workflow is nicer than emailing patches to a mailing list.
    - znpy 6y ago
      But Gitlab is its own walled garden (albeit an open-source one) if it's open source then the garden is not walled -- by definition. This is the kind of scenario where body from gitlab would have all the rights to chime in and say "patches are welcome".
      - bccdee 6y ago
        But it is walled. If you use Gitlab and I use Gitea, I can't submit a PR from a Gitea fork to your Gitlab repo. I have to create a Gitlab account or host my own Gitlab server. Because it's not interoperable, it's a walled garden.
- znpy 6y ago
  Like... Gitlab and Sourcehut ?
Seirdy 6y ago
> stop relying on duct-taped solutions from the 70s I wonder how you feel about age discrimination. Some old tools and ideas (vim, emacs, the UNIX philosophy, etc.) are still going strong because they haven't been beaten by decades of venture capital and SV "disruption"

Good: Fuck plain-text email. We should stop relying on duct-taped solutions from the 70s. Web-based code review solutions are vastly better.

by kanox 6y ago

Good: Fuck plain-text email. We should stop relying on duct-taped solutions from the 70s. Web-based code review solutions are vastly better.

santoshalper 6y ago

Agree. The problem with github is not that it is web-based instead of email-based. The problem is that it is a proprietary walled garden. An open source direct competitor to github is what's needed, not going back to email as the UX for development.

kanox 6y ago
I don't see a shortage of github competitors. For example GitLab works well and also allows for self-hosting.
- bccdee 6y ago
  But Gitlab is its own walled garden (albeit an open-source one). What we'd ideally have is a platform-agnostic PR protocol. Sadly, we're not likely to get one. That being said, I agree that "let's all use plain-text email" isn't a very good alternative. It's perfectly possible to use Gitlab or Gitea and have the web UI experience without marrying yourself to a proprietary ecosystem.
  - sreevisakh 6y ago
    Is the plain-text the problem? Because Gitlab/hub use them too - as markdown. Their UI layer is built on top of it. Why not do the same thing for emails? Plain-text in SMTP as a communication layer, but a rich UI layer on top of that at client level? Make a combined mail + list + git client?
    - bccdee 6y ago
      I don't have any inherent problem with plain text, I just think that the pull/push/PR workflow is nicer than emailing patches to a mailing list.
  - znpy 6y ago
    But Gitlab is its own walled garden (albeit an open-source one) if it's open source then the garden is not walled -- by definition. This is the kind of scenario where body from gitlab would have all the rights to chime in and say "patches are welcome".
    - bccdee 6y ago
      But it is walled. If you use Gitlab and I use Gitea, I can't submit a PR from a Gitea fork to your Gitlab repo. I have to create a Gitlab account or host my own Gitlab server. Because it's not interoperable, it's a walled garden.
znpy 6y ago
Like... Gitlab and Sourcehut ?

Seirdy 6y ago

> stop relying on duct-taped solutions from the 70s I wonder how you feel about age discrimination. Some old tools and ideas (vim, emacs, the UNIX philosophy, etc.) are still going strong because they haven't been beaten by decades of venture capital and SV "disruption"