I'm looking at this situation strictly as 'What's possible today'. If a 1M lines code rewrite from one language to another goes into production in 1 month, that's a very strong signal that the models are now insanely capable.
My anxiety before merging a 2K lines PR is greatly reduced after 3 frontier models (Fable, 5.6 and kimi K3) finds no issues in it.
Just 6 months ago (Opus 4.6) this was not true, a big PR would have countless number of issues.
Aside from the human drama, the message to all of us is - these things are ready for whatever your imagination can throw at them.
I think that's exactly what Anthropic wanted to communicate.
A better title would be 'My emotions on the Bun Rust Rewrite', since the article feels like an emotional reaction rather than a thoughtful analysis of the situation. Give it some time..
I'm rooting for Zig either way, even though I have nothing against Rust and I don't directly use bun.
because it's unusable in practice. It's fun as an idea and as a toy, but when you try to use such a visual system to do work, you quickly realise that text is way more flexible and simpler to operate on.
This is and has always been inevitable with tech.
Politics can only postpone people's inherent desire to control and dominate and powerful tech makes this easier and cheaper.
We (the tech people) have built the perfect tools to centralize and automate control and we're still doing it, mostly for free.
The way things are going, our imagination is probably too poor to visualize the kind of dystopia this can/will eventually grow into.
It's highly unlikely that the general population will revolt against this - fear makes most people docile and compliant, self censoring and obedient. There are many examples of this in the world right now and it's only going to get worse.
We can only push back to postpone this, but the tide is against us and too few really care about these things.
It depends on what your function does with that memory. If the fn expects any kind of structure at that address, you and your callers are on your own, compiler can't help if the caller passes the wrong thing.
Worse, acessing that memory might not immediately crash, but lead to strange side effects in your program.
Dynamic languages can handle this with reflection, but with void* you can only pray nobody makes the mistake..
Have you ever used other (modern) programming languages ?
In a lot of languages, you achieve the same with 1 line of code. It's not about familiarity, it's about the fact that it's a long and convoluted incantation to get the name of an enum.
Why do I have to be familiar with all those weird symbols just to do a trivial thing ?
I was very curious to see what C++ 26 brings to the table, since I haven't used C++ in a while.
When I saw the 'no boilerplate' example, the very first thought that came to my mind:
This is the ugliest, most cryptic and confusing piece of code I've ever seen.
Calling this 'no boilerplate' is an insult to the word 'boilerplate'.
Yeah, I can parse it for a minute or two and I mostly get it.
But if given the choice, I'd choose the C-macro implementation (which is 30+ years old) over this, every time. Or the good old switch case where I understand what's going on.
I understand that reflection is a powerful capability for C++, but the template-meta-cryptic-insanity is just too much to invite me back to this version of the language.
Claude code deleted the database once for me. It wasn't production, but it did contain data I needed. The good thing was that I made a backup of the database right before running claude. I told it that I made a backup, so it decided to delete the db rather than drop the table.
Why did you delete the database? you were supposed to drop the table !
• You're right, I apologize for that mistake. You said to drop the table, not the entire database. I should have run:
DROP TABLE IF EXISTS model_requests; Since you mentioned you backed up the database, you can restore it and I'll run the correct SQL command to drop just the model_requests table.
I use my Brompton in ways which are not on its label.
Besides rides in the city, I take it on long 100+km rides on the road, on gravel, forests, rocks, mountains.
It has taken me on every street of Barcelona and around it many times over. I've had it for 14 years.
Because of the small wheels it's extremely agile and allows you to go really slow without losing balance. This makes it like a sharp knife in the city but also off road on rocky trails, steep climbs, eg. in places where you'd never think of going with a Brompton.
If the trail is impossible, I can just lift it up and climb with it on my shoulder. Or I can fold it and carry it like a bag, on the metro, trains or in the trunk of the car.
As I understand, I'm not the only one using the Brompton as a gravel/mountain bike, so they released the G-line, which I still haven't checked out, but it's on my bucket list.
If I were to write one eulogoy for a piece of equipment in my life, the Brompton is definitely it :).
"If only I had an agent which does everything at work for me".
The logical continuation would be 'then I wouldn't have to work', right ?
No. Just as with coding agents, it doesn't mean less work - it means a lot more work of a different kind with the main challenge - don't loose your mind when managing the outputs from these agents.
Look at it another way - if these agents work perfectly and really increase productivity and profits and companies agentify all of their processes/development - then won't these companies essentially become extensions of OpenAI and not the other way around ?
The comment was for the article 'Obsession with growth is destroying nature'. Read it. It's not about me personally.
In fact, I live a very comfortable life in a beautiful city.
But this comfort has a price, described in the article. It's huge.
It's also not static, it's growing and accelerating.
Our children will have to pay these bills in one way or another.
What I do with my life (or you with yours) has zero consequence on this, the process can't be stopped. But it will one day, because math.
But you do realize that all the positives are mostly hedonistic ?
Yeah, there are more places to enjoy yourself and have fun, more entertainment.
I'm passionate about going out to clubs, electronic music events, concerts, restaurants, flying around on a plane or driving my car on the endless roads.
All of this is great, but according to TFA and my own experience, we're absolutely shitting on the natural world to have our nice drink or exotic food which will be gone from our system in 12h.
We've 'borrowed' from the future generations to have our fun and I'm not sure it's all worth the price.
When I was a child, I was spending my summers at my grandparents.
They had a cozy house in the village.
They worked the land, they had a few animals.
They grew their food.
They sold some wine and fruit at the market.
They had a big house, land, clean air, clean water and they were healthy.
They celebrated the holidays, had many friends, went to church, weddings, funerals, etc.
Villagers always greeted them and stopped for a quick chat when they met on the street.
Now compare with life in a big modern city.
I design complicated distributed systems using AI in order to provide shelter and food for myself. Those are tools which other people use to achieve their goal of providing shelter and food for themselves.
Tons of cars, the air is polluted, constant noise, fake bling, restaurants selling food at 20x price, stressed, depressed, lonely people.
Each in their own digital rabbit hole on their phones all the time.
Smiles for money only.
I'm really struggling to understand what we've grown into and why this rat race is considered 'better' than what people have had for millennia without destroying nature in the process.
I tried maintaining chat hostory and summary in a 'changes' dir in the repo. Claude creates a md file before commiting (timestamp.md, commit hash doesn't work as filename because rebase/squash).
I had to stop doing this because it greatly slowed down and confuse the model, when it did a repo search and found results in some old md files. Plus token usage went through the roof.
So keeping changes in the open like that in the repo doesn't work.
Not sure how tfa works, but hopefully the model doesn't see that data.
It's very tempting to agree to the 'gambling' part, given that both a jackpot and progress towards the goal in your project will give you a hit of dopamine.
The difference is that in gambling 'the house always wins', but in our case we do make progress towards our goal of conquering the world with our newly minted apps.
The situation where this comparison holds is when vibe coding leads nowhere and you don't accomplish anything but just burn through tokens.
Great work! Obviously the goal of this is not to replace sqlite, but to show that agents can do this today.
That said, I'm a lot more curious about the Harness part ( Bootstrap_Prompt, Agent_Prompt, etc) then I am in what the agents have accomplished. Eg, how can I repeat this myself ? I couldn't find that in the repo...
Bottlenecks. Yes. Company structures these days are not compatible with efficient use of these new AI models.
Software engineers work on Jira tickets, created by product managers and several layers of middle managers.
But the power of recent models is not in working on cogs, their true power is in working on the entire mechanism.
When talking about a piece of software that a company produces, I'll use the analogy of a puzzle.
A human hierarchy (read: company) works on designing the big puzzle at the top and delegating the individual pieces to human engineers. This process goes back and forth between levels in the hierarchy until the whole puzzle slowly emerges.
Until recently, AI could only help on improving the pieces of the puzzle.
Latest models got really good at working on the entire puzzle - big picture and pieces.
This makes human hierarchy obsolete and a bottleneck.
The future seems to be one operator working on the entire puzzle, minus the hierarchy of people.
Of course, it's not just about the software, but streams of information - customer support, bug tickets, testing, changing customer requirements.. but all of these can be handled by AI even today. And it will only get better.
This means different things depending on which angle you look at it - yes, it will mean companies will become obsolete, but also that each employee can become a company.
My anxiety before merging a 2K lines PR is greatly reduced after 3 frontier models (Fable, 5.6 and kimi K3) finds no issues in it.
Just 6 months ago (Opus 4.6) this was not true, a big PR would have countless number of issues.
Aside from the human drama, the message to all of us is - these things are ready for whatever your imagination can throw at them.
I think that's exactly what Anthropic wanted to communicate.