You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Mentors**: Shauvik Roy Choudhary, Ryan U, Michael Noah, Claudia Babescu (all from Uber)
15
43
16
44
From picking up Kotlin from scratch to building a compiler-integrated Language Server with the new Analysis API, Hemram’s project expanded the boundaries of Kotlin tooling.
17
45
18
46
Working with mentors from Uber and the Kotlin Foundation, he delivered a modern, open foundation for editor integrations and future AI-assisted tools for the Kotlin Language Server Protocol.
19
47
20
-
## **About the author**
48
+
## About the author
21
49
22
50
Hi, I’m Hemram, a developer from Bangalore, India, passionate about developer tooling and compiler technologies.
23
51
24
-
## **Intro and motivation**
52
+
## Intro and motivation
25
53
26
54
I’ve always been curious about how Language Server Protocols (LSPs) work behind the scenes. When I came across this project idea during Google Summer of Code 2025, it immediately caught my interest.
27
55
28
56
During that time, I was exploring kotlin-language-server, which is an open-source Kotlin LSP using `kotlinc` under the hood. I had experienced some bottlenecks and understood what the community wanted. On researching further, I found out about the Kotlin Analysis API, which is a better way to communicate with the K2 compiler compared to the inefficient `kotlinc`. This formed the base of my proposal for this LSP project.
29
57
30
-
## **Technical Highlights**
58
+
## Technical Highlights
31
59
32
60
The project involved designing a new Language Server Protocol (LSP) implementation based on version 3.17 of the spec.
33
61
34
-
### **Key components:**
62
+
### Key components:
35
63
36
64
***Kotlin Analysis API** – leveraged for semantic analysis and compiler-backed insights.
37
65
***LSP4J** – the Java framework used for implementing the LSP specification.
38
66
***RocksDB** – integrated as a persistent key-value store for efficient codebase indexing and symbol resolution.
39
67
40
-
### **Core features implemented:**
68
+
### Core features implemented:
41
69
42
70
* Project handling for the Gradle build system (single and multi-module for both Vanilla and Android)
43
71
**Go to Definition*
@@ -51,31 +79,31 @@ The project involved designing a new Language Server Protocol (LSP) implementati
It was an exciting period working under the Kotlin Foundation, building a Kotlin language server.
61
89
62
90
I first heard about GSoC a few years ago and always admired how contributors made a real impact in open-source ecosystems. This year, I finally took the leap, and it’s been a rewarding experience from start to finish.
63
91
64
92
There were some challenges along the way, like when the official Kotlin LSP was announced at KotlinConf 2025\. As it was in the pre-alpha stage, I had to fork an incomplete project and contribute to GSoC on the basis of that. Beyond that, the journey was pretty smooth, with the completion of the Kotlin LSP as an MVP.
65
93
66
-
## **What I learned**
94
+
## What I learned
67
95
68
96
As it was the starting point of my open-source journey, I learned about how real collaboration happens, from writing clear commits and discussing design choices to adapting when project goals shift.
69
97
70
98
One of the biggest takeaways from my GSoC journey was stepping out of my comfort zone and realizing how much it stretched my learning curve. I had to pick up Kotlin from scratch, explore the Analysis API, and work across multiple tools and environments. It was also incredibly rewarding to see my work tested, reviewed, and used by others in the community.
0 commit comments