101–110 of 170 posts
That title is clickbaity.
I suggest editing the title to the following: "Open Source Components of macOS 10.12"
Earlier quoted context omitted.
Either they don't want to release it or they can't (a third-party contract/NDA), at least right now. Open sourcing is often seen by big-businesses as potentially "helping" competitors undermine, replicate, sue, make interoperable wares which may threaten the "Golden Goose." It sucks, but that's the situation... lawyers can't force them to release other code unless they're caught TiVoizing some GPL 3 code or something…
I can't believe this is a serious comment. The majority of open source is crap, like 80% of it. People build what they need and forget about it. Often the code has no cohesion to the rest of the project and often it is of poor quality. Not to mention the ego's and lack of sociability of most projects. Apple didn't become the most valuable company by following that principle. Instead it took the approach of an egotist…
You might be interested in fact, that even Model S runs on Linux kernel ;)
Earlier quoted context omitted.
Leaked source code is not open source dude. Open source is software licensed under terms compatible with these rules: https://opensource.org/osd
Both the Windows Server 2003 x86 and the Windows XP amd64 kernel source code have been available for academic purposes. They are governed under the WRT License, which forbids re-distribution outside of the academic use. But yes, MS provided that source code with full documentation on how to build and debug each kernel. I've built the WinXP kernel a few months ago just for nostalgic purposes, here's a VM running the c…
This isn't just pedantry, we are scientists from different countries, with many of us having learned English as a second or third language (I'm from Romania, hi), so it's better to be precise in language.
And in this instance "open source" is a good term to be precise about, because the OSI definition specifies exactly what you can and cannot do with it. And in particular (1) you can use it for any purpose, even for evil ones and (2) you can fork it and modify it in any way you wish.
So when I hear "open source", I don't have to go and read the license and validate that these requirements are true, because OSI has already done that for me and they have lawyers that know how to read licenses. This saves me time, headaches and money.
And academic, non-commercial licenses do not qualify. Microsoft itself has introduced an alternative term for such academic, non-commercial licenses and I think it's a good one: Shared Source. Lets use it.
Earlier quoted context omitted.
...just like over reliance on google.com to search internet? some people say "yes", some people say "nonsense".
Who relies on google exactly, other than advertisers? It works really well, but, if it fails... there's plenty waiting right there to take it's place.
So, without further ado:
- obviously, services like Search, Youtube, Gmail are unavailable. That includes searching from the address bar in your browser ;)
- people, who have their DNS set to 8.8.8.8 should reconsider their settings,
- too many web pages use assets hosted on Google CDN, including analytics or fonts, and when unavailable, the pages will load very slowly, waiting for timeouts from CDN.
- Android phones will say, that Internet is unavailable, even if it is.
Otherwise, everything is fine.
Earlier quoted context omitted.
It 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.
Project sites are already github repos. Bug tracking etc should be backed up ( https://backhub.co/ ), or did we forget how to make backups?
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.
Heh, I went spelunking through the bsd/mach layers of the code, was quite a bit of fun. Looks like they've only released the x86_64 and x86 versions of the code? I don't see any ARM in there. Anyways, found gems like this [1]: /* * File: sched_prim.c * Author: Avadis Tevanian, Jr. * Date: 1986 * * Scheduling primitives * */ I hope to leave a legacy like this someday, hopefully someone will appreciate the author's com…
Here are some hints of what they are doing to process the original sources:
https://opensource.apple.com/source/hfs/hfs-366.1.1/make_ope...
Earlier quoted context omitted.
I can't believe this is a serious comment. The majority of open source is crap, like 80% of it. People build what they need and forget about it. Often the code has no cohesion to the rest of the project and often it is of poor quality. Not to mention the ego's and lack of sociability of most projects. Apple didn't become the most valuable company by following that principle. Instead it took the approach of an egotist…
> Furthermore, I'd challenge you to name one open source project that can be shipped AS-IS as a product. Don't even say the Linux kernel, that has like what 2% market share? GitLab. Postgres. Atom. Docker (debatable). I could go on, but to be fair I am a bit of a hoarder of interesting oss. Re the Linux kernel: isn't it way higher than 2% if you count commercial and industrial usage? Also Android devices.
Earlier quoted context omitted.
'macOS' is just too much of an affectation to ask for in styling capitalization. You'll notice a lot of people resisting it, defiantly writing 'MacOS'.
Not really. "iOS" is standard and no resistance has been noted.