<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IDE on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/ide/</link><description>Recent content in IDE on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/ide/index.xml" rel="self" type="application/rss+xml"/><item><title>Thoth: An IDE That Grows With You</title><link>https://lab.artur-rios.tech/brainstorms/thoth/</link><pubDate>Wed, 21 Oct 2026 12:00:00 +0000</pubDate><guid>https://lab.artur-rios.tech/brainstorms/thoth/</guid><description>&lt;p&gt;An IDE that adapts to your exact needs, nothing more, nothing less.&lt;/p&gt;&#10;&lt;h2 id="features"&gt;Features&lt;a class="heading-anchor" href="#features" aria-label="Link to this section"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Starts like a simple and lightweight code editor and the user can activate modules to add functionalities to fill their needs. For example a .NET module, an Angular module etc&lt;/li&gt;&#10;&lt;li&gt;Experience must be similar to Visual Studio Code on Linux and Windows and similar to LunarVim on terminal&lt;/li&gt;&#10;&lt;li&gt;Do not support extensions, the idea is to use the modules to extend the application on-demand&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="platforms"&gt;Platforms&lt;a class="heading-anchor" href="#platforms" aria-label="Link to this section"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Linux&lt;/li&gt;&#10;&lt;li&gt;Windows&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="first-release-modules"&gt;First release modules&lt;a class="heading-anchor" href="#first-release-modules" aria-label="Link to this section"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;.NET&lt;/li&gt;&#10;&lt;li&gt;Angular&lt;/li&gt;&#10;&lt;li&gt;React&lt;/li&gt;&#10;&lt;li&gt;Flutter&lt;/li&gt;&#10;&lt;li&gt;Python&lt;/li&gt;&#10;&lt;li&gt;Rust&lt;/li&gt;&#10;&lt;li&gt;HTML/CSS&lt;/li&gt;&#10;&lt;li&gt;JavaScript/TypeScript&lt;/li&gt;&#10;&lt;li&gt;Java&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="technology-stack"&gt;Technology stack&lt;a class="heading-anchor" href="#technology-stack" aria-label="Link to this section"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The feature that shapes the stack most is the second one: the same IDE in a&#10;window and in a terminal. If the window and the terminal are two programs, every&#10;feature is built twice. So the design starts from one &lt;strong&gt;core&lt;/strong&gt; that owns&#10;everything an editor does, such as buffers, cursors, syntax trees, language&#10;servers, commands, keymaps and modules, and two thin &lt;strong&gt;front ends&lt;/strong&gt; that only&#10;draw what the core describes and send it the user&amp;rsquo;s input. The core and the&#10;front ends talk only through typed messages: input events go in, view updates&#10;come out. Neither side calls into the other, so a front end can be replaced,&#10;and the core could later run in a separate process, for example on a remote&#10;machine over SSH.&lt;/p&gt;</description></item></channel></rss>