I saw this trending on github yesterday and tried it and liking it so far.
What I like:
- familiar tmux like key binding (configurable) interface
- comes with all the tmux advantages like detach, ssh etc
- mouse
- nice sidebar
I prefer to manage my worktrees manually with a super simple script.
They sold at the top. My entire TEAM was weaned off cursor in the last year. New setup - 50% of them do (Codex Desktop, Claude Desktop) + Zed for IDE and the other 50% use (claude code + codex cli) on cmux -- a ghostty based terminal that adds some bells and whistles, literally for notifications when claude is done.
IMHO, the codex desktop app is very powerful for development + testing given it can easily control the computer.
"Just use autoresearch and it will fix your app's memory leaks in an hour" is what I was nonchalantly told by someone who has never written a line of code ever.
I guess what I relate to the most is how dismissive people get about real software engineering work.
I may have skill issues, but I am yet to reach the level of autonomous engineering people tend to expect out of AI these days.
Congrats to the Zed! I've been using zed since their first launch on HN. They did not even have a search + replace function at that time! I now use zed all_the_time.
What is confusing to me, is as a business I would happily pay GitHub for many many features that I pay others for. Maybe MS thinks its just a billion here, billion there, but isn't it so easy to capture these?
1. faster more configureable action runtimes so I can get faster builds
2. usable merge queues because the github one is a joke
3. some reasonable CI management and workflow debugging features
Thank You. This is exactly why I read comments on HN before clicking on news. I am not looking for confirmation bias, I just trust people here more than the BBC.
No shade on these guys, looks like a cool tool and I'll try it. However, I find myself doing large majority of my git operations using a an agent[1] or a TUI [2], and I rarely open a git interface. I can get everything done straight from the terminal.
I guess I can overcome the "what if I cannot undo" anxiety.
Things that make an an OpenCode fanboy
1. OpenCode source code is even more awesome. I have learned so much from the way they have organized tools, agents, settings and prompts.
2. models.dev is an amazing free resource of LLM endpoints these guys have put together
3. OpenCode Zen almost always has a FREE coding model that you can use for all kinds of work. I recently used the free tier to organize and rename all my documents.
> File Explorer is one of the most used surfaces in Windows. Our first round of improvements will focus on a quicker launch experience, reduced flicker, smoother navigation and more reliable performance for everyday file tasks.
Really? it took "user feedback" for one of the world's best software companies to realize one of the most fundamental parts of the OS was broken?
I have been long on $MSFT for a while now, but my faith as an investor stands shook.
One of my buddies works in a company that makes very popular Text AI models. His words "Gemini's visual understanding AND output in best in class and we use it in production apps"
People are flooded by new projects and assume (rightly) that most are low-signal, so they don’t engage. Because there’s low engagement, new projects get even less visibility. That reinforces the belief that nothing interesting can be built anymore.
I ship earlier now (often free and open source) to learn faster, but it doesn’t change the attention dynamics much.
The bottleneck isn’t building. it’s distribution and who already has an audience. Now dont get me started on getting an audience. thats a whole different pain.
I was an on-prem maxi (if thats a thing) for a long time. I've run clusters that costed more than $5M, but these days I am a changed man. I start with PaaS like Vercel and work my way down to on-prem depending on how important and cost conscious that workload is.
Pains I faced running BIG clusters on-prem.
1. Supply chain Management -- everything from power supplies all the way to GPUs and storage has to be procured, shipped, disassembled and installed. You need labor pool and dedicated management.
2. Inventory Management -- You also need to manage inventory on hand for parts that WILL fail. You can expect 20% of your cluster to have some degree of issues on an ongoing basis
3. Networking and security -- You are on your own defending your network or have to pay a ton of money to vendors to come in and help you. Even with the simplest of storage clusters, we've had to deal with pretty sophisticated attacks.
When I ran massive clusters, I had a large team dealing with these. Obviously, with PaaS, you dont need anyone.
I prefer to manage my worktrees manually with a super simple script.