Live data from Hacker News

Apple is patenting Swift features

forums.swift.org

101–110 of 223 posts

Re: Apple is patenting Swift features

#101
Chris Lattner has commented on the OP:

-----

Disclaimer: I'm not an apple employee and not am not lawyer, this is just my understanding of the situation having spent lots of time talking to lawyers and other experts about this:

I agree with much of the sentiment that software patents are often silly and the system is broken in many ways. This patent is a reasonable example of that (patenting syntactic sugar for monads, really?). I have no idea if there is prior art, but I wouldn't be surprised. For sake of discussion, lets assume the patent is valid.

Even if I and others don't like it, the software patent system exists. As is pointed out upthread, one of the major reasons that Swift uses the Apache 2 license is to provide more certainty for the community w.r.t. licensing and patents. An additional bonus of the Apache 2 license is that the open source project as a whole benefits from companies having and contributing their patents under the terms of the license: to say more directly, it is good for the Swift project that Apple has this patent and has contributed it to the project.

The reason for this is the Apache patent revocation clause 1, the end of bullet 3:

>If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

This basically says that if someone sues someone else over Swift then they lose access to the patents contributed to the project, and are therefore subject to countersuits. This is a significant part of the protection that the Apache license provides (it is a big deterent to lawsuits in general) but it only has teeth if there are actually patents in play!

The LLVM.org community is actively working on a multi-year relicensing effort specifically to achieve these sorts of projects for LLVM as well.

-Chris

-----

Am I misreading this to mean that if Apple sues someone for infringement over the patents they have been granted, they immediately lose those patents?

Re: Apple is patenting Swift features

#103
post #74

Classic Apple hoarding software patents. Even if they don't use them, this looks like a threat move. Patenting programming language features is just sick. Questions in that thread: > 1. If a separate open-source programming language under Apache 2.0 license implements an optional chaining feature, would it be a violation of the patent then? > 2. What if there's a separate implementation of a Swift compiler developed…

They have not patented any programming language features.

They have patented one or more ways to implement some programming language features.

Read the claims, that is what is protected. Do one step differently and you are golden.

Re: Apple is patenting Swift features

#104

This feature wasn’t even invented in Swift, the fact that a patent was granted on it shows the sorry state of technical policy making

Good thing this patent does not protect any programming language features.

(It protects how Apple implemented some features)

Re: Apple is patenting Swift features

#105

Chris Lattner has commented on the OP: ----- Disclaimer: I'm not an apple employee and not am not lawyer, this is just my understanding of the situation having spent lots of time talking to lawyers and other experts about this: I agree with much of the sentiment that software patents are often silly and the system is broken in many ways. This patent is a reasonable example of that (patenting syntactic sugar for monad…

> >If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

> Am I misreading this to mean that if Apple sues someone for infringement over the patents they have been granted, they immediately lose those patents?

You in this case is likely a defined term with a narrow meaning and likely does not refer to Apple (which is probably referred to as We, Us, "the company", etc) in the document.

Re: Apple is patenting Swift features

#106

Chris Lattner has commented on the OP: ----- Disclaimer: I'm not an apple employee and not am not lawyer, this is just my understanding of the situation having spent lots of time talking to lawyers and other experts about this: I agree with much of the sentiment that software patents are often silly and the system is broken in many ways. This patent is a reasonable example of that (patenting syntactic sugar for monad…

The biggest question here is whether this means they lose the patents when they sue something that's not covered by Derivative Works as defined in Apache 2.0?

Looks like an implementation of a compiler not from Apple (that is, not a fork, or one that diverged too much from the original) or different languages that overlap with the patent would be infringing even if they used Apache 2.0 as well.

Re: Apple is patenting Swift features

#107
post #92
post #73

Earlier quoted context omitted.

IANAL, but those claims seem to describe .Net (multiple languages targeting a common IR?), so there's prior art.

p-code?

The key "innovation" that Apple seems to be claiming is that multiple languages are intended to be compiled down to a single p-code (in this case, LLVM). .Net does this in two ways:

* Projects in different languages (originally, C#, VB and curiously Eiffel) compile to the same p-code/IR and are dynamically linked into an application.

* A single project contains multiple languages (C#, ASPX, Razor) compile to the same p-code/IR and are statically linked into an application.

.Net may not be the first that did this intentionally, but it does cover all the scenarios.

Re: Apple is patenting Swift features

#108

Earlier quoted context omitted.

Can't you make a pretty similar argument about all types of patents?

it wouldn't be quite the same because software does not have physical material properties. IMO this difference is crucial.

So-called software patents are always drafted as machines that can perform the claimed actions. These machines are comprised of one or more hardware components, including some hardware components that can execute machine readable instructions.

(There really is no such thing as a software patent.)

Re: Apple is patenting Swift features

#109
post #105

Chris Lattner has commented on the OP: ----- Disclaimer: I'm not an apple employee and not am not lawyer, this is just my understanding of the situation having spent lots of time talking to lawyers and other experts about this: I agree with much of the sentiment that software patents are often silly and the system is broken in many ways. This patent is a reasonable example of that (patenting syntactic sugar for monad…

> >If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. > Am I misreading this to mean that if Apple sues so…

Right, also it's for "any patent licenses granted to You under this License" - if Apple owns the patent, they have no need for Swift's license to grant them a patent license. They own it. (They are not being licensed the patents by the government, and they're certainly not being licensed them under the terms of Swift's license.)

Re: Apple is patenting Swift features

#110
post #5

Earlier quoted context omitted.

Thats not the only thing, no? Doesn't it also prevent e.g. other people/company from including that feature in their own programming language that doesn't use Swift at all?

Someone could even implement the feature in a dynamic language like Python or Lisp for a particular application. Does that mean the application is infringing the patent because they didn't use Swift?

no.
Post reply on HN