The Gram Code Editor - 2026-07-17

I'm planning to create an issue to discuss ideas for improvement

Hi

> I'm liking gram (I hadn't used Zed before), but it (Zed, in this case) was clearly created for people with the latest macbooks. it's not working great on older hardware well, coming from a JetBrains IDE, Gram feels very fast ↺

but if the LSP is slow, there isn't much Gram can do

However, the GPU rendering something is an issue for some old laptops I still use, true.

no LSP

my main dev machine has a good CPU but it's using an old GT730 for graphics (GF108 chip, Fermi). wgpu does not seem to work on it. Alacritty (also rust using gpu acceleration but via glutin) works fine though. Similar stories on a couple of other old machines

for the main dev machine software rendering works and it's not laggy but the CPU goes to 40-50% load often, just for simple editing. I started to notice my fans doing a lot more noise. it's not hard to do a couple of improvements to the software rendering path that could improve the situation

does not seem hard, at least.

oh right, software rendering is not usable on my low-end devices too, I had reported that here https://codeberg.org/GramEditor/gram/issues/247#issuecomment-14168471 :(

Hello, I was wondering, is it possible to install an extension by simply putting the compiled .so somewhere into the `~/.local/share/gram/extensions` directory? I just don't have rustup on the same context as gram, but I can compile the extension into .so elsewhere. So I'd like to avoid the step where gram calls rustc.