You can get those numbers with https://codeberg.org/ggz14/radiance-vllm-mxfp4. I also can get it on a single R9700 but the 75 ~ 80 t/s is only peak acceptance of very predictable tokens like coding or json, and averages lower for prose. It's still much faster than regular llama.cpp.
that’s likely the promise but it’s so confusing and high cognitive overhead to maintain that backend <-> frontend relationship. ‘use client’ - i think the special sauce for why people use nextjs is all frontend based. the frontend that comes from the backend.
nextjs dx is a special kind of hell. disclaimer: im just a simple rails guy.
Next.js is a poor choice for a client-side application. It is first and foremost a server-side framework, and trying to force it to be client-side is to work against it. There are so many better options than Next.js for dedicated client-side front-ends.
I don't understand this perspective. I've developed, delivered and maintained countless Next.js projects and never come close to considering it "high cognitive overhead." It's among the nicest DX I've experienced. It has a lot of features, I guess, but you don't have to use them if you don't like them. Next.js has very little to do with the frontend. The frontend is literally just react, which is why I commented in the first place. People keep acting like it's a "frontend framework" which doesn't make any sense at all.
React is a frontend framework. How do you get around that? It's invented entirely to handle client-side UX and reactive DOM updates which have to be DOM because it for the browser which is a frontend. Are you saying nextjs is the backend and react is just react, it's not nextjs' fault?
I'd say we disagree on the simplicity then: hydration, nextjs API reinventions of every interaction else 'use client' as an escape hatch which means it runs on the client but then what does the non 'use client' code do if nextjs is not a client-facing framework?
Yeah the base requirement has gone up. So more training/schooling is required.
Imagine when jobs started adding the requirement entry level positions require ability to read? That cut out so many people when that requirement was added yet the economy survived
I think the base requirement to compete will keep going up. We already have AI models that can debug and audit code better than the best humans.
You used to have a career as a software engineer or devops person if you were good at debugging. Today, I challenge you to take any past production outages, toss the traces into Claude Fable, and see if it finds the bug faster than humans can.
I think this is the way the rest of white collar labor goes.
I “try your suggested experiment” several times per month at work. Usually when I’m on call.
It’s great at being a search engine for our docs and communications. It can also find bugs quickly in small repos with static analysis and coverage tools.
But when it comes to larger projects or interconnected systems, the time it takes to correct its “assumptions” is often longer than the time it takes to solve the entire problem myself.
He was quoting the claim you made. Shouldn't you have your own justification for it? Which tests did you run with both Fable as well as the best human programmers?
Honestly? Not really, not since Fable came out. There's been a bunch of times it needed to ask for context, and I needed to deploy some additional tracing at its request.
(There have been a few times where it has refused to debug due to safeguards. This is actually the biggest problem.)
For some roles, I agree but I also think that there will be many new-ish roles that will have lower requirements right down to being a warm body capable of walking and talking. The lower requirements will be possible because these roles will essentially be proxies for AI agents that need a human to go somewhere and do something in the physical world, whether that's resetting a breaker or just being a human face and voice delivering a message.
And yes, before anyone brings it up, I've read Manna and if you haven't you probably should[0] but I don't think it will be as dystopian or utopian as that. Humanoid robots would obviously replace some of the proxy need but there will still be a lot of things that only a living human can do even if it's just purely for legal and regulatory reasons.
I also think there will be a lot more roles that are purely human in nature and which will have an entirely different set of requirements but that's a different topic.
Of course. For a great deal of software, the main skills needed are vaguely speaking the jargon so you can understand Claude, and doing manual debugging.
Taalas uses a design that requires masked ROM layers specific to a model, but Etched uses a newer design with a specialized RAM that supports any transformer model.
reply