catwell

https://x.com/pchapuis/header_photo

Peter is not just a random "vibe coder" and he does not need to be hired by OpenAI to achieve "success". Before this he founded and sold a company that raised €100M. It is not his first project in the space either (see VibeTunnel for instance).

OpenAI is not hiring him for his code quality. They are hiring him because he proved consistently that he had a vision in the space.

Personally, I know Lua and Python very well but I still used TCL a few years ago for something very specific: using ODBC on Windows. I gave more details on the Lua mailing list here: http://lua-users.org/lists/lua-l/2021-01/msg00067.html

He's written about it here: https://daniel.haxx.se/blog/2025/10/10/a-new-breed-of-analyz... and talked about it in his keynote at FOSDEM - which I attended - last Sunday (https://fosdem.org/2026/schedule/event/B7YKQ7-oss-in-spite-o...).

I agree with the sentiment though, I even gave a talk about this at Lua Workshop 2013 (https://www.lua.org/wshop13/Chapuis.pdf) around that issue. There are good reasons why several important but OS-specific features are not included in the core language. Discussion around a "blessed" extended standard library module arise from time to time but never lead anywhere.

The Lua community - at least the one around PUC Lua - is reasonably small and you can typically look at what active popular projects use to figure out the best libraries. The LuaRocks download count can be an indicator as well. But I agree this is still a problem.

However I really like what you've done here for Dillo as well.

First, this is mostly about things that happened before his election.

The tribunal ruled he did not personally benefit, and he did not directly solicit money to finance his campaign either.

However, some of his closest allies (who would become his ministers later) did the latter. The tribunal could not find any direct proof he was involved but ruled there were enough "converging indications" that he knew and did nothing to stop it.

I love ST (my last blog post is https://blog.separateconcerns.com/2025-01-04-teal-lsp-sublim...) and I think the main thing lacking compared to the competition is the remote development experience.

I work in AI so we typically work over SSH on machines with big GPUs. Most of my colleagues use VSCode because it has a very good Remote Development extension.

Solutions are relatively easy on a client-server model (but do you really need something like ITC with a server...?) For instance the server could delegate its part of the interval with a timeout and claim it back once it expires.

If you know you have this model you can find a different way to split the interval to avoid the issue of the linear number of bits. Nodes can split their interval however they want.

When I did that talk I was at the point you are now, trying to find a real use case. I had considered them for Lima but we were actually find with version vectors.

I think the case where ITCs can really shine is when you have a lot of short-lived nodes. That could be containers or serverless functions, for instance. I didn't think about the tracing use case but it makes a lot of sense, you can fork a new node per request.

EDIT: I found where the paper has moved, I have updated the article.

> How that curve is initially drawn isn't clear at all. Is it flat and becomes complex over time by forking (+ data modification)?

Yes, the initial curve is typically constant 0.

> Why are interval boundaries real-value in a system that cannot actually express real numbers?

Like snthpy said "real" is a shortcut to say infinitely subdivisible. The numbers themselves are actually rationals.

> How are the intervals / portions decided? Is that simpler than generating UUIDs?

Nodes are forked from an existing node, that node decides which portion of its interval it gives to the new node. You pick the splitting point to keep complexity low.

Regarding comparison: you always know the values of the whole curve. When I say "a node only has to know about its share of the interval" I only mean the ID space. In a version vector there is a direct link between identifiers and counters, whereas here outside of your share of the interval you don't know who owns what or how many devices there are at any given point.

I don't know many systems that use ITC. Version vectors are simpler and sufficient in most cases. One of the authors of the original paper mentioned in a later presentation (https://cbaquero.github.io/web/pdf/SDLtime2021.pdf) that they were used for tracing, in particular in a 2015 system called Pivot Tracing.

Redis is a 15 years old project started in 2009 by Salvatore 'Antirez' Sanfilippo. He worked on his startup, then at VMWare, them at Pivotal, and only joined Redis Labs (created in 2011) in 2015.

In 2018 Redis Labs changed the license of their modules and Antirez published http://antirez.com/news/120 In 2020 he quit.

Anyway I agree with the conclusion: Redis will be forked, the fork will win and Redis Labs will become irrelevant.

They focus on the more specific problem of preventing drug misuse (checking interactions w/ other drugs and diseases, pathologies, etc). They use GPT-4 + RAG with qdrant and return the exact source of the information highlighted in the data. They are expanding their test set - they use real questions asked by GPs - but currently they have 0 % error rate (and less than 20 % cases where the model cannot answer).

Lines 1, 4 and 14 have rubber tyres and platform doors because they are fully automated (or in the case of line 4 in the process of being fully automated). So far Paris only fully automates rubber tyres lines.

Line 13 has classic metal tyres and is only semi-automated, but it has platform doors because it is very high traffic. Most Parisians avoid line 13 at rush hours because it is probably the most packed line in the city.

Posting occasionally since 2009.