4 ms·
Any thoughts on why they wouldn't have released this under a Github repo?
by hanniabu 10y ago
Any thoughts on why they wouldn't have released this under a Github repo?
- milcron 10y agoInertia, probably. You can find older releases at that URL too: https://opensource.apple.com/release/os-x-1010.html https://opensource.apple.com/release/os-x-1010.html
- duskwuff 10y agoAll the way back to 10.0, which was released in 2001 -- long before Git was even a thing, let alone Github.
- wahern 10y agoThey've been publishing their source code using their own portal since before GitHub existed.
- userbinator 10y agoPersonally, I'm not a fan of centralising all open-source software on GitHub and think it's good that Apple host it themselves. Of course, being open-source, you're more than welcome to put a copy there.
- deleted 10y ago[deleted]
- peterkelly 10y agoBecause not all open source software has to be distributed via GitHub. Think about what happened to SourceForge, and be glad that the Internet hasn't become totally centralised around a few major websites yet.
- threeseed 10y agoSeriously the over reliance on Github is a systemic risk to the industry.
- flukus 10y agoIs it? Every repo contains the complete history, github crashing tomorrow would be more of an inconvenience than a disaster.
- yarrel 10y agoIt doesn't contain the bug tracking, the wiki or the project sites. It doesn't include the team organization and access control. It doesn't include the bot integration. And it doesn't include the merging workflow that people are really starting to rely on. GitHub going down would be a major inconvenience.
- flukus 10y agoProject sites are already github repos. Bug tracking etc should be backed up (https://backhub.co/ https://backhub.co/), or did we forget how to make backups?
- simonh 10y agoI get really annoyed by comments like this. The comments was that there may be a systemic risk. Pointing out that there are mitigating controls available is simply not sufficient to refute the concern. To refute it you'd need to show that enough repos do have sufficient backups and are capable of recovering adequately from the loss of github. If I asked a colleague at work if a project was properly backed up and they said 'well there's an enterprise backup solution that is appropriate for it', I'd metaphorically kick their but into next week. I'd want to know that they are actually backing it up and that the backups have been verified, not that they could be backing it up. If you'd said something like 'there are options available to mitigate the loss of github and projects should be taking advantage of them, and here they are' that would be a good and useful comment, but I don't think a practical concern can be reasonably dismissed with a theoretical counter. I find it dismissive and lazy.
- flukus 10y ago
- temp2016 10y agoSomeone made an unoffical github repo, but it's not been kept up-to-date: https://github.com/unofficial-opensource-apple https://github.com/unofficial-opensource-apple The tool they used to create it is here: https://github.com/n-b/tatin https://github.com/n-b/tatin Not sure if it still works, but it's was pretty handy for doing diffs, etc...