Let’s use IntelliJ as a game engine, just because we can
summary
Kotlin code runs inside the IntelliJ plugin platform using JCEF for optional HTML but the games are native plugins, render sprites and physics at a claimed 120 FPS, and use the IDE’s PSI tree to find mutable variables. Built demos: Pong, “State Invaders” that maps mutable vars to aliens (chance-of-production-crash drops from ~51% to 0% when killed), a Pac‑Man maze built from dependency names that removes lines when ghosts are eaten, a vertical Sonic for unit tests, and an OSU‑style paste blocker; exploding‑code is published on the marketplace and sources are on GitHub.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:15Experiment rules
- 7:10Pong proof of concept
- 9:43Backend development sins
- 10:26State Invaders
- 14:18Pac-Man dependency fight
- 18:56Explosions and feedback
- 20:03Sonic the Test Dog
- 26:06Code Hero rhythm game
- 32:55Games showcase
- 33:17IntelliJ feature requests
- 40:07Coding superpower
- 42:14Doom in IntelliJ
- 43:40Q&A
related talks
50mLet’s use IntelliJ as a game engine, just because we can
42mLet’s use IntelliJ as a game engine, just because we can
41mKotlin Notebook Meets IntelliJ Platform
36mExploring Kotlin Multiplatform
46mHow we’re improving performance of IntelliJ IDEA Kotlin plugin
59mKotlin Notebooks for Spring Developers
38mThe Battle of the IDEs (Pokemons)
01h 03mWhy Do Developers Love IntelliJ IDEA?