Another commenter explained it: It's about working on multiple branches in parallel. You can only check out one branch at a time currently in git - but with "but" you have all the changes just in memory so different agents can work on different branches at the same time.
Working on multiple branches in parallel is literally what Git was created for, and how it's been used since the very first version 20 years ago.
Other commenters mentioned worktrees, which let you check out different branches at the same time from a single local repo. That's convenient, but not required.
Git always supported "fast cloning" local repos as well. You just "git clone" from one directory to another. Then they are independent and you're free to decide what to merge back.
These days, agents can also fork their containers or VMs as often as required too, with copy-on-write for speed.
So that's four ways to work on multiple branches in parallel using Git that we already use.
Absolutely! The community has always been the strongest part of the project.
In the new version the core player itself is built as many composable components rather than one monolithic player, so we're going to invite more people to contribute their "plugins" to the core repo as more of those composable components. Versioning plugins and keeping them up to date has always been a challenge, so we're thinking this will help keep the whole ecosystem working well together.
Deno basically popularized the idea of a standalone JS runtime that primarily relies on standard Web APIs over "in-house" APIs like Node, although we can say that those standard APIs didn't exist yet when Node was created and for most of its rising period.
I don't think I'd go as far as "copying" but Deno was the first to aggressively push for web standards in server-side runtimes and certainly helped accelerate getting them adopted in that environment.
I work at Cloudflare on Workers (but infrequently work on our runtime) and I've always been pretty impressed with Deno. Their recent-ish support for built-in OpenTelemetry is something we've been wanting to do for a while and have been working on, but Deno was able to build a good implementation of that in that time.
(I love cloudflare workers and thanks for that), but I do think that credit is where its due and Deno's push for server side web standards also helped the general ecosystem.
I think it’s fair to say that work on the experimental-strip-types option in Node was inspired/energized by a desire to try to catch up with the DX improvements found in Deno for Typescript-first development that is now the norm.
I always thought Deno was more or less trying to copy the Cloudflare (edge) runtime, but decided incompatibility was a good idea. The ecosystem bifurcation was the mistake, which they came around on, but it was already too late by then.
Anthropic, the company that actually has much worse revenues and likely mislead the public? [1] That Anthropic? The same Anthropic that has taken billions of gulf state money where the countries are on the verge of divesting itself from the US or fear of potentially losing their refineries + oil fields for at least 50 years? That same Anthropic?
This house of cards is about to collapse and lot of "smart" devs are going to act shocked when the water recedes.
The same thing always happens: companies "adopt" open source then, unless you have monopoly, money problems eventually appear and leadership sees this lovely team with "bloated budget" in the bylines.
I hate it when people use commentary articles as fake sources for their points. It's even more aggravating when the "journalists" are making points that play to the ignorance and outrage of the reader, as they know those readers are the easiest to bait for clicks and mislead. For instance, how is Anthropic claiming that its total revenue since January 2025 as $5 billion contradict that its expected run-rate revenue for the year 2026 is $19 billion?
> Anthropic claiming that its total revenue since January 2025 as $5 billion contradict that its expected run-rate revenue for the year 2026 is $19 billion?
Isn’t the “exceeding $5BN” comment a lifetime revenue? … on $30BN (edit: previously said spent) raised (or something ridiculous.)
A lot of the commentary on the frontier model companies is based on how much money they’ve spent to the relatively small amount they’ve made in return, and the skepticism, especially given almost continuous reporting, that deploying AI in a variety of situations doesn’t seem to yield favorable business outcomes. OpenAI shifting to enterprise / coding type stuff this week seems, also, potentially informative. Is Gen AI actually useful for anything but code? Signs keep pointing to no… and even then, we’re in the early stages of figuring out how to build without destroying everything… something Amazon just recognized as possible with their recent shopping outage.
It also means the Bun team is no longer in control. Acquisition has a similar time frame and we've seen numerous projects chart a similar path to irrelevance.
reply