<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sitt Guruvanich</title>
    <description>The latest articles on DEV Community by Sitt Guruvanich (@aekasitt).</description>
    <link>https://dev.to/aekasitt</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F745360%2Fa6645a83-0278-4f6b-b9f4-c99ce18c212b.png</url>
      <title>DEV Community: Sitt Guruvanich</title>
      <link>https://dev.to/aekasitt</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aekasitt"/>
    <language>en</language>
    <item>
      <title>Tylsp - the LSP Plugin you didn't know you needed for Neovim</title>
      <dc:creator>Sitt Guruvanich</dc:creator>
      <pubDate>Sat, 10 May 2025 09:23:40 +0000</pubDate>
      <link>https://dev.to/aekasitt/tylsp-the-language-server-protocol-you-didnt-know-you-needed-3ai4</link>
      <guid>https://dev.to/aekasitt/tylsp-the-language-server-protocol-you-didnt-know-you-needed-3ai4</guid>
      <description>&lt;p&gt;Just like a typical &lt;a href="https://astral.sh" rel="noopener noreferrer"&gt;Astral&lt;/a&gt; fanboy, as soon as &lt;code&gt;ty&lt;/code&gt; was announced as an extremely fast Python type checker and language server, written in Rust, I wanted to try my hand on it. It did not disappoint me that the speed and flexibility of the language server caught up to my usual &lt;code&gt;pylsp&lt;/code&gt; on &lt;code&gt;neovim/nvim-lspconfig&lt;/code&gt; so I went ahead and decided on writing my very own built-in language server protocol for the first time.&lt;/p&gt;

&lt;p&gt;😸🐙 Let there be &lt;a href="https://github.com/aekasitt/tylsp.nvim" rel="noopener noreferrer"&gt;Tylsp&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;While I'm not yet familiar with setting up configurations for a language server protocol, ty fit in quite well with existing syntax and gave me clear warnings when I make intended errors and the appropriate warnings did not lag down my text editor any bit. My first time writing an LSP plugin was a smashing success, and I hope to have ty added to &lt;code&gt;nvim-lspconfig&lt;/code&gt; official supported list as soon as possible. In the meantime, I will be keeping my eye on &lt;code&gt;ty&lt;/code&gt; and maintain &lt;code&gt;tylsp&lt;/code&gt; until further notice.&lt;/p&gt;

&lt;p&gt;Check out &lt;a href="https://github.com/astral-sh/ty" rel="noopener noreferrer"&gt;ty&lt;/a&gt;&lt;br&gt;
Leaked/Announcement by Charlie Marsh: &lt;a href="https://x.com/charliermarsh/status/1920536415798009918" rel="noopener noreferrer"&gt;Leak&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
