1) There's a "No" button in this dialog. It allows you to opt out from detailed data sharing, and you can still use the plugin.
2) In the next plugin update, we'll make it so that the detailed data sharing prompt is shown only in EAP builds of the IDE, and detailed data sharing is never enabled in release builds.
Just to clarify: No one is forcing you to use AI assistance features. All the deeply integrated features start working only after you explicitly log in to JetBrains AI service.
Just to clarify:
1) the AI Assistant plugin is not bundled, it needs to be installed separately;
2) once the plugin is installed, you need to explicitly log in to the AI platform.
Therefore, there's no risk of your code being submitted to a third-party service without you performing several explicit actions to authorize it.
To provide even more control over the use of AI Assistant at the organization level, we're adding support for per-repository opt-out flags in the next update of the AI Assistant plugin.
Actually there's no difference in terms of how sharing code is handled. Both Copilot and AI Assistant send your code to a LLM, and neither of those tools will use your code for training code generation models.
JetBrains IDEs ask you whether you want to submit usage data on the first startup, and honor your choice. You are not watched if you don't give an explicit, opt-in permission for that.
A lot of our work is open-source. You can easily see that our investment into improving our products, visible through the open-source repositories, has been steadily increasing every year.
If it was this easy, we'd have enabled this by default. Unfortunately by far not all UI freezes in IntelliJ IDEA are caused by GC, and ZGC is not a wholesale performance improvement even for those scenarios which do depend on GC.
I'm not in contact with the research team and don't know which practical applications they have in mind, but as far as IntelliJ is concerned, we don't have any current plans to use the results of their work.
What exactly do you mean by "copyright and licensing"? JetBrains products do not violate any copyright or licenses from Oracle, and even if they change the license of future versions of Java, current versions are available for us to use. And Oracle has been investing into two different IDEs, NetBeans and JDeveloper.
You can do isomorphic (server-side and client-side) rendering in Kotlin. For mobile UI, you can build native UIs in Kotlin for Android and for iOS, but the UI code will be different for each platform, built on the native API of the corresponding platform. At this time we have no plans to build a solution for reusing UI code between mobile platforms.
It's a bit different from a regular export/import relationship. An exported declaration is usually made visible to an unlimited number of clients, and an actual declaration matches a single specific expect declaration.