I wrote this for the infracost LSP so I could write multiple IDE extensions. Its not even really a language server, its just a neat way to parse the Terraform&#x2F;Cloudformation and return diagnostics.Language servers are cool!

Started in case I ever build a language server, thanks! The interface looks very understandable, and the debug server looks really nice.Now that I think about it, it might be really cool to add LSP to my CLI framework[0] (I already have tab completion for shells, why not make an editor plugin if it&#x27;s this easy ..)0: <a href="https:&#x2F;&#x2F;github.com&#x2F;bbkane&#x2F;warg" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;bbkane&#x2F;warg</a>

I actually started out using that. I wanted a debug UI to track messages which was the major driver in creating my own tbh

Have you tried out <a href="https:&#x2F;&#x2F;github.com&#x2F;tliron&#x2F;glsp" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tliron&#x2F;glsp</a>?

To give you some idea how versatile a language server is, I wrote one once to provide go-to-definition between two related blocks in a large proprietary YAML configuration file. If the definition was missing, it would also render the red squiggly line to indicate that something was misspelled.Another time I used one to make the hosts in my SSH configuration file clickable to either open a terminal with a session or just to display cpu&#x2F;memory statistics.Lots of neat editor-independent interactions can be enabled using language servers.

thanks!Thankfully, I finally had a reason to build an LSP (infracost LSP), so it motivated this and I&#x27;m really pleased with it

Very nice. Now I want to build a language server. If only I had anything to build it for.

Markdown survived because it optimized for the right tradeoff: human readability with just enough structure for machine parsing.

The godoc format enforces that the comment start with the name of the identifier and be a complete sentence(s) describing what that identifier does. Predates LLMs

But you don&#x27;t have to add a docstring. Cases like this are worse than no docstring at all, because it wastes the reader&#x27;s time.If you add one, at least make the effort to provide some useful information. For example which is more severe: higher or lower numbers.

Yeah some times godoc comments look crap by necessity

<pre><code> &#x2F;&#x2F; DiagnosticSeverity indicates the severity of a diagnostic.
 type DiagnosticSeverity int
</code></pre>
Hmmm :robot:

Show HN: Create a full language server in Go with 3.17 spec support