This is interesting, TBH the Ease of using FE & BE in Typescript is the reason I think. I'm also using TS for that.

The agent layer is a kind of client and since typescript thanks to node and the browser has become a universal language for client sides, whether the client is used by a human or used agent to agent.

much more easier to built UI

> - Also, as Sam points out, full-stack devs can ship quickly using TS for both backend and frontend.

Typescript (which is still "Javascript") is extremely immature for a "backend" language.

I can't take anyone seriously if they believe or use such a pseudo-typed language like typescript and especially a weakly typed language with dynamic types on a costly runtime such as Javascript on the backend.

Both of them should stay far away from anything backend.

I'm not surprised, I don't think it has anything to do with AI, it's the same in blockchain and prob in all other fields.

I think ppl underestimate the cost of context switch between languages, even if you're really proficient in more than one.

If you're a team with 1-2 eng and have to build a frontend, you are forced to use js/ts. Now, if you can keep everything in a monorepo in the same language, you're simply moving faster. And I'm sure people will criticize and bring counter examples... but statistically 60-70% of the teams will just be faster working this way.

My first startup was frontend php, backend python, 2 eng; soon we specialized one working on frontend, the other on backend, it's tedious to context switch. My last startup was typescript for everything, again 2 eng, same code base, same coding style, both iterating on all code. (And daily I work in rust & C, I'm definitely not a frontend eng nor a js/ts enthusiast, I'm just reflecting on efficiency.)

Makes sense - for front-end there's really no alternative. For back-end node.js is more than fast enough for pretty much any startup.