Yes, Zed was first harness where you could seriously use local models. The issue is more about not having to check so many options to make sure it's all local. You can set up local model for chat but your auto completions will still be sending your code remotely.
VPNs are essential tools against government persecution. Linking identity to a VPN session under any guise (age verification or otherwise) is something out of the playbook of dictatorial states.
I've tried it out with Claude Code on my existing codebase and it seemed to hold its weight (despite being the 2-bit quant). Takes minutes on prompt processing, the actual edits are reasonably quick at above 20 tks.
The good: It succeeded with discovering, applying edits and writing a test for a small task I gave it.
The bad: It could not address a small nitpick I had.
The ugly: It hallucinated a conversation about "The Duck" that I had with it simultaneously while trying to solve another problem. I can only imagine it's one of examples in the initial Claude Code prompt:
--cut--
However, the user's query is "Can you track these 3 videos here?" which seems unrelated. Perhaps the user is asking if I can track the progress of three videos they are working on?
Let me re-read the user's message. The user said "Source Code" and "The Agent" and "The Duck", it could be video titles. And they are asking if I can track these 3 videos.
?? That doesn't make sense in the context. Could there be two different conversations?
--cut--
Exactly my thinking. The same reason why capitalizing and putting the word NEVER in asterisks makes the model more obedient. Or repeating twice. For whatever reason, it just works.
I've been using the editor since the early days and have always been a fan of its visual look and feel, so I was pretty happy to see its UI library open sourced.
I wish GPUI could become the go-to Rust UI library and not just an editor backend.
For that, a couple of changes would be highly desirable: being able to switch the GPU backend from Metal to wgpu (so it could be mixed with vello, for instance), and the ability to integrate into an existing event loop like egui allows you to. If this were easy to do, I would switch from egui in a heartbeat.
I took a look at gpui-component a while ago when assessing GPUI for a project I was working on. IANAL but was dissuaded because it's almost certainly not compliant with the Zed license--gpui-component "borrows" gpui code patterns lifted straight from the main zed repo, which therefore must be AGPL/GPL (unlike the gpui-only which is Apache IIRC). Caveat emptor (caveat user?).
I'm beating a dead horse here but the challenge is a11y. Chromium wrappers get a11y for free; bespoke UI frameworks must implement accesskit (or something) which is a lot of work and something that (imo sadly) many small teams decide is not worth the investment.
It looks like their approach could nicely solve a problem that's shared by almost every new GUI toolkit I've tried: text looks terrible, or at least out of place when surrounded by applications built with the desktop's native toolkit.
Pretty neat and fun to browse. Definitely works in more than the 50 cities advertised. I am curious why it seems to cover some areas but not other? For example, Yerevan in Armenia is not covered, but a ton of smaller towns to the south of it are in.
Also, it may be just a matter of getting used to, but I found the color of the heatmap to be a bit misleading. When you switch to a specific activity - for example, night life, the high concentration areas are in red, while that color means low concentration when on the Liveability tab.
Thanks, I looked at these colors for so long that they "appear" normal for me. Some are about "perception", night life is not necessarily good when you want to live in the place but is fun when you come for visiting ("activity"). However, I admit that this is not clear and needs work.
The coverage is larger part of Europe, gaps are present where there are no data points, where OSM coverage is practically zero. Aremenia looks like it's on a cut off border of OSM Europe file that's the source of everything here, only points close to the border are available.
I was still using Skype to talk with my parents when they pulled the plug on it, too. Obviously (and unlucky for Microsoft), that conversation never moved to Teams. Curious how many users they lost with that move.
Good work on the polished design, it does seem to blend in with the native interface. Did you need to use any private APIs to position or capture the previews?
Personally I hide my dock to reclaim extra space. One app I wish existed is an endless scrollable desktop to plop windows on, in the same manner that Vision Pro does it but without the VR. However, I think that would be hard to impossible to implement with what the native window manager lets you do.
Thank you! I'd definitely be interested in giving something like that down the line, but I think that might be its own project haha. The one private API is _AXUIElementGetWindow to map AX elements to window IDs.
