penberg

9 ms·

1.
by penberg 6mo ago
There's a reference manual in Git repository, but probably not what you're looking for. Will add something.
2.
by penberg 6mo ago
Yup, Ghostty build requirement.
3.
Show HN: A tool to manage a swarm of coding agents on Linux(github.com)
5 points by penberg 6mo ago|3 comments
4.
Repairing Programs with AI Agents(penberg.org)
3 points by penberg 6mo ago|0 comments
5.
Building AI agents with just bash and a filesystem in TypeScript(turso.tech)
2 points by penberg 9mo ago|0 comments
6.
AgentFS with FUSE: SQLite-backed agent state as a POSIX filesystem(turso.tech)
7 points by penberg 10mo ago|0 comments
7.
by penberg 1y ago
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 ev
8.
by penberg 1y ago
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.
9.
by penberg 1y ago
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
10.
by penberg 2y ago
Yeah… Attempting to integrate MVCC and then doing vector search gave enough perspective to do this!
11.
Show HN: Limbo – SQLite compatible, in-process OLTP database written in Rust(github.com)
10 points by penberg 2y ago|2 comments
12.
Approximate nearest neighbor search with DiskANN in libSQL(turso.tech)
3 points by penberg 2y ago|0 comments
13.
Building a better-sqlite3 compatible JavaScript package with Rust(blog.turso.tech)
2 points by penberg 3y ago|0 comments
14.
SQLite-based databases on the Postgres protocol? Yes we can(blog.chiselstrike.com)
2 points by penberg 4y ago|0 comments
15.
How ChiselStrike generates its TypeScript client API(blog.chiselstrike.com)
3 points by penberg 4y ago|0 comments
16.
Why middleware may not be the right abstraction for your data policies(blog.chiselstrike.com)
2 points by penberg 4y ago|0 comments
17.
Show HN: Viewstamped Replication for Rust(github.com)
2 points by penberg 4y ago|0 comments
18.
Low latency drives modern infrastructure architecture(blog.chiselstrike.com)
4 points by penberg 4y ago|0 comments
19.
Fly.io makes infrastructure easy for developers(blog.chiselstrike.com)
185 points by penberg 4y ago|121 comments
20.
How far can you go without a message queue?(blog.chiselstrike.com)
64 points by penberg 4y ago|94 comments
21.
Offline data access: a dream come true?(blog.chiselstrike.com)
3 points by penberg 4y ago|0 comments
22.
Jurassic Cloud(usenix.org)
1 points by penberg 4y ago|0 comments
23.
by penberg 4y ago
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.
24.
Show HN: ChiselStrike serverless runtime for TypeScript with native data layer(github.com)
2 points by penberg 4y ago|0 comments
25.
by penberg 5y ago
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
26.
by penberg 6y ago
User-level threads do not solve the problem of synchronization and data movement. That is, with a “thread-per-core” model, you eliminate most needs to synchronize between multiple CPU cores, and, therefore, eliminate the overhead of acquiri
27.
by penberg 6y ago
So thread-per-core is not just about eliminating context switches. It's also about partitioning application-level data to reduce inter-core synchronization to let speculative, out-of-order cores run independently as much as possible. D
28.
by penberg 6y ago
Excellent question! I think VoltDB, for example, uses the same application-level data partitioning approach, but with processes instead of threads. One advantage of the "thread-per-core" approach is that it allows fast communicati
29.
by penberg 8y ago
AGPL treats "networked access" as "distribution", not "linking". With the GPL, you are required to make your modifications available as GPL if you distribute the modified program. This creates a loophole for AS
30.
by penberg 8y ago
AGPL is an open source license as per OSI definition which you yourself point to! You don't have to take my word for it, just check out their own site: https://opensource.org/licenses/AGPL-3.0 The licenses you are

More ›