If your WFH desk setup doesn't cost more than a used Honda Civic, you aren't serious about your pipeline.
My ergonomic chair is built from the salvaged suspension of a 2019 Tesla Model S.
My primary monitor is a converted IMAX screen I bought from a bankrupt theater in Oakland.
When I drag a cell in Google Sheets, I physically have to rotate my entire torso. I burn 400 active calories a day just searching for the Slack icon.
Stop complaining about back pain and optimize your environment.
@monolisafont@dinsley@jahirfiquitiva I figured that out by checking the purchase page as an anonymous user. I’ve already purchased the upgrade. Thanks again! You’re the best!
We open-sourced Zed in January 2024.
Since then, the repo has amassed over 84k ⭐s and receives more PRs than we can honestly keep up with.
The Community Champions program is how we recognize and track work from contributors we've come to know and enjoy working with.
https://t.co/onba9GFaXe
Unfortunately, this issue broke the Ruby extension, which relies on the correct Ruby version. Probably the best approach here is to remove the automatic installation of Ruby servers and rely entirely on the project gemset. The downside is that Ruby LSP is usually not part of it.
Meh, found a nasty macOS PATH issue in @zeddotdev
Zed can correctly capture a project env, but extension commands like `ruby --version` may still launch the wrong binary.
Why: macOS posix_spawnp("ruby", ..., envp) resolves ruby using Zed’s own process PATH, not the PATH passed to the child (I think). https://t.co/HKez5naVJu
Terminal Threads are live in Zed v1.3.5!
You can now run claude, amp, pi, or any terminal-based workflow as a managed thread in the Threads Sidebar, right next to your other agent threads.
Meh, found a nasty macOS PATH issue in @zeddotdev
Zed can correctly capture a project env, but extension commands like `ruby --version` may still launch the wrong binary.
Why: macOS posix_spawnp("ruby", ..., envp) resolves ruby using Zed’s own process PATH, not the PATH passed to the child (I think). https://t.co/HKez5naVJu
@juliknl Exactly. I try to stay away from commenting on any GitLab‑related tweets because I'm an employee, but Ruby perf is not in the top 10 (or even 20) challenges at GitLab. Even humorous tweets like "let’s just create our own GitHub" don't make much sense, IMHO.