Live data from Hacker News

Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)

protesilaos.com

1–10 of 73 posts

Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)

#2
The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one).

Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a busy community outweigh the drawbacks of too many PRs in my opinion

Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)

#3
post #2

The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…

Shouldn't we call it a "network prison" in that case? :)

Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)

#6
post #2

The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…

Why wouldn't this possible on, say, GitLab or Bitbucket?

Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)

#7
post #5
post #4

But the network effect could lead to something like the next xz backdoor

If xz would have been hosted another place, what could have been prevented?

That maybe fewer people would have even known about it and therefore decreased its importance as a target? /s

Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)

#8
post #6
post #2

The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…

Why wouldn't this possible on, say, GitLab or Bitbucket?

don't forget CodeBerg

Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)

#9
post #2

The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…

Shouldn't we call it a "network prison" in that case? :)

well it's one where the inmates can leave, but have to come back out of solidarity to the other prisoners :-)

Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)

#10
post #6
post #2

The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…

Why wouldn't this possible on, say, GitLab or Bitbucket?

All of my new stuff is on GitLab. I have seen zero interest in any of my projects, even the ones that were carried over from Github (which are archived). It could just be that I am a dull coder, but I'm leaning more on the notion that discovery is hard in GitLab.
Post reply on HN