Integrating Developer Experiences
summary
A standard JSON-RPC protocol now maps build units called targets to IDE modules so editors outsource compilation and get per-target compile progress and diagnostics; IntelliJ and Metals act as BSP clients while bloop, Fury (as bridge), and experimental No act as servers, and BSP v2.0 is implemented in the Scala plugin. Project discovery uses a client-server discovery file placed in the repo, shared-sources get synthetic modules and compilation is delegated to the build tool (example showed a 55s target compile), and test and progress notifications are already supported.
AI-written summary · about
chapters (14)
- 0:00Introduction to integrated development environments
- 2:02Speaker and Scala plugin
- 3:06Build tool integration challenge
- 7:55Language Server Protocol
- 11:11Modern build tools rise
- 15:25Build Server Protocol intro
- 18:48BSP discovery and lifecycle
- 21:47Build targets and actions
- 24:05IntelliJ BSP demo
- 29:59Project import in IntelliJ
- 33:11BSP ecosystem overview
- 35:09BSP roadmap
- 37:15Beyond BSP standards
- 39:06Call to action
related talks
30mINTEGRATING DEVELOPER EXPERIENCES - BUILD SERVER PROTOCOL AND BEYOND
28mIntegrating Developer Experiences - Build Server Protocol and beyond
43mIntegrating Developer Experiences - Build Server Protocol
03mInterview
31mTaming the Beast - Better Bazel in IntelliJ
39mMeet Bloop and Get More Productive with Scala
58mWish You Were Here: Stories of Building a Remote Development IDE
19mExploring Scala Tooling ecosystem
