Hacker Newsnew | past | comments | ask | show | jobs | submit | penberg's commentslogin

1. I am on Claude Code Ultra plan, mostly for Fable, but I also burn through quite a bit of tokens.

2. I am experimenting with hybrid setup with Fable and Qwen3.8-27B locally.

3. I use Claude Code, some Codex, and for local development, I built my own harness (https://github.com/dwim-sh/dwim) because I had hard time getting Qwen to stop overthinking and staying out of (infinite) thinking loops.

4. I built one for myself (https://github.com/splay-sh/splay) because there were no Linux orchestrators around when I needed one. Now I am also using Rex, which seems like a keeper.


We're aware of your woes with ClickBench. The first time you added it I even explicitly told you that it was way too early to even try that. The attempt you did recently was fair, but it's all in the ingestion before the benchmark, and does not show up anywhere, so we ended up spending time on this instead:

https://turso.tech/blog/turso-0.8.0

In any case, this is on our radar and we do intend to improve it but not the highest priority right now.


Why do you think f311a is alexey?


I also want to know that; it's a weird accusation.

Penberg's earlier reply said f311a was (paraphrased) "talking crap on the internet" but it looks like they've edited out the cussing.


I'm not affiliated in any way.


There's a reference manual in Git repository, but probably not what you're looking for. Will add something.


Yup, Ghostty build requirement.


You're not wrong about VC-funded database arc, but what history are you even talking about?

I am sure you understand that I have absolutely nothing to do with Scylla's licensing. I have not worked there for four years nor was I ever in a position there that I would even had that opportunity to influence such decisions.

I am also sure you understand that Scylla's development model was completely different: they had AGPL license and contributors had to sign a CLA, which is why they were able to relicense in the first place. Turso is MIT licensed and there's no barrier to contributing and, therefore, already a much bigger contributor base.

I fully understand the scepticism, but you're mistaken about the open source history of Turso's founders.


The project is MIT licensed with a growing community of contributors. It does not even matter how long the company lives, all that matters is that some of the core contributors live.


The actual reality is that I personally started the project because its synchronous architecture is holding back performance. You can read all about it in https://penberg.org/papers/penberg-edgesys24.pdf. The design is literally the next evolution of SQLite's architecture.


Yeah… Attempting to integrate MVCC and then doing vector search gave enough perspective to do this!


Remember, that argument to `findOne()` is an arrow function. You need a compiler to turn it into a efficient, deferred query; otherwise you need to _evaluate_ the function at runtime.


This is the disconnect I've found in my self-taught compiler education journey. Every time I try to tackle this topic, I get bogged down by parsers and lexers. I already have that structure.

Users.find(x => x.name == "Bob").

My programming language has done that for me. What's the next phase? What data structures do I need to maintain to construct these DSLs? How do I optimize them?

I can fight my way through this but I wish I just had the theory and making this kind of stuff easier. It just comes up so often in the problems that I solve and I'd like to reach for this tool more often.


Perhaps you are looking for macros? Rust had a substantial macro system while being low-level enough to fit into most architectures. I haven’t implemented a macro but I’ve used many. Have you looked there?


As I was writing my comment, I think maybe I should start with DSL, but this isn't conclusive. Spark, Scalding, LINQ, RxJava, even Slick are examples of the types of DSLs I'd like to understand how to construct. They're essentially compilers.

Looking at the code for these technologies it's incredible how complex it is to implement the nice DSL that they expose. How much of that is accidental complexity?


So the innovation here is instead of doing "User.findOne({name: "Glauber Costa", age: {superiorOrEqual: 40}});" you do what's in my previous comment?


I don't know if SQLite + Raft is going to be the next Postgres, but it's certainly an interesting solution for a variety of use cases where you don't need your data _partitioned_ on multiple machines (but still want it to be replicated for availability and fault tolerance).

As others point out in this thread, there's already rqlite for Go, sqlite for C, and now we've open sourced our work on bringing SQLite and Raft to Rust: https://glaubercosta-11125.medium.com/winds-of-change-in-web...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: