# intellij-platform Open-source JVM-based platform for building extensible IDEs and language tooling. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Релиз OpenIDE 2026.2: одна IDE для Java, Kotlin, Go, Python и веб-разработки DevFeed: [Релиз OpenIDE 2026.2: одна IDE для Java, Kotlin, Go, Python и веб-разработки]() Original publisher: [Read original article]() Author: honest\_niceman (Haulmont) Published: 2026-09-17T09:12:16Z Content type: release Language: ru Sources: [Tagir Valeev]() Topics: [intellij-platform](), [Java](), [Git](), [Kotlin](), [Gradle](), [Databases](), [Docker](), [Go](), [Python](), [SQL](), [JSON]() Tags: [2](), [2026](), [2026-2](), [compose](), [db-eaa4bca15522](), [docker](), [docker-bdf52bf499c4](), [git](), [go](), [gradle](), [ide-1f5689fe989b](), [ide-af948443b041](), [ide-java-0ad4946a0e57](), [intellij-idea-27f15aabb340](), [intellij-platform](), [java](), [javascript](), [json](), [kotlin](), [openide](), [openide-2026-2](), [openide-pro](), [oracle](), [sql](), [structure]() ### AI overview OpenIDE 2026.2 updates its base platform, expands Java and Kotlin support, improves Git and Gradle workflows, and updates its Java profiler. The release also includes improvements to the DB client and Docker plugin, including SQL formatting, Greenplum support, JSON highlighting, and enhanced Compose service management. ### Source excerpt Обновили базовую платформу до версии 2026.2, расширили поддержку Java и Kotlin, улучшили работу с Git и обновили Java-профилировщик. Доработали редактор и подсказки в терминале, добавили проверки настроек Gradle и упростили переход к исходникам библиотек. Через Git worktrees теперь можно работать с несколькими ветками одновременно. Читать далее ## Java Weekly, Issue 659 DevFeed: [Java Weekly, Issue 659]() Original publisher: [Read original article]() Author: baeldung Published: 2026-08-15T10:23:09Z Content type: article Language: en Sources: [Baeldung]() Topics: [Programming](), [intellij-platform](), [Model Context Protocol](), [elasticsearch]() Tags: [elasticsearch](), [github](), [gradle](), [idea](), [java](), [mcp](), [netflix](), [no-ads](), [no-after-post](), [no-before-post](), [no-optins](), [programming](), [releases](), [security](), [weekly-review](), [weekly-review-no-ads-no-after-post-no-before-post-no-optins]() ### AI overview Java Weekly, Issue 659 is a roundup of Java ecosystem reading, including MCP server evolution, Project Valhalla, JVM security, DuckDB, HTTP extension design, AI features in IntelliJ IDEA, webinars, and software releases. ### Source excerpt Equality in Java is evolving. The post Java Weekly, Issue 659 first appeared on Baeldung. ## Live coding with dir stepper DevFeed: [Live coding with dir stepper]() Original publisher: [Read original article]() Published: 2026-07-16T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [intellij-platform](), [IntelliJ IDEA](), [Git](), [ide](), [Code](), [Documentation]() Tags: [code](), [coding](), [git](), [ide](), [intellij-idea](), [intellij-platform](), [kotlinconf](), [plugin](), [presentation](), [procedural](), [refactoring]() ### AI overview The article describes creating a workflow for live-coding presentations after finding that Git commits and interactive rebases were cumbersome for managing sequential coding steps. It explores using IntelliJ IDEA as an extensible platform for a tool that can move through steps, jump to completed states, refactor steps, and keep the process unobtrusive for the presenter and audience. ### Source excerpt Two months ago I gave my first ever live programming talk at KotlinConf. It was called "Talking to terminals (and how they talk back)", and you can watch it here. I've previously done slide-heavy talks which contained small demos or navigating through an existing codebase. Since this talk was starting from nothing, I decided to just write all the code from nothing. This meant spending the majority of the time in the IDE, but also figuring out how to remember what I was supposed to be writing at each step. Making the wrong choice The exceedingly obvious solution to having a series of steps in a live coding presentation is a git repo and a commit for each step. Unfortunately, this is a huge pain in the ass and really doesn't work at all (at least not for me). I started with commits, but by the 7th or 8th commit I was spending more than half my time doing interactive rebases over the entire history. Need a function in step 8 that should've been extracted between step 3 and 4? That's another 10 minutes rewriting history. Because it's a small set of files that are changing, every commit conflicts with any changes to history. It's also not clear how you actually move through the history. We want to start from nothing and move forward through history. Generally, git helps you jump backwards from the latest, not stepping forward from the oldest. It's not impossible, it's just clearly going against the grain. The problem, defined Now thoroughly enjoying this distraction from writing the actual talk, I distilled what I was trying to solve. Ability to manually write the changes required or to simply jump to the finished step. Some steps are important to watch unfold while others are procedural. This also can help with time management when I (inevitably) run low on time. Easily refactor steps as I go. Later steps often requiring refactoring previous ones to minimize the diff. As the talk evolves I want to add or merge steps. Nearly invisible to me and the viewer. I don't want t