3 ms·
Ehh I don't buy that the market was ready 10 years earlier (in 2006) for open-source LSP implementations. You gotta have someone write those language servers f
by muglug 1y ago
Ehh I don't buy that the market was ready 10 years earlier (in 2006) for open-source LSP implementations.
You gotta have someone write those language servers for free, and the language servers have to be performant. In 2006 that meant writing in a compiled language, which meant that anyone creating a language server for an interpreted language would need to be an expert in two languages. That was already a small pool of people.
And big multiplayer OSS platforms like GitHub didn't exist until 2008.
- skydhash 1y agoAnd the fact is that anyone working professionally was using an IDE, and anyone else was fine with grepping and using ctags. I think LSP is only truly useful in two contexts, global symbols (even with namespacing) and confusing imports. In language like C, you mostly have a few structs and functions, and for the ones in libraries, you only need to include a single header. With Python, the imports are concise and a good references gives you the symbol identifier. But with languages that needs an IDE or LSP, you find yourself dealing with many imports and many identifiers to write a few lines of code and it becomes quickly unmanageable if you don't have completion or autoimports.
- autarch 1y ago> And big multiplayer OSS platforms like GitHub didn't exist until 2008. SourceForge launched in 1999. I think GitHub is better in many ways, but the basic building blocks of hosted repo, issue tracking, and discussions (via email lists) on Sourceforge. I collaborated with folks on a number of projects on SourceForge way back when.