Glauber Costa

Hi I am the author of [glommio](https://github.com/DataDog/glommio), a thread-per-core runtime for rust that recently got some attention. Prior to rust I was involved in the [Scylla](https://github.com/scylladb/scylla) C++ database, which also...

hello @fire ! I think this would be best stated as a Discussion (https://github.com/libsql/libsql/discussions) But in the mean time, what would you suggest?

In my mind, keeping compatibility with the file format is 110% crucial. Keeping compatibility with the existing APIs is 100% crucial (but adding new APIs should be fine, doing good...

I am willing to be convinced, but for me, the interesting aspect of "embedded" is that you add attach to your application through an API, versus going through some remote...

@losfair would love to get some testing / comments on this from you before we put it out of draft!

@losfair just to make sure to bring this to your attention, there's a PR open implementing a first RFC for this, would love to get your eyes on it!

The problem is that the semantics of the write system call are different than that. It says: >> Note that a **successful** write() may transfer fewer than count bytes. Such...

To my knowledge, I assume they are aligned, but we should assert. Asserting is bad, but it is less bad than silently breaking something. To be clear, for *async* writes,...

Yes, there's usually this policy, but because short writes are already present, the usual thing to do upon a short write is to try again. It is not unreasonable to...

This should not be at the `Source` level. This is a higher level API decision, breaking with what the OS provides should happen as high as possible. Because we ingest...