kjuulh
kjuulh on Hacker News
I am not sure how the IPO is going to go.
Tokens themselves are already a bit of a commodity, and the margins are gonna be fierce on these as there is not a whole lot of lock in.
Would Anthropic and OpenAI position themselves using their extra tools, their ai agents, presentations, docs. Are they nice; yes. However, that doesn't make a 2T company. It reminds me a bit of Dropbox, a truly great product, however, they're differentiation is simply not there. I think the momentum is there for the IPO to go decent, but it feels like the company is on such unstable ground that the fallout could be catastrophic.
I know, but if something is split up and stored in a vault somewhere the likely hood of a vulnerability napping the wallet falls. Defence in depth and risk analysis.
The name of the hacker is a bit on the nose lol.
I can't understand how you could let this happen. If they stored everything in fat hot wallets, that just seems like a recipe for disaster. Especially with the "features" of crypto. Math for the most part, doesn't care about your feelings, or money for that matter.
It might actually have been Libra. It was part of the whole get away from MS thing.
My mom still uses OpenOffice at her job (municipality), and honestly they haven't really felt a huge difference, they still get their work done like before, but heck there were some training to do as they were switching. I suspect at this point they would need the same training just to get back to word etc.
I think it is an interesting question of what makes someone effective at using AI, which changes in what context you're in.
If you're at a small start-up and effective ai user looks different than one at an enterprise company, or hyper-scaler with infinite resources.
For me being effective at using AI, is as much the harness and workflows I built up alongside the services to support it, good ci, good tests, deployment pipelines and more. This allows us to streamline development and let the AI agents work much more autonomously, and in some cases even do automatic development and triaging.
Does that put me in 0.01% of spend, nope, but it makes me effective at my company and for personal development.
That looked like a really fun project, and quite the persistence you've got to actually stick with it for such a long time. I might have to give it a try when i get home.
Docker and containers are amazing. They definitely have their caveats, whether that is security, bloat, you name it. But the fact that I can produce an artifact and have it run pretty much anywhere without much overhead is amazing.
For me firecracker has mostly taken over most of my hosting needs, as i can actually take a docker image and unpack it into a firecracker image, and still have a slim process (vm), with great performance, though with a bit extra bloat, but now also have a secure workload that I've got better control over.
Docker and docker compose however, is still the core of my development workflow, and has been for many years, in my eyes, docker compose is the best we've got for simple composition of various services.
If you didn't know of an embargo, and you posted about it, I can't see how you were wrong.
This getting out before the fixes were published sucked, but they would've sucked anyways.
This getting out at least allowed me to inform some of my previous colleagues that they had services that were affected and they were able to shut them down until we had a proper fix available.
I feel like in the beginning it was a way to highlight the fidelity of the models as they struggled to produce good latex and svgs figures. But especially now with the iterative loops that is no longer such a good benchmark. And honestly these pelicans are pretty much the same, so yeah it feels totally benchmaxxed.
We ran actions runners ourselves in kubernetes at previous jobs, and at least back then, a lot of the errors came from the github services simply not telling the runners to handle jobs. So in general it didn't matter how much compute you had, they never got scheduled jobs.
It feels more like volume than speed. AI has actually improved our speed quite a bit, as it is fairly easy to just get AI to make it fast. Will vibe coders do this, probably not. That said our volume is probably 10-30x in commits and ci jobs as we had pre-march.
Great read. I always find these turn a feature of a computer into a database an interesting read/idea. It certainly has upside, and downsides. For example having an entire filesystem as a sqlite database etc, or in this case an executable. It would be nice to have a structured way of talking to our utilities, rather than interpreting various commands as json through a few layers of tools to then get the output in a common format. That said I'd probably rather have a split up tool-set, than everything having to be in a single database for it to interoperate.
Reading this port-mortem / plan shocks me, this doesn't look like a service that has been serving high-throughput services for more than a decade. In fact it is almost like they've barely started. It seems the solution has been capacity, capacity rather than architectural or data changes.
> Our next milestone is an architecture that scales read capacity linearly with the number of readers, enabling unlimited read operations
How do you not have read-replicas / read caches at this scale yet? Which is what I am reading from this statement. You can of course get really far with sharding and whatnot. But at some point it might become worth it to engineer your data into a model that scales better.
Great article. I find that I learn something every time I read a post about linux kernel work.
I guess an LRU with priority would handle VRAM for games pretty decently without going getting too application specific.
What about VRAM to Disk specifically NVME, would direct to disk be feasible for large workloads, I know it is used for streaming in assets directly via. PCIE, but i wonder how the performance would be on compute workloads running with NVME as a swap for GPU VRAM.
I've built my own workflow for using agents on git, as i now often have to do changes across repositories, or in the same repository for different tasks. I could use worktrees, but I'd rather invert it, give agents the ability to have a workspace, that they pull repositories into, create branches as they want, commit on main it doesn't matter. the agents don't bother each other, and when i finally have to merge, conflicts are either resolved, or it is just smooth sailing.
The tool is called gitnow. it is honestly quite simple, just create a project, add the repositories you want and get to building. I've found having another claude chat or whatever use the tool to great success coupled with zellij, but could also be zed, tmux or whatever.
Secondly it also pretty much solves the problem of the agent dumping memory files everywhere, they now basically have a scratch space that is theirs, where they can keep their tasks, and just update the repositories as needed.
Use gn the shell after eval if you use it, it will actually invoke cd, instead of creating a subshell.
https://github.com/kjuulh/gitnow
Love clickhouse it is just super performant. I've had to tweak a few queries for performance here and there but it has been more than stellar. I'd initially set up a real time pipeline ingest for us to handle our larger incremental ingests when i started (used redshift in the past, very expensive and quite slow in comparison), it has been unnecessary so far, as clickhouse has just been able to chew through tons of data and large transformations without breaking a sweat.
Only issue i had was that the default configuration had some quite heavy handed tracing turned on which tanked performance on the relatively little machine we had for it, it has since been scaled up and is the core of our data stack.
I can't recommend clickhouse enough. If you were truly large I'd probably choose something else, but as long as we're staying on a few nodes it is manageable complexity and we enjoy using it.
Interesting Mistral sort of knew something about me, both gpt and deepseek produced the same answer more or less. I wonder why xD, only gemini knew my online handle mostly github and rust which is interesting.
I tried out PgDog a while ago, but couldn't find a good way of handling the config except for having this users / pgdog toml file, which makes it a bit awkward to handle in kubernetes where we often do multi-tenancy in postgres - or rather having many databases on the same instance(s), and have them come and go at will.
Also had an issue with it because it cached authentication requests when doing passthrough it seems, I'd changed the roles password, but it kept using the old one, which was no bueno ;).
PgDog seems to make more sense when you really care about a few databases that need massive scale, rather than a simple proxy in front of postgres. I'll keep following the development though, it is much needed in this space, postgres can use all the investment it can get to get it past the single machine scale that it excels at currently.
Rug-pulls, security incidents, lost passwords, I also don't know if they've kept my passwords behind when i deleted my accounts. The risk of them having them is too high, so i had to swap all of them.
At this point it is too high of a risk to store my password elsewhere. I've been screwed over by dashlane, lastpass, potentially bitwarden now, I am with 1password now, but I've had my passwords in all these places, and I've had to change them each time, probably missing a few.
I like 1password, it is by far the highest quality product I've used in this category. I moved from BitWarden back then because their browser integration was quite poor.
I think I'll move to something custom, or a selfhosted keepass server, with the rugpulls, incidents, and whatnot, it is becoming too high of a risk.
When I started my professional work, Visual Studio was the recommended editor where I was, it was terrible, the Laptops we had were incredibly shit. My phone scored better on benchmarks than it, as such Visual Studio was not a good experience, I convinced my boss to let us try Rider, it was incredible, I no longer had to sit for 10s of minutes for a project to load, it was relatively snappy. My next job I started using Goland and was quite happy with it, at this point we had more high-power macs, but still great editor. I then moved on to Neovim, and then Helix in search of better ergonomics. I now have gone full circle and pretty much develop on a laptop of the same caliper as when i started working, however, because of a more lightweight editor helix, it doesn't feel like a slog, I wished I'd gotten it recommended back then, or been curious enough to give it a try, I'd saved myself many coffee breaks, and pain.
So if anyone is out there sitting in a similar position, give it a shot, you can get a better editor experience, whether you build it yourself with emacs, neovim, or use a more curated approach like helix, or zed for that matter. I mix and match Helix now with Claude Code, and it works really well. I don't want a single AI feature in my editor, only navigation, and auto complete. I'll have my AI on the side thank you ;)
I am using docker-compose everywhere. I really enjoy using it. I have a single thing that is annoying for normal production deployments, and that is that it isn't super easy to have a rolling deployment, I just need two replicas for zero downtime deployment, and I don't really want docker swarm. I think it is the networking which breaks at that point, and you have to have a more involved setup, and at that point I'd just use kubernetes, as I know how that works.
Could i survive with 10 seconds of downtime, probably, but I'd really like if I could avoid it.
Had this happen to me once, though totally my own fault. Was brewing kombucha, and left it out in the bottles a little too long before burping.
Me standing there, kombucha and peach slices pulverized against the cap, kombucha leaving a large mark on the ceiling it all happened so fast, glad I was wearing my glasses.
No injuries except my pride, but it did take some hours to clean up.
I wouldn't do it in a thermos, but I guess those are mostly accidents?
I am conflicted on tuis they are nice, convenient and I dig the aestetic. But they're often not composeable. So even if they're there they dont feel native to the terminal. It is just an app in the terminal and that is okay, but you lose some of the terminal magic
On the other hands, having half the packages depend on packages such as serde, syn, procmacro2 might not be such a good idea. First of all it is annoying when creating new projects to have to move over table stakes. Second, it is a security nightmare. most of rust could be vulnerable if dtolnay decided to go rogue.
It is not that everything should go into the stdlib, but having syn, procmacro and serde would be a good start imo. And like golang having a native http stack would be really awesome, every time you have to do any HTTP, you end up pulling in some c-based crypto lib, which can really mess up your day when you want to cross-compile. With golang it mostly just works.
It isn't really in the flavor of rust to do, so I don't think it is going to happen, but it is nice when building services, that you can avoid most dependencies.
Anthropic should calm down, I get that they're trying to either build a moat, or simply curb what is essentially subsidized tokens. It is technically true that when you've got a claude code subscription you pay for the product with its terms, and those terms doesn't include you grabbing the token and using it for another application. They're also trying to build a competitor to openclaw so it makes sense they're trying to crush it. But it feels like such a feeble moat, that it looks silly. Claude Code is nice, but it is not that nice.