Re:A ZFS developer’s analysis of Apple’s new APFS file system
by desdiv on Sunday June 26, 2016 @10:29PM
(#11983870)
>why is it bad first to analyze what already exists and to evaluate good / bad sides of that?
It's a legal defense strategy.
ZFS is covered by multiple patents.
If someone who have never read about any of ZFS's designs and patents independently reproduces one of ZFS's patented features, then the courts could rule that that was non-infringement.
That's why the author said of Giampaolo: "...but didn't delve too deeply for fear, he said, of tainting himself". Reading too much about a patented product effectively taints yourself from being able to freely create your own designs.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by shmerl on Monday June 27, 2016 @12:02AM
(#11984154)
So you think it's Apple's paranoia? They should blame themselves for contributing to this sick patent climate.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by prutschman on Sunday June 26, 2016 @11:14PM
(#11984007)
Independent reinvention is not in general a defense to a claim of patent infringement. Is there some fairly specific set of circumstances you're referring to here?
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by antod on Monday June 27, 2016 @05:05AM
(#11984966)
No, but it helps you to avoid the potential treble damages bit for wilful infringement.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by cm3 on Monday June 27, 2016 @05:24AM
(#11985010)
I understand what you're saying, but I also find it funny that Apple would try to avoid patents. If you're saying that Apple is happy to patent stuff but not so much when it comes to using patents by others, maybe you're right. I wish filesystems were more like media codecs in that Apple had no choice but to support an industry standard.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by cm3 on Sunday June 26, 2016 @05:54PM
(#11982954)
I don't believe Dominic and the team were in NIH-mode. There are most likely other factors which due to Apple's secrecy, and this not being a public project like Linux or Firefox, we may or may not learn. Though, with the information we have right now, it's easy to come to your conclusion.
I'm not sure I quite understand this approach. It's sounds like a pure NIH kind of method (which is admittedly common for Apple). I.e. of course one can always try to reinvent the wheel, but why is it bad first to analyze what already exists and to evaluate good / bad sides of that? Or his approach is simply always to make everything from scratch and not to look at anything else?