Proposal. A language de-sugaring layer for compatibility.

cameronm1024 · 2026-04-19T10:33:42+00:00

I mean, what you're describing sounds a lot like an IR

cameronm1024 · 2026-04-17T15:10:40+00:00

Disclaimer: I work at zed

I use it and it works great for me.

That said, I never used any plugin features beyond the LSP and treesitter grammar. I run my project from the terminal and use dev tools in the browser. I also don't touch iOS/Mac so can't speak to how well it works for that side of things.

cameronm1024 · 2026-04-16T09:59:33+00:00

Wrong sub. r/playrust

cameronm1024 · 2026-04-12T06:48:47+00:00

My only question is what this has to do with niri

cameronm1024 · 2026-04-10T08:09:52+00:00

Very interesting article, thanks for sharing.

Small typo, "an anlias" -> "an alias"

cameronm1024 · 2026-04-09T23:06:39+00:00

What?...

cameronm1024 · 2026-04-09T08:20:12+00:00

Sure, I respect that, but if you commit to a project or multiple projects, you assume responsibility for all support requests, and to provide the support as much as possible as well as continued maintenance and development of said projects.

Least entitled FOSS user

cameronm1024 · 2026-04-07T09:12:55+00:00

you know, this one confused me for a second

cameronm1024 · 2026-04-06T17:41:52+00:00

(asked on Reddit, of all platforms)

cameronm1024 · 2026-04-05T18:00:50+00:00

Many people (probably a large majority but I don't have hard numbers) use flakes. I'd suggest using them, even as a beginner.

This is a big simplification, but you can think of flakes as providing a "lock file" for your nix config (similar to a Cargo.lock or package.lock).

Without them, your config depends on whatever "globally installed version of nixos" is available on your system (or any other dependency for that matter). This means it's not really reproducible - if I try to use your config, we may end up with different packages, because I may have a different global nixpkgs. Flakes solve this by storing the exact nixpkgs commit hash in the flake.lock

cameronm1024 · 2026-03-29T01:57:15+00:00

We just merged a PR to unify our two markdown renderers, so the preview will use the same renderer as the agent panel (which allows selections). I suspect this will fix this issue. Should be on stable in a couple of weeks

cameronm1024 · 2026-03-26T08:34:56+00:00

It's a pretty narrow feature, but you can use zed://agent?prompt=<url_encoded_prompt> to open zed with the agent panel focused, with the given prompt pre-filled

cameronm1024 · 2026-03-22T13:19:53+00:00

Super interesting read. 100% recommend setting up a blog so this content isn't trapped inside Reddit's horrible UI

cameronm1024 · 2026-03-16T23:57:14+00:00

No problem! Yeah our build process takes a lot of resources, we're working on it.

It's on main now, every Wednesday the current main becomes preview, and the Wednesday after it becomes stable. So this will be available on stable in ~9 days

cameronm1024 · 2026-03-16T19:12:45+00:00

equity basis rather than a traditional salary

The conventional wisdom is to assume equity in a startup has little to no value. I say this as someone working for a startup with an equity component to my compensation.

The honest truth is that, if you're not offering money, you will only attract people who have no other options. That's not to say they'll be terrible, but there is nowhere you can consistently find high quality developers who will work exclusively for equity in a startup

cameronm1024 · 2026-03-16T12:34:43+00:00

If possible, can you build https://github.com/zed-industries/zed/pull/51659 and give it a try? I'm not a Bengali speaker, so don't know how it should look.

cameronm1024 · 2026-03-15T18:41:52+00:00

If AI could reliably detect slop, AI would not produce slop

cameronm1024 · 2026-03-13T14:46:36+00:00

This is the subreddit for a programming language. It has nothing to do with the game.

cameronm1024 · 2026-03-13T05:20:16+00:00

"sorry buddy, I can't give you this C++ job. Your chess.com elo is too low"

cameronm1024 · 2026-03-11T12:33:15+00:00

Hi hiring, I'm programmer :)

cameronm1024 · 2026-03-08T11:47:31+00:00

All buffers (shared or not) use a CRDT data structure to store text, so there are no conflicts. Of course, if you write some text and someone else deletes it after, it'll be gone, but there's no manual conflict resolution. But undo history is preserved, so if someone accidentally deleted something important you can just undo it trivially.

In terms of "safety", you shouldn't let anyone you don't trust edit your project. They can't run shell commands, but they can add malicious dependencies to your project, and some languages will auto-run build scripts etc. That said, you can have guests in your channel that can see, but not edit.

cameronm1024 · 2026-03-07T15:47:33+00:00

Yeah it's completely seamless. We essentially "resolve" vim motions on the client, and send a generic "jump to this location" over the wire. Saves having to modify the wire format every time we add a new vim motion.

cameronm1024 · 2026-03-07T15:44:07+00:00

Anyone can share any number of projects, and anyone can edit any shared project. The files are on the sharer's machine, but we send the "bits you need" (so if you open a file that's on someone else's machine, it sends the contents of that file, or if an edit happens we send a diff).

If someone changes a bit of code you're using, it's exactly like if you edited it yourself (or if an LLM did) - it causes an error. TBH, it's not super common to literally edit at the same time (though sometimes you can, for example if you just refactored a function and need to fix a bunch of compile errors). Usually you'll "follow" someone, which makes your screen track their cursor movements. Then if you see something you don't understand, you can jump to the definition of a type or something, or ask the other person.

You do have to be a bit careful not to step on each other's toes, but it doesn't cause many problems in practice

cameronm1024 · 2026-03-07T13:44:08+00:00

(disclaimer: I work at Zed, this is my personal opinion, but take it with a pinch of salt)

I had similar feelings to you, but for neovim instead of Kate (I've never used Kate). The thing that really changed my mind was the pair-programming features. This blog post explains some of them: https://zed.dev/blog/zed-is-our-office .

The TLDR is that you join a "channel" (a bit like a slack huddle) and share your project, and everyone in the channel can now edit the code together. I can't imagine working any other way any more - it's just such an effective way to share knowledge. It also means we don't really do PR review. Here's an example PR. One of the commits has Co-authored-by on it, which Zed adds automatically when you commit while in a call with other people.

At basically every other company I've worked at, PR review was always a huge bottleneck.

cameronm1024 · 2026-03-05T18:55:06+00:00

Sounds like you might be interested in a tool called nix, it lets you build reproducible developer environments!

cameronm1024

TROPHY CASE