Interesting. I hadn't touched my Openclaw install but just recently revived it, updated the software, and switched API keys to a different provider. Suddenly everything was completely broken. I kept messing with it, abandoned discord for IRC in an attempt to just get basic comms online, but it's still cooked. Now it makes sense.
That's why I designed my bot to have a very small core, with most other things being plugins, from the start. I also containerized everything and made it so the bot never sees API keys as well.
The very concept of installing something that pulls in a ridiculous amount of unvetted npm dependencies likely rife with supply chain attacks makes my skin crawl.
A real team? With humans? Meatbags? What do you need those for?
Imagine paying any amount of money for this unmaintainable slop, and then worse, paying a team to try to salvage the hundreds of thousands (or is it millions now?) of lines of never-read-before code. Guess it doesn't matter when it's monopoly money you're burning, though. Sam says AGI is achieved internally in 2025, Boris says software engineering is dead and that no human is writing code at Anthropic, Jarred says humans will be banned from contributing to open source projects, and while all these people are pissing on your face and telling you it's raining, when you open your eyes all you are left with is, in fact, a bunch of piss in your face.
People need a mental bucket for 'stochastic software' for a while. Or hot mess, a fast food meal that you can expect to mostly be bad in some sense, but serves a purpose, and can be really good in that case.
Conflating the new style of agent-driven/vibe coded software with the old more predictable software leads to applying wrong heuristics/expectations.
People have a pretty good mental model of different types of meals they'll have in a year, and modulate their expectations by context. I think there's room for a new type of software that operates on different principles. Peter has mostly been clear what type of software he's developing. And if it ever converges to bug free, that's great, but I think some of his motivation is to figure out what this new software is. While not giving the users food poisoning.
22 comments
[ 4.8 ms ] story [ 46.7 ms ] threadhttps://stavrobot.stavros.io if you're interested in the design decisions.
Just show us the prompt, don't ask an AI to apologize to people
A real team? With humans? Meatbags? What do you need those for?
Imagine paying any amount of money for this unmaintainable slop, and then worse, paying a team to try to salvage the hundreds of thousands (or is it millions now?) of lines of never-read-before code. Guess it doesn't matter when it's monopoly money you're burning, though. Sam says AGI is achieved internally in 2025, Boris says software engineering is dead and that no human is writing code at Anthropic, Jarred says humans will be banned from contributing to open source projects, and while all these people are pissing on your face and telling you it's raining, when you open your eyes all you are left with is, in fact, a bunch of piss in your face.
https://github.com/openclaw/openclaw
So many MRs
Conflating the new style of agent-driven/vibe coded software with the old more predictable software leads to applying wrong heuristics/expectations.
People have a pretty good mental model of different types of meals they'll have in a year, and modulate their expectations by context. I think there's room for a new type of software that operates on different principles. Peter has mostly been clear what type of software he's developing. And if it ever converges to bug free, that's great, but I think some of his motivation is to figure out what this new software is. While not giving the users food poisoning.