Live data from Hacker News

SDL Moves to GitHub

discourse.libsdl.org

231–240 of 270 posts

Re: SDL Moves to GitHub

#231
post #207

Earlier quoted context omitted.

What world? ChromeOS and Android? POSIX APIs are not exposed to app developers. Cloud? Language runtimes and serveless make POSIX irrelevant. IoT? Linux is largely irrelevant in the world of real time OSes and bare metal language runtimes. Desktop? How is that 1% going?

> ChromeOS and Android? POSIX APIs are not exposed to app developers. Cloud? Language runtimes and serveless make POSIX irrelevant. The underlying POSIX filesystem is still exposed to android developers via java's File. And via the C apis too, from the sounds of things. I think its the same on iOS. But even if you're only using posix calls indirectly through complicated database abstractions and unix sockets, you're…

I disagree with everything you said because your tone is just wrong. Old APIs don't remove the need for new ones. New APIs don't remove the need for old ones. The existence of one API does not prevent the existence of another API. Phrasing this as an us vs them problem will just waste your time and fail to convince everyone else. Instead of telling everyone how wrong they are you should convince them how great the new thing is.

Re: SDL Moves to GitHub

#232
post #89

Earlier quoted context omitted.

I think what was meant is that at least parts of GitLab are FOSS and can be installed locally which in not the case with github.

But installable locally kinda defeats the whole point of this move? And as someone who manages a small gitlab instance, it's not always set it and forget it unfortunately.

No, it doesn't because Gitlab.com exists. Installability is an insurance policy.

Re: SDL Moves to GitHub

#233
post #166
post #137

Earlier quoted context omitted.

Exactly. You have new solutions like GitLab, Gitea and Docker which can automate this stuff for you and it is yours and you own everything. Didn't stop RedoxOS, wireguard and GNOME from self-hosting.

The point is that they didn't want to deal with self-hosting anymore. I think he makes some valid points in the article re: owning all of your own infrastructure - there is something to be said for that. But it is so much more than just Git hosting. > "It’s not just Bugzilla. It’s the wiki, the mailing lists, the quaint little Mercurial web interface. The little open source thing that we rely on but no one is working…

I don't see GNOME (GitLab), FreeBSD, Blender (Phabricator) or even wireguard complaining about their issue tracking management here. I have seen many examples of FOSS/FLOSS devs choosing a self-hosted solution over GitHub.

For example, ReactOS's source is hosted on both GitHub and they have a self-hosted backup which they control in case GitHub goes down. If this was SDL being GitHub, so far they don't have a backup plan. Pull requests, issues and their GitHub actions will not work and they would need to wait for GitHub to restore their services or do 'anything'.

I prefer 'Owning all of your own infrastructure' or even being on GitHub and having a self-hosted backup of your own infrastructure just in case GitHub goes down. But moving everything and being 'all in on GitHub' is the ridiculous quest to centralize everything on a platform you don't own because everyone else is doing it.

Re: SDL Moves to GitHub

#234
post #93

Earlier quoted context omitted.

Actually LLVM has their official repository there, not a mirror as GCC[0]. But they still do reviews and merges outside of github. linux kernel project does a similar thing. [0] https://github.com/llvm/llvm-project

The "linux kernel project" does not have its official tree on github, Linus just has a read-only mirror there. You can confirm this by reading one of the bot replies to a PR [0]: Linux kernel development happens on mailing lists, rather than on GitHub - this GitHub repository is a read-only mirror that isn't used for accepting contributions. So that your change can become part of Linux, please email it to us as a pat…

I know that the discussions and reviews happen on mailing lists and believed that this github repo is the official one there all these patches go, but apparently it's not.

Thanks for the correction.

Re: SDL Moves to GitHub

#235

This sounds like an indictment of git. It was supposed to make it easier for OSS developers to collaborate, but it turns out that you become bound to a monopoly like Microsoft. Why can't git users develop an easy to maintain server, like svn and fossil did, for example?

