Yeah, first thing I did was change all the locations back. I really dislike the automatic layout change they pushed.
Also, watching the change notes, most effort seems to be focused on agents this days, which is a bit worrying. I love Zed because it's great editor that also knows a bit about agents; I don't want it to continue pivoting towards pushing agent management deeper and deeper into the experience.
I don't have any problem with them investing heavily in this, I just think they need to be smart about the UX and not let the business VC drive the experience this much. Pivoting from text editor to agent manager is a bad choice IMO, when it can easily be both and help people onboard from editor to agentic workflows.
Personally, I still pay Zed because I think they’re doing great foundational work. However I’ve now almost entirely migrated to helix for editing needs.
> I don't want it to continue pivoting towards pushing agent management deeper and deeper into the experience.
AI and agent tooling is the only way this VC-backed company is going to make any money. Nobody is going to pay for a text editor, so they've had no choice but to enshitify it by chasing AI features for the last year+.
We don't have this kind of tooling built up, but we've been using Linear as a source of truth alongside a human written prompt adding context. It's worked really well for both feature development and bug hunting, and helps keep us honest with tickets (good LLM context is still good human context) as well as maintain some level of consistency between LLM passes on the same issue.
100% on using linear as the source of truth! We went a bit further and just use Linear as the prompt. So there isn't a human written one adding context that lives elsewhere
This has been great for me too. Every feature starts and completes with /gh-issue <issue number>.
Every issue is created with /spec and a conversation with a human. Once the spec is materialized as an issue it’s sufficient for an agent to implement.
It makes me think, what `gh` features don't generate some activity in the github API that could as easily guide feature development without adding extra telemetry?
I'm not sure how they are related. USB-C was not really a technical challenge or had trade-offs. I'm not a hardware engineer but from what I've read, having an easily replaceable battery would degrade the water resistance of the phone.
Don't get me wrong, there were plenty of people in the more toxic parts of Apple's fanbase decrying USB-C for appearing too fragile, for being forced on them, for having a confusing set of standards (that last one is a fair point).
But I think, among Apple fans, USB-C has generally been a point of 'pride' for the past decade. Designed by Apple, put in a laptop first by Apple, best $10 USB-C-to-3.5mm DAC by Apple, etc.
Whether correct or not, I think Apple fans anticipate more severe tradeoff ramifications with a replacable battery. I think they're different things. (I don't think it's impossible though- the Fairphone has IP 55, I bet Apple can improve on that).
Lightning is a superior physical design to USB-C (can't speak to the electrical part). Much like every major tech battle in history, however [1], the worse solution won because of ubiquity. I'm not particularly thrilled because I've had a USB-C connector irretrievably break off in a port once on a laptop but I'll make that trade for being able to use a single cable for all of my devices.
- Not an "Apple Faithful"
[1] VHS vs Beta, Doom vs Marathon, Zergling vs human, etc
I've never had trouble with usb-c, but have had lightning connectors short out and burn one of the leads, or stop working from dust. Not sure I'd say one is better than the other, but individual experience can really vary on these kind of things. Tough to say one is clearly better imo.
Yeah it seems to be really up to individual experience. I had two apple-made lightning cables that shorted and burned out the leads on the male end of the connector.
Get it approved in a lot of large markets? Deal with ongoing supply issues as suppliers change and you need to maintain your product? Market it? I could keep going on, but making a prototype is the easy part, making a sustaining business out of it is the hard part.
This doesn't answer your question, but Aerospace (tiling WM) has been good for me to not use spaces. I don't mind spaces in theory, but the slow animation, for whatever reason, just really irks me.
Also, watching the change notes, most effort seems to be focused on agents this days, which is a bit worrying. I love Zed because it's great editor that also knows a bit about agents; I don't want it to continue pivoting towards pushing agent management deeper and deeper into the experience.
reply