Integrating Developer Experiences - Build Server Protocol
summary
Build Server Protocol (BSP) goes from concept to working integration: IntelliJ implements a BSP client in IntelliJ and Fury implements a BSP server in Fury, connecting through bloop so import, compile, diagnostics and progress all work without tool-specific plugins. Compilation progress shows per-target timing (Akka actors 23s) and diagnostics flow as LSP-style messages. Adding basic BSP support for a tool is small—around 400–500 lines in Fury—and version 2.0 is imminent.
AI-written summary · about
chapters (29)
- 0:00Intro
- 0:26The IDE
- 1:05Justin Kaeser
- 2:47Integrated Development Environment
- 3:56Integration Issues
- 6:04Build Tools
- 7:36Language Server Protocol
- 8:31Challenges
- 10:01Fury
- 11:04Fury in IntelliJ
- 12:38BSP Client in IntelliJ
- 13:05BSP Client in Fury
- 14:19Build Server Protocol
- 16:37Server Discovery Protocol
- 17:57Life Cycle
- 18:30Build Structure
- 20:22Diagnostics
- 21:00Progress Notifications
- 21:36Testing
- 23:23VSP Support
- 24:05IntelliJ Challenges
- 28:36Compile
- 28:48BSP Roadmap
- 30:40Other Protocols
- 32:41End
- 35:16Using BSP with IntelliJ
- 37:27Questions
- 39:55Test suite
- 40:37Language support
related talks
28mIntegrating Developer Experiences - Build Server Protocol and beyond
30mINTEGRATING DEVELOPER EXPERIENCES - BUILD SERVER PROTOCOL AND BEYOND
42mIntegrating Developer Experiences
03mInterview
47mDesign Challenges of Bloop
29mExploring Scala Tooling ecosystem
31mTaming the Beast - Better Bazel in IntelliJ
39mMeet Bloop and Get More Productive with Scala
