I came away with the exact same takeaway. If you really want to convince people that content moderation is a hard problem, just ask them to listen to this Radiolab episode about Facebook's struggle: https://radiolab.org/podcast/post-no-evil
I encourage anyone who thinks the Supreme Court is composed of 9 wordcel idiots who can't possibly understand anything about computers to read their opinion in Google v. Oracle [1]. It's very readable and well-argued. It's like a reverse Gell-Mann amnesia—clearly the author of the draft understands the issues at play quite well.
Google v. Oracle is one of the most anticlimactic decisions I've read.
The decision does show that the Supreme Court justices are savvy as to how the tech industry works, at least they know from a policy perspective they can't strike down the whole Android ecosystem without causing mayhem. And they know they can't affirm copyrights of APIs for similar reasons.
But from a legal perspective the way they outright dodged the legal question they were supposed to answer (i.e. are APIs copyrightable?) and the way they just asserted the conclusion about fair use without pretending to apply legal reasoning (together with a disclaimer that they haven't tried to change the existing law even if it looks like they have), I wouldn't say it's one of their better decisions.
As you say, in general people in tech have a tendency to assume judges are idiots. Most often they aren't, because judges sitting in the top courts are a handful of people at the pinnacle of their field, and they don't get there by being idiots. I agree with you that it's a good idea to sample some opinions from Supreme Courts or perhaps even others appeal courts to gain an appreciation of how judges tend to think. I just think Google v. Oracle is one of the worse ones to start with..
To your point w/r/t Google v Oracle, the justices aren't being useful idiots, but instead, useless geniuses. Hopefully they do something of value with Warhol and the Alice cases coming up.
Their JetBrains plugin is written in Kotlin / Java but it spins up a agent server written in node.js which handles the business logic (building the prompt, caching, making completion requests to their API). I assume most of the code is shared between the VSCode extension and this javascript agent.
If you start the function you're trying to write (just by writing `def` on a new line), you should usually be able to get it to start implementing it.
You can see alternate suggestions on VSCode by hitting Option + [. We don't currently support seeing alternate suggestions on JetBrains IDEs, but we're working on it!
It's much more convincing.