Why not try to define a strict subset of the current specs, that would target ease of implementation & graceful degradation? I'd rather have many different clients compatible with a "web-lite" spec that is enough to navigate on 95% of websites, which would have an incentive to officially support that subset if it becomes popular enough.
Thanks for the write up. Always interesting to see how very senior developers interact with AI these days.
@antirez: Introducing a regex feature that late into the project for a seemingly unrelated feature feels a bit weird? Can you explain more your rationale on that? thanks!
Once I realized arrays were a great fit for text files, many use cases I could conceive were always limited by the fact we need to grep on files. So I thought: what is the AROP equivalent for files? ARGREP. Then I made sure to add both fast, exact and regexp matching so that depending on the use case the best tool could be used. I then discovered that for many OR-ed strings regexps could be the faster way if we'll optimized. And then I specialized TRE a bit.
I'm using this as my main way to run Claude & others, it's just a shell wrapper but it provides a lot of niceties and a pretty good developer experience in a single command line. Curious to have feedbacks on it!
Love Oxide and what they're building, but I'm not sure raising even more VC money is the way to build a generational company. Quite the opposite? With money you don't need, you're trading faster growth for more dependencies on third parties that will seek a ROI eventually?
Hardware businesses are capital intensive. They need the money.
They also need to grow and iterate faster. Their software stack is great, but their hardware is quite dated in a fast moving industry. This limits them to domains that value their software and security but don’t need the latest hardware for performance and aren’t necessarily concerned with performance per dollar, which is a small market.
> ...it's not uncommon for us to be asked directly: "How do I know you won’t be bought?"
Raising ~infinite runway from investors who are already known quantities signals that you can safely buy into their product knowing they're not getting snapped up by $megacorp anytime soon. That's where the faster growth comes from--customers who feel secure in the knowledge that the company isn't going anywhere.
Not necessarily. Supply chains and vendor management into scale is very difficult and very very expensive, I think we prob spend north of $200MM to get to $150MM ARR, but the economics started to shake out thereafter based on CAGR. To do this without owning 0% of the company while still recognizing needing a lot of cash in the system to keep everything lubricated, (for example Michael Dell might be fine personally extending a $500MM line of credit to the business, if the business has $50MM in venture funds on some predictable growth rate) - basically you use true risk capital via the smallest amount of equity you can give to de-risk downstream capital requirements. I don't know anything about how Oxide is growing their business so this could be total nonsense in their case, but it's how we built a generational business (digitalocean)!
I don't think any Oxide racks come with GPU's at present, and the power density of modern GPU-centric AI compute is on a rather unprecedented level. Oxide racks are very well cooled but are no match for the racks in an AI datacenter that's literally burning a full gigawatt of power.
Not sure this is necessarily for faster growth. Riding out the AI bubble's rise and/or its bursting will each present a lot of need for capital and a lot of barriers to raising it. They're not an AI company but they obviously have tons of exposure across the stack to these markets. They may simply be making the call that this is a better time to be raising money than the years to come.
This is the way to go! On my side I've build a very small `claude-vm` wrapper to run each instance in a VM with Lima: https://github.com/sylvinus/agent-vm
I'm convinced that VMs are the right primitive here, for now. Being able to give an agent full root and passing it in just the stuff you want it to have is super easy and it's extremely foolproof. I have my assistants free to install software, run docker, build their own nested VMs, etc. knowing that the boundary is sound and that no capabilities will ever be sacrificed.
I might switch to LXC to reduce the weight somewhat (easy with incus) but this requires providing a more limited set of tools (i.e. podman instead of docker).
bwrap is great, but you're stuck with the limitations of the environment, which depending on what you're doing may neuter the agent.
Yup, DINUM does support the Matrix Foundation, which is appreciated in terms of helping keeping Matrix itself alive and independent.
However, this doesn't help support the folks improving & maintaining Element (either its clients or servers), which is the actual upstream product that Tchap is dependent on. Just like donating to the W3C doesn't help improve Firefox, if you were operationally dependent on a Firefox fork.
We’re not trying to obscure anything: we very well know that Tchap’s adoption of Matrix and their current support (Foundation membership, code contributions to Element Web, evangelisation to other countries, etc.) are key to our success, and we are very grateful for it.
We’re just stating facts: DINUM stopped funding upstream development at Element in 2022/2023 when their post-COVID funding evaporated, and this then directly contributed to the licensing changes at Element at the end of 2023 (https://element.io/blog/element-to-adopt-agplv3/) as we tried to figure out a way to survive (which, thankfully, worked).
But we also know that the Tchap team is very budget constrained internally themselves to keep it running, despite the growing criticality and huge visibility of the service, and are trying to find ways to fix the situation at every level.
This is not a challenge limited to France: the question of how to support the upstream when heavily using open source was one of the top topics of last week’s Open Source Week in Brussels, involving folks at every level in European government.
reply