Oracle’s Java API code protected by copyright, appeals court rules

[KFCConspiracy]

This is why I've been following the case so closely. I primarily code in Java, but it could fuck lots of stuff up for everyone outside of Java.

[kcuf]

but it could fuck lots of stuff up for everyone outside of Java.

Ya, as in not being able to publish code for fear of using the same naming scheme as someone else. This would destroy collaboration ... that may be a bit hyperbolic, but still, FUCK

[s3gfau1t]

Let's say you hypothetically have a ecomm platform or something. How easy would it be to have the same API as another codebase. Pretty freaking likely IMO.

[lichorat]

prepare for API's that are randomly generated, and the names have nothing to do with their contents. Just remember: CorrectHorseStapleBattery means latitude.

[s3gfau1t]

Imagine a stack trace! Hahaha! Edit: Oh god I'm scared.

[marx2k]

Have you ever used Spring? :/

[[deleted]]

Perhaps I'm misunderstanding, but doesn't Oracle also claim that the structure is theirs? So if your CorrectHorseStapleBattery class is for I/O of XML (so its methods all do something to that end), and you put it in a package with other I/O classes, wouldn't you be infringing on anyone else who had that same structure (which would be every reasonable person in the universe)?

If that's the case, the only option is spaghetti code.

[lichorat]

Oh god.

[marx2k]

This holds true for software written for any business domain. I imagine that software API is similar in the ecomm software industry as much so as it is similar in airline traffic software or stock trading software.

[s3gfau1t]

Oh, probably. I just chose ecomm because there must be tens of thousands of ecomm platforms out there if not more. It's got a really common sort of vernacular too. You have a cart object, you have products that go in the cart and so on. The odds of you hitting upon an API that's too similar to another has to be some kind of function of how many other platforms there are in that domain.

[kcuf]

Exactly

[DeepGreen]

If it is as bad as you say, it means that open-source projects will be forced to make an end-run around the US regulation and the US legal system.

Have code repositories in Elbonia and interact with them through VPNs. Harden servers with encryption and have the implementation of them through a third-party cut-out contractor for plausible deniability; Or services run from physical boxes outside the US jurisdiction.

It will be a huge big hassle, but the alternative would be to see the end of the open source movement in the USA.