If the benchmarks are to be believed, and assuming ~0.93 recall is "good enough" for the use case, this vector DB is seriously fast: about 5x the queries/sec of OpenSearch and 19x Milvus.
NOTE: The script is broken, DO NOT ATTEMPT TO USE THE SCRIPT NOW. Attempting to run it may get your account flagged stopping you from trying face verification either temporarily or permanently, forcing you to use your ID.
Literally the opposite though, as being able to see what it reads allows you to tell it to ignore certain files when you see it read the wrong one, and adjust the claude.md file to ensure that it does not read incorrect files given a specific input.
Jokes about vibe-coded CLI aside, I think that's the issue for me, the defaults are being tailored to vibe coders. (and the general weirdness of trying to fix it with verbose mode)
I like that people who were afraid of CLIs perhaps are now warming up to them through tools like Claude Code but I don't think it means the interfaces should be simplified and dumbed down for them as the primary audience.
Sure you can press CTRL+O, but that's not realtime and you have to toggle between that and your current real time activity. Plus it's often laggy as hell.
Yeah, these all sound like complete non issues if you're actually... keeping your codebase clean and talking through design with Claude instead of just having it go wild.
I'm using it for converting all of the userspace bcachefs code to Rust right now, and it's going incredibly smoothly. The trick is just to think of it like a junior engineer - a smart, fast junior engineer, but lacking in experience and big picture thinking.
But if you were vibe coding and YOLOing before Claude, all those bad habits are catching up with you suuuuuuuuuuuper hard right now :)
As a SE with over 15 years' professional experience, I find myself pointing out dumb mistakes to even the best frontier models in my coding agents, to refine the ouput. A "coder" who is not doing this on the regular is only a tool of their tool.
(in my mental model, a "vibe coder" does not do this, or at least does not do it regularly)
Well, the term lacks clarity and a shift of meaning.
If you define "vibe-coders" as people who just write prompts and don't look at code - no, they ain't coders now.
But if you mean people who do LLM-assistet coding, but still read code (like all of those who are upset by this change) - then sure, they always have been coders.
I was curious about the scale of 1TiB of text. According to WolframAlpha, it's roughly 1.1 trillion characters, which breaks down to 180.2 billion words, 360.5 million pages, or 16.2 billion lines. In terms of professional typing speed, that's about 3800 years of continuous work.
So post-deduplication, I think it's a fair assessment that a significant portion of high-quality text could fit within 1TiB. Tho 'high-quality' is a pretty squishy and subjective term.
> it can read my text messages, including two-factor authentication codes. it can log into my bank. it has my calendar, my notion, my contacts. it can browse the web and take actions on my behalf. in theory, clawdbot could drain my bank account. this makes a lot of people uncomfortable (me included, even now).
...is just, idk, asinine to me on so many levels. Anything from a simple mix-up to a well-crafted prompt injection could easily fuck you into next Tuesday, if you're lucky. But admittedly, I do see the allure, and with the proper tooling, I can see a future where the rewards outweigh the risks.
Best case, Google DeepMind cracks AGI by letting agents learn for themselves inside simulated worlds. Worst case, they've invented the greatest, most expensive screensaver generator in human history.
Wayland+sway switch from x11+i3 is so simple and works so well.
Only minor annoying thing not working for me are right-click context menus on some applets like Blueman and Steam.
Nvidia's official drivers have supported Wayland quite well since the 550-series. If you haven't tried it in a few years, now is a great time to give it a spin.
My problems with Wayland are KDE specific. I tired it, but there where so many window management regressions and sometimes graphical glitches that I switched back. But that was under plasma 6.4. Have to try again now on 6.5 to see if these issues are fixed. If not I should write a bug report, I guess.
Also there needs to be an alternative for (or patch to) simplescreenrecorder that works under Wayland. I don't want use a complex thing like OBS to make a quick demo video to demonstrate something for a co-worker and stuff.
Didn't know Spectacle can do screen recordings now. Just tried it: The "New Recording" button seems to be broken. It does nothing. No error message on the terminal even. Maybe it only works under Wayland?
Personally I like Rust, but I'm against rewriting old well tested tools in Rust just because. There is this opinion out there that Rust devs rewrite everything for no good reason, but I only really saw that happening in coreutils and sudo. In the other cases that I heard of the rewrite wasn't from C/C++ (but e.g. from JavaScript and they need more speed) or they needed a rewrite anyway for different reasons (e.g. first working parallel style calculation in Firefox).
So I'm very skeptical of the coreutils rewrite. In the current state it's incomplete, slower (not optimized), and replacing all GPL code with MIT/BSD code also feels strange to me.
Worth mentioning that Bubblewrap[1] (bwrap) can remove most npm/node attack vectors or, at the very least, limit the damage from running arbitrary code during install/execution. Far from a silver bullet, and you'll want to combine it with a simple wrapper script to avoid dinking around with all its arguments, but it beats dealing with rootless Podman containers.
This looks really interesting, but it sounds like it's as complicated to setup as rootless Podman — which is to say not _that_ complicated. Anyone using this with Node or Deno successfully?
I always thought a screenshot of code was just an iPeople flex. Like, "look at my code, framed in this glassy macOS window with a $29.99 drop shadow." Kinda like how Nix or Arch users can't resist mentioning they use Nix or Arch. (btw i use arch)
reply