This. I tried Zed for an entire month, but this "search thing" drove me nuts. It is also slow. If you work in a large project search is absolutely essential. Too bad.. Back to Visual Studio Code.
I think VSCode use ripgrep and Zed has its own ripgrep-like search. Zed likely still do more work per match due to the multibuffer. A normal nested tree-based result should be faster.
I think multibuffer can be good in edit/renaming use cases, but it's very annoying for fast lookups/navigation across different files (as mentioned elsewhere).
DeepInfra, as far as I'm aware, doesn't log your prompts and doesn't retain them in most cases, except "debugging purposes". As their per their privacy policy[1]:
"We understand that the inputs you provide to our API and the outputs it generates may contain your Personal Information. We will not store, sell, or train using this data unless we have your explicit consent. We might sometimes store, for a limited period of time, the inputs and outputs to API calls for debugging purposes."
They're not EU-based, though. And I'm not sure how "private" their inference actually is. The throughput is also not the best everywhere, sometimes it can be really slow (although right now both DeepSeek-V4 models seem to be doing fine). However, they have a good pricing, probably on of the best on the market.
I'm not affiliated with them in any way, but when I want to test (I'm not a power user of LLMs, chatbots and agents, not at all; I'm doing it just out of the curiosity) something that is too big for my local hardware, DeepInfra is usually being my go-to provider.
Fascinated, a bummer that DeepSeek does not offer a DPA or opt-out for training. This renders it unusable for my use cases unfortunately. At least z.ai GLM has a somewhat DPA in Singapore.
"Not great" is quite an understatement from a European perspective.
We're talking about a state-issued digital identity system, the European equivalent of your ID card, that cannot function without accounts at two US corporations. That's not a UX limitation. That's a structural dependency on foreign infrastructure for core state sovereignty.
The concerns aren't abstract.
The US has a documented history of mass surveillance programs (PRISM, XKeyscore) that directly targeted European citizens and governments.
Both Apple and Google operate under US jurisdiction, which means CLOUD Act requests, national security letters, and executive pressure are all legal avenues for US government access.
PlayIntegrity is explicitly described in your own architecture docs as a black box: "we do not know what they are actually doing in their backend." A critical security component of a state identity system, and you don't know what it does. That's not an engineering trade-off, that's an accountability gap.
GrapheneOS being "on the list" is not reassuring. It means the system launches in a state where European citizens who have actively chosen to reduce their dependence on US Big Tech are excluded from their own national digital identity infrastructure.
The EU passed GDPR to establish digital sovereignty. It's building eIDAS to establish identity sovereignty. Baking in a hard dependency on Google and Apple at the attestation layer undermines both, by design, at launch.
This is really cool. But showing Fahrenheit, despite everything else is perfectly localized, for my home town Hamburg in Germany, is somewhat useless. Guys from the US, we use Celcius here! :-P
Ah, nice, thank you very much. But it is impossible to reach the countdown page once you are in. So it is almost impossible to make the switch, because you notice the Fahrenheit thing only if it is too late. And it looses the setting after a reload..
Which community? Organic traffic to your GitHub exclusively coming from external references and links. There is no reason the same isn't working with Codeberg. If you link to Codeberg instead of GitHub it still works the same.
reply