---
title: "Discussion on \"Building an IDE Out of Spare Parts\" | Hashnode"
description: "Discussion on \"Building an IDE Out of Spare Parts\". In this article, I explain why I chose to have language specific servers instead of 1 big LSP setup."
url: "https://hashnode.com/posts/building-an-ide-out-of-spare-parts/6a9b22ff182069349e514c5b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building an IDE Out of Spare Parts](https://blundersnbuilds.hashnode.dev/building-an-ide-out-of-spare-parts?utm_source=hashnode&utm_medium=feed)

In this article, I explain why I chose to have language specific servers instead of 1 big LSP setup.

Sep 4 · 3 min read · blundersnbuilds.hashnode.dev  
Read the article

-   [#neovim](https://hashnode.com/tag/neovim)
-   [#lsp](https://hashnode.com/tag/lsp)
-   [#mason](https://hashnode.com/tag/mason)
-   [#nvim](https://hashnode.com/tag/nvim)
-   [#vim](https://hashnode.com/tag/vim)
-   [#terminal](https://hashnode.com/tag/terminal)

## Written by

[Sushanth Kamabathula](https://hashnode.com/@sushanthk)

@sushanthk

  
[View profile](https://hashnode.com/@sushanthk)

Notes on code, chess, mistakes, and the tools I build with.

I'm Sushanth, a high school senior in Hyderabad, India. This is where I write about the things I spend time on: learning from mistakes, building things in code, and the tools I actually work with day to day. I hold the Candidate Master title and a FIDE International Master norm, earned across roughly 140 rated tournaments in six countries. I stopped competing in 2025, but the habit competition taught me, sitting down after every loss and figuring out exactly where I went wrong, shapes how I approach everything else. On the technical side, I've gone deep on C/C++ through Duke University and University of London coursework. I'm also someone who likes a good terminal workflow and enjoys exploring (and abandoning) productivity tools. Expect posts on Neovim, tmux, what broke this week, and whatever I'm tinkering with.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.