Exactly the same as the OpenCode drama, at this point OpenAI are just getting free customers from common sense.
Anthropic seem oddly focused on their moat being the app, rather than the underlying intelligence and model. Which is odd when Claude Claude is no better than all the other harnesses.
I have a suspicion that the reason they’re using react, and the reason they’re trying to keep people using Claude code instead of other tools is because it gives them additional data to train on.
It's even simpler than that. They keep trying to get people using Claude code because that's their vendor lock in. That's their business model. They don't want to become a commodity, they want you to use Claude Code. I can't blame them either.
I'm sure a lot of API plumbing can be copied/adapted wholesale from the (open-source) openclaw repo. LLMs are surprisingly good at this kind of stuff. And yeah it would require some testing, but I doubt what openclaw has now is itself in a very stable state (from my very limited testing)
You think he implemented those thousands of integrations himself?
Or maybe some particular tool was used that can be used again for implementing such things? Particular tool that so many of us use as well?
Honestly the trademark thing was fine on its own — you protect your brand. But Anthropic was playing a legal game while OpenAI was playing a relationship game. One got a name change, the other got the most visible open-source agent project. If you're going to push someone away, maybe think about where they land.
Miss the boat on what? Idiotic agents with no sandboxing, with the door fully open for prompt injection purgatory? There's nothing interesting about this technology other than how dumb it is and how badly it will spam the internet (see https://theshamblog.com/an-ai-agent-published-a-hit-piece-on... for how bad agent slop has gotten).
Yes. Tax season for small businesses and New Year's resolutions for personal finances are the times I get the largest influx of new signups and subscriptions.
Not sure I’d be worried for my job, but it’s legitimately a significant jump in capabilities, even if other models attempt to fudge higher bench results
First, "just use" is doing a lot of work in that sentence, because DPDK is much harder to use than XDP. The authors of this blog were surprised they had to do their own checksumming, for instance.
Maybe more importantly: they're not building a middlebox. DPDK ultra-high performance comes in part from polling. It's always running. XDP is just an extension to the existing network driver.
It’s boggles my mind that enterprises or SaaS wouldn’t be following release cycles of new models to improve their service and/or cost. Although I guess there’s enterprises that don’t do OS upgrades or pathing too, just alien to me.
They're almost never straight upgrades for the exact same prompts across the board at the same latency and price. The last time that happened was already a year ago, with 3.5 Sonnet.
Same background as me, however I moved into cellular/mobile - not really any official routes I know of in the industry, certainly not like a Cisco track.
Typical route is work at a Telco or IoT company as Network Eng or Developer and naturally pivot into telco learning on the job.
Vendors will run training courses when you buy their kit which helps a little, but it’s mostly self learning or on the job.