Junie tooling excels when you are more involved. Like, look in these two files, add this specific functionality, in this specific way. Junie is usually a lot faster and to the point. Very simple tooling , it just works for this workflow. But it breaks for the “code the whole thing for me” workflow.
I don't think they ever going to be able to re-claim large chunk of developers who are now fine with thin VSCode-like + Terminal for non-JVM languages.
Perfect example of how large corp with research capacity failed to navigate their product changes.
I haven't tried out Junie yet, but the concept seems pretty compelling to me. I want a good IDE for the language I'm using, and I'd like an AI that's well integrated and trained on delegating to it for algorithmic/deterministic transforms (e.g. IDE-driven refactorings).