[Kranar]

>The next time someone sues Apple for this, there will be precedent.

Trial courts don't set precedent, only an appellate court or higher can set a precedent, and that precedent is only binding on lower courts.

Since trial courts are the lowest courts, their decisions are not binding on any future trial and as a general matter do not set any kind of precedent.

[granzymes]

Appellate courts set binding precedent, but district courts routinely look to eachother for guidance on how to rule on questions where there is no circuit/SCOTUS ruling.

Similarly, a judge in one circuit may look to the decision of a different circuit court when their own circuit has yet to rule on an issue, even though a different circuit’s opinion does not bind them.

In this case, however, the issue was ultimately put before a jury which doesn’t produce the kind of written decision that other judges would look to when deciding similar cases.

[clnq]

Ah, thanks for the additional knowledge. I’ll edit my comment for clarification.

Epic Games v Google is going to appellate now, though, isn’t it?

[troad]

It's kind of wild to see someone confidently posting legal analysis while obviously lacking an understanding of - uh - precedent.

[clnq]

I clearly stated “I’m not an expert on this” and publicly corrected my mistake to not mislead readers.

Don’t fulminate, my brother, see comment guidelines on HN for more info. There’s need to act like this and your comment doesn’t contribute anything to the discussion.

[troad]

> There’s need to act like this and your comment doesn’t contribute anything to the discussion.

Does yours?

I mean that in earnest, not as a dig. You're posting legal analysis without even rudimentary legal knowledge, and I think that's worth noting and responding to.

It's also worth noting you only admitted you were not an expert once your initial post was debunked, and that in your corrigendum you manage somehow to add many additional substantive legal claims. Without any apparent additional legal knowledge.

If you did the same on a programming topic, there'd be an army of people ready to downvote you, because most of the wonderful folks here on HN are versed in programming, and could easily see through that. But this doesn't hold true for law, and you're in a position to mislead. Noting that contributes to the discussion by helping a reader discriminate signal from noise.

[clnq]

> It's also worth noting you only admitted you were not an expert once your initial post was debunked

No, that was in the original comment. I added only the paragraph prefixed with EDIT.

My friend, you are just picking a fight on the internet. You don’t actually know what the comment was and yet you say you do. Please do not.

Alternatively, please tell me how my comment is misleading now, if there truly exists an argument in your comment beyond an ad hominem. That would be more useful.

[troad]

With respect, you seem to be the one struggling to let this one go. In two short comments you've accused me of: fulminating, not being constructive, posting against site rules, picking fights on the internet, posting ad hominem attacks, etc. All I've noted is that you're not legally trained, which you yourself admit.

My respectful advice is that if you're not legally trained, but wish to write legal analysis, (1) pause and consider how useful this actually is to others, and (2) if you must continue, preface (!) your statement with a disclaimer that you're not legally trained.

Lawyers are trained that with knowledge comes responsibility - people tend to rely on what lawyers say, often in unanticipated ways. Not only does this often lead people to go off half-cocked, but it can have legal consequences for the person giving the advice (there's such a thing as negligent advice). Generally these laws apply equally to lawyers and non-lawyers, and simply because you don't have any legal training doesn't mean you're not giving 'legal advice', it just makes your advice all the more dangerous. It seems reasonably unlikely you'd be sued for negligent advice for random comments online (not impossible!), but you should reflect on the ethics of confidently leading people on, from a position of relative legal ignorance.

I realise you may not be receptive to what I am saying to you - you appear to have become somewhat defensive and might be perceiving my words as further attacks - but I'm genuinely not here to diss you, and I'm absolutely not looking for a fight. Perhaps my initial comment was a little glib, but not knowing what precedent is and giving legal advice is rather like not knowing what a variable is but nonetheless giving confident programming advice. Generally best avoided.