Live data from Hacker News

SDL Moves to GitHub

discourse.libsdl.org

111–120 of 270 posts

Re: SDL Moves to GitHub

#111

"So in moving it to GitHub, we’re finding that a lot of things are just nicer because a large paid staff of engineers is working on it every day. And I grew up during the heydey of the Free Software Foundation, so I know this is a trap, but I’m tired and don’t have the energy to be a server admin for something that’s held together with scotch tape and prayers when I’m really supposed to be writing OpenGL code." This…

>This seems to sum up the biggest pain point that drives people away from OSS. Not knowledge, not skill, not price, but the total experience of a nice piece of software that lets you get the work you actually want to get done... done. This is why I continue to be fascinated by FreeBSD, I don't use it for much but when I do, what I'm trying to do almost always works right out of the box. My point is that is all comes…

I have come to the conclusion that the only reason why things like flatpak and snap exist is because the ergonomics for creating and maintaining .deb packages is so awful.

Re: SDL Moves to GitHub

#112

Earlier quoted context omitted.

>This seems to sum up the biggest pain point that drives people away from OSS. Not knowledge, not skill, not price, but the total experience of a nice piece of software that lets you get the work you actually want to get done... done. This is why I continue to be fascinated by FreeBSD, I don't use it for much but when I do, what I'm trying to do almost always works right out of the box. My point is that is all comes…

I have come to the conclusion that the only reason why things like flatpak and snap exist is because the ergonomics for creating and maintaining .deb packages is so awful.

Pacman FTW

Re: SDL Moves to GitHub

#113

Earlier quoted context omitted.

Wonder why they did not pick GitLab since it is significantly better for FOSS ideals and has the same niceness of GitHub

My guess is the network-effect. If you want more contributions Github is the platform to pick for your project. Good or bad it is the de facto standard platform for OSS projects with a huge pool of potential developers.

I don't think this is it. I think it's more about (1) marketing and discoverability and (2) ease for current maintainers.

Getting new contributors is overrated for OSS unless they are an exceptional contributor (like if a big org were to contribute).

Main incentive is getting more consumers of the project (increase popularity) and making it more convenient for current team.

Re: SDL Moves to GitHub

#114

Earlier quoted context omitted.

>This seems to sum up the biggest pain point that drives people away from OSS. Not knowledge, not skill, not price, but the total experience of a nice piece of software that lets you get the work you actually want to get done... done. This is why I continue to be fascinated by FreeBSD, I don't use it for much but when I do, what I'm trying to do almost always works right out of the box. My point is that is all comes…

I have come to the conclusion that the only reason why things like flatpak and snap exist is because the ergonomics for creating and maintaining .deb packages is so awful.

Not just that. Application sandboxing is important too. The traditional unix approach of any process run by your user can access all your files is at odds with modern security concerns.

Re: SDL Moves to GitHub

#115
post #35

Earlier quoted context omitted.

I mean git is wildly popular because of GitHub, and probably that was something to do with it in the Rails community... a community that if anything is culturally the opposite of the kernel dev community (or at least very different). I don’t think any kernel dev influence had to do with it, even though it’s often stated as a fact.

No, even at the time of GitHub's founding Git was already the clear winner. Think about it, why did GitHub feel safe launching with only Git support, while its competitors (Google Code, Bitbucket, SourceForge) had support for multiple VCSs?

Its competitors didn't have support for multiple VCSes. Sourceforge was CVS only, Google Code did SVN (and maybe CVS?), Bitbucket was hg only _and_ later. Many of these were later forced to add git support (and google code added hg iirc), but tying your source code host to a single version system was the norm when github launched.

Re: SDL Moves to GitHub

#116
post #3

I've never heard of mercurial until this post, I've been using git for version control and it does the job really well. To those who use mercurial over git, why?

Mozilla uses Mercurial for Firefox code because Mercurial had much better Windows support that git (at the time Mozilla was moving off CVS back in ~2007). Some Mozilla developers prefer git and use git plugins (cinnabar) to talk Mozilla's Mercurial servers.

https://hg.mozilla.org/

Re: SDL Moves to GitHub

#117

Earlier quoted context omitted.

Well, to be fair, regardless of what you do, the likelihood that you will get exactly zero contributors is very high. Oh, you'll get complaints, that much is very achievable. But actual contributions? Even simple, bullshit code boot camp homework exercises? Good luck.

Why would someone want to contribute to a bullshit boot camp homework exersize? That seems literally the least likely thing to get any collaborators on. But, sure, if you don't care about making the development tools something that anyone other than you find convenient, than you can of course just pick whatever you find convenient, nobody is going to stop you. That's still not a mailing list with patches for most peo…

I was saying that the few contributions I've ever gotten on any of my projects are basically people completing bullshit codecamp exercises. The contribution is low impact and the contributor never returns. The actual act of submitting the contribution was a larger percentage of the effort than the actual change itself.

Re: SDL Moves to GitHub

#118
post #101
post #55

Earlier quoted context omitted.

Since the Microsoft takeover, the platform is compromised. It seems people have very short memories.

Microsoft is a completely different company than it was even just 5 or 10 years ago. Saying that MS is an enemy of open source is uninformed at best and idiotic at worse. Do me a favor, look at Facebook [1], Apple [2], Amazon [3], Netflix [4] and Google [5]. Now tell me which one has more Open Source repos than MS [6]. I'll give you a hint... none of them. Sure, volume of open source repos may not be the best metric,…

You're factually correct, but you've probably forgotten the "3 Es": "Embrace, Extend, Extinguish" [0]. Microsoft is a business and is therefore about maximizing profits. I'd rather not assume anything, especially not that they are somehow friendly to the OSS movement. Lets give it a few more years before we assume that OSS is something they are gonna do long term. Otherwise, it's like "free" google products; here today, gone tomorrow.

[0]: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

Re: SDL Moves to GitHub

#119

Earlier quoted context omitted.

Well, to be fair, regardless of what you do, the likelihood that you will get exactly zero contributors is very high. Oh, you'll get complaints, that much is very achievable. But actual contributions? Even simple, bullshit code boot camp homework exercises? Good luck.

Why would someone want to contribute to a bullshit boot camp homework exersize? That seems literally the least likely thing to get any collaborators on. But, sure, if you don't care about making the development tools something that anyone other than you find convenient, than you can of course just pick whatever you find convenient, nobody is going to stop you. That's still not a mailing list with patches for most peo…

> Why would someone want to contribute to a bullshit boot camp homework exersize? That seems literally the least likely thing to get any collaborators on.

You've misunderstood, the coding boot camp assigns homework, and sometimes that homework is: "Contribute to an open source project!" This usually takes the form of something like a pull request to "Fix typos in README" or something otherwise insignificant. GP is just saying that however you release your FOSS project, you're unlikely to get even that tiny level of outside contribution, so using "no one will contribute" as an argument against a mailing list isn't very persuasive. The argument that mailing lists suck, perhaps more so, but GP didn't opine on that.

Re: SDL Moves to GitHub

#120

Earlier quoted context omitted.

A much better UI. Git won because of the influence of the Linux kernel developers, that's all.

Git is and always was very fast. Hg used to be much much slower, and still is.

Mercurial beats git in a fair bechmark on a large repository by now. As far as I know, no other DVCS received similar dedicated optimizations.

(Microsoft worked around git by shimming a fake file system driver below the local repository to make it scale enouth to cover the Windows codebase. It's all Windows exclusive and not part of git, so it doesn't really count).

Post reply on HN