d1l

If you took the findings seriously why didn’t you take the outrageous claims you were making in your own copy seriously? Why couldn’t you provide cogent analysis of these issues during the process? How did you hack up your db so bad in the first place?! This thing looks so bad bro I can’t help but think this kind of assertion only adds fuel to the fire.

> we're working on benchmarking now as well.

But you already said you were 1000x faster than Postgres??

Bro you've got to be kidding. pre-release builds? Aphyr directly addresses this in this analysis. Furthermore, given the absolutely ridiculous nature of some of these bugs, and the low confidence exhibited by the authors in the fixes, how can anyone assume that suddenly things are correct? The database was so janky that it sounds like most of the time was spent on basic bugs that a decent set of unit-tests would've caught. Who knows what wasn't uncovered because the db was so broken to begin with?

I mean did you see the "primary key equality" thing? Holy shit.

Jesus... How the fuck is this even on the frontpage?

The main difficulty I see in these "RETVRN TO SOVL" things is not the window-manager or desktop itself but the UI toolkits for the applications. GTK2 had so many excellent themes. Now GTK or libadwaita seem designed to resist themes and introduce constant breaking of selectors or widgets or whatnot. I believe they griefed the themers into just giving up. I have less knowledge about Qt, but I assume it's probably the better pick these days.

io2 has lower latency than gp3, and better durability. We switched workloads off gp3, didn’t even need to provision crazy iops. It had a cascading effect of calming down.

It performs well in the domains we’ve implemented it. Cheap, fast, good enough, multimodal. Its a workhorse and it strikes a nice balance. I’m open to the suggestion that I’m just winging it here and happened to get lucky with a model whose training fit our usage, which is boringly unspecific.

Thx I’m digging into it but am somewhat comforted not to be alone in this. Turning up the level helps some but then we lose the speed. I don’t know that we’ll switch to 5.5 and may shop a different provider.

Anecdotally we ran sonnet 4.6 for our more complex stuff and sonnet 5 was a LOT worse. 5.5 seems to have fixed it and we cut over our customer workloads. It’s strange, really.

At work we use haiku 4.5 for a handful of latency sensitive tasks that are fairly simple. It performs well. Just started testing 5.5 as I’ve been anticipating a nice improvement since it was teased. Results so far are trash. Prompt leakage even. And it’s slower. I guess it’s cheap but I think they got the balance wrong on this.

I think Richard Hipp has quipped “if you think you can build a better SQLite by god you’re welcome to try!”

Post is slop but I was on a call this morning with our go-getter sales guy (he’s calling himself a gtm engineer now) where he talked about alternately buying Reddit comments and going and placing flyers on car windshields himself at offices of potential customers. Our CEO was enthusiastic.

Don’t take AI so damn seriously (rule 63)

We ran EBS for years. Finally the costs became ridiculous and we moved our entire dataset to S3. We’re saving 20k/month. There’s just no beating the price.