My Dream Ide Does Not Exist

Tue, 16 Jun 2026 06:52:46 +0200

Emacs is my main IDE. It is powerful, versatile, and very stable. It has a few limitations I can live with, like the absence of multi-threading, which sometimes gets in the way on rare occasions. Native compilation gave it wings and the Doom configuration layer enables an improved UX, great keybindings and sane defaults. Did I mention Org, and more particularly Org-Roam?

On a side note, Elisp (is a (nightmare (of brackets (you) need to (follow through) (and count) (which (I suck at))))) — more on that in another post about programming language UX and why I love Ruby. But in the end, I can live with a few crashes here and there as I get lost in the bracket maze when editing my config.el. I can count.

That said, there is some friction involved when using Emacs. MacOS integration is not perfect, especially when it comes to managing the emacs daemon. I cannot make Dape (the DAP mode for emacs) work with ruby. I also find the UI to be a little slow: typing has a tiny slight delay which kind of gets annoying in a subtle way. And that slaps you in your face when you open Neovim.

I’m a TUI nerd, so Neovim is one of the alternatives I turn to when I get bored or annoyed at Emacs. Like Emacs with Doom, Neovim has the LazyVim configuration layer to ease most of that side of things. Lua has a much better UX than Elisp, and man, the whole beast is blazing fast, both in terms of loading time, overall snappiness, and typing rendering. Some plugins are really better than the Emacs stuff (thinking about vim-dadbod-ui — what a funky name, btw), some less (try to beat Vertico + Marginalia + Orderless). Debugging ruby stuff works out of the box.

I have made my Neovim as similar to my Doom emacs configuration as possible, so switching is close to seamless. But I miss a good integrated terminal experience - I am not very happy with how :terminal behaves, and it feels kind of odd to open a terminal inside an IDE which lives in a terminal. I am trying to find a way to overcome this, but for now, this is where some of the friction comes from.

This is usually when I open Zed.

(Well, sometimes, I will start a Helix session, get excited by the speed and simplicity, and then get frustrated for the lack of a plugin system — mainly for git/JJ, running tests and that stuff — read the 11-month-old release notes and related issue/PR threads, realize this is not going anywhere, and only then, open Zed.)

Zed is cool. It is like VScode stripped of the bloat and all the Microsoft cringe. It is sexy. Its development is moving fast. It features AI as a first-class citizen, but does not shove it up to your face without asking you first, and you can ignore it altogether. Zed respects its users by trying to serve them with a good product, not shove junk down their throat to get ready for the next VC fund. At least for now.

Zed is not a TUI, but it is damn fast. I get all the snappiness of Neovim, along with most keybindings. I get a rich plugin ecosystem. But it is still somewhat limited compared to Emacs and Neovim — I am not blaming the Zed team, though, I am comparing a 4-year-old project to IDE veterans (considering Neovim and its ecosystem is built on the foundations of Vim).

Zed is currently lacking a Telescope-like picker (but it is coming), a merge tool, and a more capable plugin system to be able to connect to, and manage your database, for instance, or offer the possibility to manage Jujutsu natively (you can do some of that stuff with workarounds, mainly with tasks). But the main friction comes from the Vim keymap integration: it is good, but it is not available everywhere… like, you cannot do some stuff when in menu mode. So if you want a mouse-less experience, it just does not cut it.

So I launch Emacs… Emacs is where I feel at home, wearing my comfy slippers. I am editing the final draft of this post in Emacs right now, actually.

But that’s until I get frustrated again and decide to launch Neovim again…

What is wrong with me? 🙄

Zed Turtle Extension

Mon, 19 May 2025 00:00:00 +0000

I have just released the first version of a Zed extension for the Turtle format.

Zed?

Zed is a very cool text editor / IDE by the creators of Atom and Tree-Sitter. It is written in Rust and it caught my interest because it is very very lean, it has Vim, JetBrains, VSCode, Helix and Emacs keybindings and a growing extension system. It has multiple advantages (at least in my opinion) over the competition, and I feel it builds upon other IDEs’ strengths while being very pleasant to use. It has pair-programming and remote development baked-in from day one. Most importantly, it is not owned by a multi-billionnaire-led, fascist-supporting company that will eventually sunset or paywall the product once the whole world is addicted to it. And yes, it features AI, MCP and agentic editing if that’s your thing, but that’s something you can turn off, which I did. Zed is currently driving me away from Emacs (and that means something if you ask me). You really should give it a try. Stop reading and download it.

Turtle?

That’s the RDF file format I use extensively at work. It renders RDF graph triplets in a readable format, making it easier to manage than plain RDF/XML or JSON-LD other semantic web file formats. This is an sample Turtle file:

@prefix rdf:  .
@prefix dc:  .
@prefix ex:  .

'''


  dc:title "RDF/XML Syntax Specification (Revised)" ;
  ex:editor [
    ex:fullname "Dave Beckett";
    ex:homePage 
  ] .

Extension?

So why a RDF extension? As I was editing .ttl files for work in Zed, I started looking for an extension to highlight my code and navigate through it, but didn’t find one. So I decided to create my own! I looked at the Zed developer documentation, took a little inspiration from existing extensions and started writing my very first Rust lines of code — which was another motivation for starting that endeavor. All I had to do is gather resources scattered here and there on the internet:

A ready-made tree-sitter project for Turtle
A language server available here

…and write a few lines of code to turn those into usable Zed features.

The features

Here is what the extension does for now:

Code highlighting
Symbol navigation
LSP — the server is automatically downloaded when you edit your first Turtle document.

What I plan on adding in a near future is:

Formatting
SHACL validation
A better LSP with go to definition / implementation (and maybe formatting as part of the LSP)

The Zed Turtle extension featuring the symbol navigation

What you can do

I hope the plugin serves both the Zed and the Semantic Web communities. If you are interested in this extension, do not hesitate to give it a try, report issues or add feature requests, or even give me a hand to improve it!