Let’s use IntelliJ as a game engine, just because we can
summary
Builds real mini-games inside the IDE using the IntelliJ plugin platform, Kotlin and Java Swing: a Pong renderer with a Unity-style Vector2 port, a “State Invaders” scanner that finds VAR fields via the PSI tree and turns them into enemies, a “Packag Man” that parses Gradle/Maven dependencies and deletes lines when ghosts are eaten, a Sonic-like unit-test collector that removes tests, and a rhythm “Code Hero” that forces typed paste verification. Rendering reaches 120 fps in small demos, explosions rewrite and resubmit editor text, and changes can be force-pushed.
AI-written summary · about
chapters (11)
- 0:00Introduction and motivation
- 3:17Why IntelliJ as a game engine
- 8:20Rules and performance goals
- 10:46Pong demo in IntelliJ
- 16:42Space Invaders with mutable state
- 22:50Pac-Man with package dependencies
- 27:10Explosion effect demo
- 31:30Sonic the test dog game
- 37:19Code Hero and copy-paste challenge
- 44:26Future requests for JetBrains
- 47:38Closing thoughts and Q&A
related talks
43mAlpha, Beta, Gamer: Dev Mode
49mDesign Tools Should Read and Write Code
47mLet's build components, not layers
12mAdding Interactive Visual Syntax to Textual Code
23mFruit Ninja 2 Tech Talk: Creating with data-driven components
42mThe Case for Whimsy
41mCompose beyond Material
36mTechnical Challenges of Building a Visual IDE for React Components