HackerTrans
TopNewTrendsCommentsPastAskShowJobs

penberg

no profile record

Submissions

Show HN: A tool to manage a swarm of coding agents on Linux

github.com
5 points·by penberg·3 ay önce·3 comments

Repairing Programs with AI Agents

penberg.org
3 points·by penberg·4 ay önce·0 comments

Building AI agents with just bash and a filesystem in TypeScript

turso.tech
2 points·by penberg·6 ay önce·0 comments

AgentFS with FUSE: SQLite-backed agent state as a POSIX filesystem

turso.tech
7 points·by penberg·7 ay önce·0 comments

comments

penberg
·3 ay önce·discuss
There's a reference manual in Git repository, but probably not what you're looking for. Will add something.
penberg
·3 ay önce·discuss
Yup, Ghostty build requirement.
penberg
·9 ay önce·discuss
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.
penberg
·9 ay önce·discuss
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.
penberg
·9 ay önce·discuss
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.
penberg
·12 yıl önce·discuss
If you already know C, you can start out by looking at the machine code generated by your compiler with "objdump -d" on Linux and "otool -tV" on Mac. Start experimenting by writing out C constructs like functions, loops, switch statements, etc., and just looking at what the generated code looks like.

Of course, to do that, you need to find the manual for your machine architecture. The x86 manuals are, for example, available here:

http://www.intel.com/content/www/us/en/processors/architectu...

You also then start to notice things like the operating system specific application binary interfaces (ABI):

http://www.x86-64.org/documentation/abi.pdf

and object file formats such as ELF that's used in Linux:

http://www.skyfree.org/linux/references/ELF_Format.pdf

or Mach-O used in Mac OS X:

https://developer.apple.com/library/mac/documentation/develo...

You can also do the same thing with the JVM and look at its JIT-generated machine code with the '-XX:+PrintCompilation' option:

http://stackoverflow.com/questions/13086690/understanding-th...