I've not used Copilot but I've experimented with two other AI driven autocompletion engines in Java and Kotlin. In both cases I uninstalled the plugins due to a combination of two problems:

1. The AI suggestions were often less helpful than the type driven IDE autocompletions (using IntelliJ).

2. The AI plugins were very aggressive in pushing their completions to the top of the suggestions list, even when they were strictly less helpful than the defaults.

The result was it actually slowed me down.

Looking at the marketing materials for these services, they're often focused on dynamic languages like Python or JavaScript where there's far less information available for the IDE to help you with. If you've picked your language partly due to the excellent IDE support, it's probably harder for the AI to compete with hand-written logic and type system information.

I'd recommend TabNine, it is extremely helpful. I tried Kite once, and it is WAY overrated. So slow that by the time it provided me suggestions I was only a few characters away from finishing. Tabnine has saved me hours.

Or the converse?

If Copilot is as good as it gets but only for some languages, won’t it influence what languages will be chosen by devs or companies?

Indeed, I could imagine it becoming more difficult to adopt a language that doesn't already have a large corpus to train on.

Could there be a boom followed by a bust? Sometimes a greedy algorithm looks good until it doesn't. It's at least imaginable that AI coding helps you do stuff locally that eventually ties you in knots globally, because you were able to rush in without thinking things through.

(It's also conceivable I'm put out of a job, but I'm not worried yet. So far I can only imagine AI automates away the boring part, and I super-duper-want that.)

I really wonder sometimes if Java would never have made it that far if it wasn’t for eclipse and later IntelliJ.

Well, there are few things many programmers enjoy better than automating away repetitive tasks. If not exactly intellij or eclipse, something that achieved the same end would certainly have arisen.

I'm sure there's at least a few relevant XKCD strips to insert here.

Would be an interesting fact so see companies adopt languages that need significantly more code to reach the same result just because some AI can automate a lot.

Thinking about generating 10 times the code you need, just because you can generate it instead of writing (perfomant?) code.

This is a good point and it will be interesting to see if something like copilot will get developers/companies to adopt a language that is better supported by AI.

Edit: You are honestly downvoting me for saying something that might actually happen. If copilot lives up to the hype, but for a limited number of languages, this can have a profound affect on what languages people might decide to use in the future.

Boilerplate is the most annoying type of code to write/try to remember, having all of that automated away would be awesome.

This approach is kind of a hack, though. The proper way to automate boilerplate is better PL/library design that makes it unnecessary.

Wait until it's time to maintain all this autogenerated code. It's going to be a nightmare.

Don't worry, the most common bug fixes will become part of the suggested code, so when you start writing patches, Copilot will have great suggestions. And then when you have to fix the new bugs, same deal.

The real nightmares will revolve around changing requirements. That's where a statistical analyzer is not going to be smart enough to know what's going on, and you're going to have to understand all this autogenerated code yourself.