3 ms·

The skills you have to learn in order to use github effectively are pretty generic in nature and easily transferable to other platforms.

toastal 4y ago
Is that why most people don't know stack-based Git flows or how to using send-email? GitHub only really works on the pull request model which is not the only way to use Git. There are pros and cons to these workflows, but if skills are generic, then you can just say "Git" or "Git forge" without needing to specify a platform.
- antihero 4y ago
  Most major platforms use pull/merge requests.
  - toastal 4y ago
    PostgreSQL uses a mailing list and Google uses Gerrit to name two "major" counters. There are plenty of big projects and orgs operating under different models.
    - antihero 4y ago
      I'm talking about stuff like Gitlab, Bitbucket, etc. What I am saying is that most of the paradigms that GitHub has have familiar if slightly different implementations in other places.
      - toastal 4y ago
        But they aren't the only ones, nor the only ways. It's not necessary to know other paradigms, but knowing of their existence is nice, but also they should never be discounted as lesser methods of doing source hosting and code review--especially when used by large orgs and projects.
- noirscape 4y ago
  send-email/stack is very niche in use from my experience. Only the Linux kernel and SourceHut really make heavy use of it (and from what I've heard, SourceHut is also looking into at least giving developers the option to not need to use send-email, but no clue how far that is). The reality is that tools like send-email just... don't really work under the current email oligopoly (since the big providers both heavily filter emails and generally consider IMAP to be insecure). That entire model dates back to the days where email accounts mostly were tied to universities and as a result an emails name had a lot more meaning. Heck, even for the kernel, send-mail is starting to fall out of practice because it just renders like shit in most email clients. It's a rather dated model. The pull request flow is the de-facto industry standard, basically all but the oldest git-based projects use it. Not all are on GitHub (since it's proprietary or just straight up issues with GitHub as a company), but even when they aren't, self-hosted git servers like gitea and gitlab are both still using that exact flow. The examples where this isn't the case are generally rare enough that they're worth more learning as a procedure for that project than as an easily transferrable skill.

toastal 4y ago

Is that why most people don't know stack-based Git flows or how to using send-email? GitHub only really works on the pull request model which is not the only way to use Git. There are pros and cons to these workflows, but if skills are generic, then you can just say "Git" or "Git forge" without needing to specify a platform.

antihero 4y ago
Most major platforms use pull/merge requests.
- toastal 4y ago
  PostgreSQL uses a mailing list and Google uses Gerrit to name two "major" counters. There are plenty of big projects and orgs operating under different models.
  - antihero 4y ago
    I'm talking about stuff like Gitlab, Bitbucket, etc. What I am saying is that most of the paradigms that GitHub has have familiar if slightly different implementations in other places.
    - toastal 4y ago
      But they aren't the only ones, nor the only ways. It's not necessary to know other paradigms, but knowing of their existence is nice, but also they should never be discounted as lesser methods of doing source hosting and code review--especially when used by large orgs and projects.
noirscape 4y ago
send-email/stack is very niche in use from my experience. Only the Linux kernel and SourceHut really make heavy use of it (and from what I've heard, SourceHut is also looking into at least giving developers the option to not need to use send-email, but no clue how far that is). The reality is that tools like send-email just... don't really work under the current email oligopoly (since the big providers both heavily filter emails and generally consider IMAP to be insecure). That entire model dates back to the days where email accounts mostly were tied to universities and as a result an emails name had a lot more meaning. Heck, even for the kernel, send-mail is starting to fall out of practice because it just renders like shit in most email clients. It's a rather dated model. The pull request flow is the de-facto industry standard, basically all but the oldest git-based projects use it. Not all are on GitHub (since it's proprietary or just straight up issues with GitHub as a company), but even when they aren't, self-hosted git servers like gitea and gitlab are both still using that exact flow. The examples where this isn't the case are generally rare enough that they're worth more learning as a procedure for that project than as an easily transferrable skill.