This is what I've been doing for years. It's remarkably stress-free!

I agree. Their fountain pens and inks are just rock solid, and I've practically never run into an issue with any of mine. I wish more companies would obsess over the details like Pilot does.

I'm working on a Neovim plugin to render LaTeX in Markdown, and I'm struggling with this. Why is it so hard to simply render an image from KaTeX?

What are you struggling with? If you want an image output, there a reason you want to use KaTeX for this, and can't just use actual LaTeX?

KaTeX depends on the browser engine to do most of the layout, so generating an image would require a tool which converts the HTML nodes back into an image. There are some tools that can do that (like html2canvas), but using LaTeX to generate a PDF and then converting that to an image is probably going to be easier.

I am happy to package it and port it for Gtk/GNOME today.

If you end up doing that, please post it here. I'd be a very happy user of that extension

Also happy to test it out on Gnome

https://github.com/abrauchli/usbee - still missing some features but it's a start. Happy to take PRs.

I am a big fan of fountain pens, and I think they're a great hobby.

Finally someone said fountain pens!!! I got into it as well. Made me write more. It is great.

I also got Fira Code, followed by Ubuntu Mono, Source Code Pro, and Oxygen Mono.

I agree. If the real concern is the flood of low-effort slop, unmaintainable patches, accidental code reuse, or licensing violations, then the process should target those directly. The useful work is improving review and triage so those problems get filtered out early. The genie is already out of the bottle with AI tooling, so broad “no AI” rules feel like a reaction to the tool and do not seem especially useful or enforceable.

Whoa, I have been looking for AI-enhanced tab grouping for a while. This is actually pretty awesome.

I had this same issue early on when trying to adopt Obsidian. I was overwhelmed by all the "systems" and I was worried I was creating a headache for myself later on. Now I just focus on dumping text in, using search, and linking only as needed. Basically don't overdo it.

That makes sense for code or technical text, but it is less relevant for car UIs. In an infotainment system you almost never see ambiguous strings where O vs 0 or I vs l matters. Everything is highly contextual, short, and glance-based. These fonts are tuned for distance, motion, glare, and quick recognition, not for reading arbitrary identifiers. If it tested poorly in real driving conditions that would be a real problem, but judging it by programmer font rules feels like the wrong yardstick.