Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Another proprietary filesystem? I was really hoping they'd adopt ZFS fully.


ZFS on OSX was doomed the moment Oracle bought Sun.

If you want to know why, just contemplate the smoking wreckage of the Oracle/Google Java API lawsuit.


ZFS is on a completely open source license.

Oracle's beef with Google comes from actions that occurred before Java was open sourced.

It's hard to see how the two scenarios are even remotely related, other than "Oracle"


Gruber, who usually has good inside sources, on Apple dropping ZFS[1]:

> Word on the street in Cupertino is that dropping ZFS wasn’t an engineering decision, but a legal one, and it might have had something to do with Oracle’s acquisition of Sun. I don’t know if it was a problem with the terms of the CDDL license, general distrust/dislike for Oracle, or what — only that the word came down from legal that ZFS was a no-go.

Apple has a notoriously paranoid pack of legal sharks, and they clearly felt uncomfortable with something about the ZFS legal situation.

[1]: http://daringfireball.net/linked/2009/10/23/zfs


The unofficial word is that Apple wanted Sun to sign an indemnification agreement, Sun had agreed to sign it on the day that Oracle's acquisition of them closed and Oracle refused to sign it.


"ZFS is on a completely open source license." This is an ... interesting viewpoint

Oracle's viewpoint on what patents are and are not granted by that license is also interesting (as was Sun's).

Interesting enough that Apple felt they needed to go get a patent license for it, and couldn't come to terms.

http://arstechnica.com/apple/2009/10/apple-abandons-zfs-on-m...

You are correct this happened pre-oracle, but note that it was confirmed by Sun's spokeperson.

(Also note that the national labs, who have been continuing ZFS on linux, are immune to a lot of these issues. Oracle literally cannot get an injunction against them on patent infringement issues, so they are guaranteed they can always work on it)


A large part of Oracle's case was based on alleging a Google developer had "copied" code that he himself had contributed to Java.

I have to say it's made me a lot iffier on contributing to open source projects, or at least those owned by for-profit companies.


Open-source is great, but if that source is covered by patents you're potentially liable for damages. Nobody would ever willingly expose themselves to that.


When Apple dropped ZFS, Sun was in the middle of a lawsuit with NetApp regarding ZFS. If I recall correctly, Apple wanted Sun to be on the hook in the event of any possible patents, but they balked. Apple isn't going to touch ZFS.


Steve Jobs and Larry Ellison were best buddies. The dream died the year after.


Apple says they intend to open-source the file system in the docs.

Open Source: "An open source implementation is not available at this time. Apple plans to document and publish the APFS volume format when Apple File System is released in 2017."


It says they plan to document and publish the volume format but nothing about the source code of the implementation. It being "not available at this time" doesn't necessarily imply that it will be available in the future.


I'd imagine the implementation will show up in the next appropriate XNU kernel release.


Neither the format nor implementation of Core Storage is documented by Apple. Near as I can tell not even an fs magic number is documented, i.e an offset and a signature that makes it possible to identify Core Storage physical volumes.


Just like they promised to open source FaceTime and iMessages? Apple has a history of making false promises in regards to open sourcing products.


My understanding was that FaceTime and iMessage weren't open sourced because of issues related to a patent troll (VirnetX IIRC). I'd be interested in hearing from others that are more familiar with the situation.


Or perhaps concern with having to deal with 3rd party iMessage/Facetime clients while at the same time trying to maintain a high level of security. Apple doesn’t want anything to tarnish the security reputation of these products.


Not only that, but apparently Steve Jobs decided to just say that on stage and while it had been discussed a bit it wasn't the plan and came as a total shock to the people involved.


> FaceTime

They got sued heavily for it. They had to completely change the implementation and it became a non-P2P video chat.


I don't recall any promises around iMessage, and FaceTime fell victim to patents.


> Apple has a history of making false promises in regards to open sourcing products

No, not true at all. iMessage was never promised, mentioned, or even hinted at being open source. Also, on the FaceTime from they said that the underlying protocols would be submitted to standards bodies as an open standard - that's a completely different things from open source. And the reasons that Apple didn't wind up doing that are well known (lawsuit from patent trolls).

Sounds like you have an axe to grind or only listen to people who do...


Not sure why you're being downvoted.

Too many fanboys I guess. I would hope the community is more enlightened than that.


Because it's just kind of lazy and incorrect, that's why.

Apple did promise to open FaceTime, and was promptly sued – that's why it's not open. AFAIK there was no promise to open iMessage.


My apologies for the unwarranted cynicism, I was not aware.


Source of the quote is this page:

https://developer.apple.com/library/prerelease/content/docum...

Releasing a new filesystem is already surprising. And they plan to open-source it. Huh.


Would it be wishful thinking to hope Microsoft would follow suit by open sourcing ReFS?


Free software and patent-free or whatever some lawyers call "open"?


They said "publish the APFS volume format". So that can mean just documentation and not code at all.


Published code doesn't mean 'open' either. You need rights to the code, not merely access to it.


That's awesome.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: