1) Their LLM integration needs to be at the quality of Cursor and VSCode to pull people away from those
2) Reduced friction to move over (keyboard shortcuts, common plugins, etc)
I think the Zed team is perfectly capable of winning. The bigger risk would be them trying to tackle fancy stuff before making sure the basics are good enough to get developers to switch.
They need to build up a deep understanding of why folks are sticking to Cursor/VSCode and not swapping over.
P.S. I would love for Zed to win in the market because I'm sick of slow software and it's refreshing to finally see an intense focus on performance.
Your notes are still in markdown.
The UX of that app is actually "ok". While it is a wrapper around their mobile site it works well enough.
I just threw up in my mouth when I read this. I've never used this language so maybe my experience doesn't apply here but I'm imagining all the different security implications that ive seen arise from failing to check error codes.
This is a common misunderstanding because unfortunately the slogan is frequently misinterpreted.
If they just mean "processes should be restartable" then that sounds way more reasonable. Similar idea to this but less fancy: https://flawless.dev/
It's a pretty terrible slogan if it makes your language sound worse than it actually is.
For example, imagine you're working with a 3rd party API and, according to the documentation, it is supposed to return responses in a certain format. What if suddenly that API stops working? Or what if the format changes?
You could write code to handle that "what if" scenario, but then trying to handle every hypothetical your code becomes bloated, more complicated, and hard to understand.
So in these cases, you accept that the system will crash. But to ensure reliability, you don't want to bring down the whole system. So there are primitives that let you control the blast radius of the crash if something unexpected happens.
Let it crash does not mean you skip validating user input. Those are issues that you expect to happen. You handle those just as you would in any programming language.
I've been coding for 15 years but I find I'm able to learn new languages and concepts faster by asking questions to ChatGPT.
It takes discipline. I have to turn off cursor tab when doing coding exercises. I have to take the time to ask questions and follow-up questions.
But yes I worry it's too easy to use AI as a crutch
This will also allow the wider community to innovate rather than waiting on standards bodies to decide what the think is best.
Bad PM: I need to make sure I am not wasting time building the wrong thing. So I am forced to be "distracted" and play the role of a PM.
Good PM: I need to stay focused building. The PM has already done a great job figuring out what needs to get built. They have given me a good mental model of how the customer thinks.
Sure some facetime with customers is good but the article has a simplistic conclusion.