sorcercode
Joined 15 years ago
Karma
306
Submissions
111
Member since
Jul 26
https://kau.sh
View on Hacker NewsRecent submissions
Comment · 6 months ago
self-published benchmark in README claims a 16% lower workflow token cost than Vercel's agent-browser on a Google Flights task (plus a much smaller install footprint).
Comment · 8 months ago
These are all evolving technologies and it's pretty evident that the big AI labs are trying different things to see what sticks. Some of it does and they keep evolving it.
The reason MCPs are so powerful are less a technological advantage over other tools and more how ridiculously easy they are to install and use.
Also given it's an official standard now (AAIF), it's easy for sharing across differently agent harnesses and tools.
Those are the two main reasons imho, they are still a mainstay.
If you'll allow some shameless plugs, my co-host and I talk about it in our podcast:
Comment · 10 months ago
Not sure how you would define successful though. I built a Firefox addon almost entirely through vibe coding and I know at least 5 other random souls on the Internet who have used and thanked me for it. But it is by no stretch, if popularity or how much money it makes, are the measures.
I was trying to test the theory if it's even possible to release something production grade with vibe coding. Wrote about the experience here https://kau.sh/blog/container-traffic-control/
Comment · 10 months ago
Might I also suggest the Firefox addon "Container Traffic Control" - A Firefox addon I built to make it even easier to use Containers
https://addons.mozilla.org/en-US/firefox/addon/ctc/
When you start to use Containers (feature the Author of the article talks about), you'll start to want a little more control in how the containers open especially for sites that you allow on more than one container
Source came be found here: https://github.com/kaushikgopal/ff-container-traffic-control
Comment · 10 months ago
i think the genie is out of the box; but i stand with your sentiment!
Comment · 10 months ago
Most AI generated text doesn't seem to have spaces around the em dashes. I've been using that as a subtle distinguishing marker; as both forms are considered grammatically correct.
tldr: use spaces around em dashes
Comment · 10 months ago
having spent a lot of time on finding the right monospace fonts, one of the things i've noticed, that's particularly important in the context of coding is a visual symmetry.
some fonts individually have beautiful glyps or characters but when you preview them with blocks and blocks of code, there's a quirkiness that throws of that symmetry.
I'll give a few examples:
- Mono Lisa font https://www.monolisa.dev/ (truly gorgeous font)
- Recursive https://www.recursive.design/ (particularly note the casual axis)
I bring this up because Google Sans Code, is super quirky; preview a few characters individually and they look good; put it all together in real code, and it's just not as smooth visually.
Comment · 10 months ago
i feel your pain my friend. i really do.
i don't have your skills of actually customizing or changing glyphs in fonts directly but i've customized and used scripts to fix glyph characters available as open type features. I've done this for fonts like:
- [Iosevka](https://kau.sh/blog/build-iosevka-font-mac-os/)
- [IBM Plex Mono](https://kau.sh/blog/freeze-alt-char-open-type-font/)
- [Jetbrains Mono](https://github.com/kaushikgopal/JetBrainsMono-KG) (yes, plenty of customization there)
- [Recursive](https://github.com/kaushikgopal/recursive-code-config)
it really is a sickness. a terrible sickness, if you care deeply about fonts. I know you don't care specifically about recommendations, but inevitably i've found myself gravitating to these fonts:
1. Berkeley Mono (paid)
2. SF Mono (walled)
3. Recursive (truly open and legible)
4. Commit Mono
I love the above fonts, but there's a few characters or quirks that drive me bananas on certain days, so inevitably find myself switching between them.
Comment · 10 months ago
this makes sense and as usual great eye by Simon. progressive disclosure is such a powerful concept, that every other tool is going to start adopting it. we've personally had such great results adopting it, especially for performing high quality large migrations.
I wrote about this but I'm certain that eventually commands, MCPs etc will fade out when skills is understood and picked up by everyone