There are great "easy to maintain" servers like Gitea. I run it myself to mirror some things that I would not want to lose.

But self hosted Gitea and other alternatives won't scale easily (and would not be cheap). The biggest attraction to Github for me is the user base and scale, not the UI/UX.

Re: SDL Moves to GitHub

#236
post #12
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?

Seems to be popular at Facebook.[1] Where I work Mercurial has been an option for some time now (no Git unfortunately) and coming from Git I must say I really love how it does some of its things: - hg split: split a commit into as many different commits as you like using an interactive patch editor (you can fold/collapse hunks, can edit them textually, can select which lines of the hunk should be applied). It will au…

I'm sure they use a custom version of mercurial and still probably use git as well. But that's really interesting, never knew about this. Like another other commenter mentioned I also use magit in interactive mode but I'm going to give mercurial a try now.

Re: SDL Moves to GitHub

#237

It seems to me people don't give enough thought to the possibility of hosting themselves elsewhere, and only "mirroring" onto GitHub for the presence effect. GCC does this (edit: LLVM half-does-it, in that issues are handled elsewhere). So does MonetDB and I'm sure there are a million more examples.

This doesn’t solve the issues of stuff like Bugzilla, plus these mirror only offer a fraction of what GitHub truly offers (issues, CI, pull requests with nice interface). Basically, if you think your home grown infra sucks, a GitHub mirror doesn’t address that.

Neither does hosting your code on GitHub. Its issues mechanism is very limited compared to Bugzilla (or JIRA or whatnot). As for CI - GitHub itself doesn't give you CI. Travis does and they've gone mostly/wholly commercial. etc.

I'm just saying you don't need to be fully on GitHub to be visible on GitHub.

Re: SDL Moves to GitHub

#238
post #228

Earlier quoted context omitted.

That's it. Back in the day that's what was great about source forge. Now it's github. Many people already have an account there so you significantly lower the bar for people to get involved with patches, bug reports etc. If a project has self hosted infra and wants me to sign up to their Bugzilla I think twice before doing so. And if github really turns to shit because Microsoft shows their true evil face you can jus…

Check out https://gitlab.kitware.com/users/sign_in or https://gitlab.xiph.org/users/sign_in You can sign up with your GitHub account.

https://gitlab.gnome.org/users/sign_in even allows you to login with a GitLab account. Which ironically isn't possible on these other two.

Re: SDL Moves to GitHub

#239
post #192

Earlier quoted context omitted.

It has a money in the bank at the end of the month, regardless of the UI/UX.

It might? It might also not have money in the bank? Is that relevant? Bad UX is subjective. Money doesn't change that.

Bad UX (for some definition of bad) may be subjective, but that doesn't mean money won't affect it.

Suppose we want to optimize user productivity. For any given UX, some users will feel they're more productive with it, and some less. Finding a UX that maximizes the number of users who feel productive is going to help attract users to the product, and money can buy the design expertise needed to find that UX.

It might be the case that users only feel more productive with a given UX and aren't actually more productive with it. Even then, if a majority of potential users think that the UX is making it easier to accomplish their goals, a project will have an easier time attracting users.

Re: SDL Moves to GitHub

#240
post #223

Earlier quoted context omitted.

> Even Linux will eventually be replaced by something else, when all the kernel engineers that helped its adoption are gone. I disagree. Linux has reached critical mass, the biggest tech giants depend on it heavily and are the main contributors. If some new fancy subsystem, interface or syscall would benefit Google's workload, they will implement it and it gets merged since even of Google will be the only one using i…

Yes I am talking decades and specifically about Linux, naturally other OSes will eventually share similar fate. Check Android and maker distributions for how much gets merged upstream. The only guarantee of the future is that it is unpredictable.

> The only guarantee of the future is that it is unpredictable.

Yet here you are making predictions...

I doubt Linux will fade away until there is some major paradigm change away from Van Neumann architecture. It has survived and become dominant over 30 years by constantly adapting and innovating.

Post reply on HN