what would make you change the programming language of your codebase in 2026? does a programming language choice matter if agents are writing for you anyway?

Last edited Aug 11, 2026 · 6:38 PM UTC

39
2
34
7,592
Sort replies: Relevant Recent Liked
Replying to @lenadroid
We changed to effect which is more or less a dsl for writing good typescript because it makes it easier to build and maintain large complex TS codebases Also @mikehostetler is more or less BEAMpilling me through osmosis
2
9
645
Curious, is your choice mostly based on accessing a programming language for humans or for agents? Probably both but which one more
1
268
Replying to @lenadroid
to anyone who says language choice doesn't matter i challenge you to write your b2b saas in x86 assembly
1
5
230
Ok, nuance - it obviously matters, but in what way does it matter? 10 years ago teams would debate about languages and would almost never consider a huge migration because of high costly it’d be. Now, has this changed? Agents know any language. What would make someone switch?
1
2
223
Replying to @lenadroid
You finding me one of those GPUs you posted a while back.
1
1
347
Replying to @lenadroid
I've already switched my stack earlier this year.
1
2
174
Why so?
1
147
Replying to @lenadroid
If my agent decides to change the language for whatever reason, I would let it
1
1
146
Replying to @lenadroid
Language doesn't matter until you talk to someone working on the BEAM There's drawbacks, but the runtime and declarative approach make it fantastic to build with Learning curve is steep, but agents are very good at writing it now
2
1
27
1,627
Replying to @lenadroid
Only matters for a couple reasons:
Programming language doesn’t matter until you need to: - have actual parallelism - scale horizontally - scale vertically - compile 1m LoC - incrementally compile 1m LOC - refactor without breaking anything - review a large diff - validate a change - detect and remove dead code - maintain backwards compatibility - get a large team working efficiently - onboard new hires - validate the security of a system - invent custom abstractions to reduce duplication - work around abstractions someone else invented - troubleshoot production issues at 2am - be operationally efficient - deploy on Friday - deploy 100 times a day - handle time & timezones correctly - handle currency correctly - eliminate null pointer exceptions - depend on libraries that are maintained & secure ​​- produce something of more value than a tweet
1
10
635
Replying to @lenadroid
A TC bump
1
4
458
Replying to @lenadroid
I'd say any language that compiles and is relatively memory safe (and not esotheric) Two reasons: 1/ shifting left, you catch a lot of issues way early on during compilations. 2/ There is absolutely no reason not to! In the past, more approachable languages were chosen due to simplicity. Now, well agents write it for us, so yeah you get the benefit of a great language. Why not to choose these languages over something very mainstream? Lack of needed libraries (ie Rust sucks at front end stuff). If you are really not familiar with the language, it may cause you issues in trusting the agent output.
2
208
Replying to @lenadroid
I choose to optimize for happiness. Ruby

ALT Fashion Love GIF by Roger Vivier

1
1
243
Replying to @lenadroid
if you pick Haskell as PL, the quality of unsupervised generated code will drop tremendously. It is being improving but still too slow. Cost of the supervision is unbearable.
2
92
Replying to @lenadroid
Do I need to build and deploy faster (eg, Rust or TS builds are too slow)? Move to Go. Does it need code to metal performance, memory management and build times don’t matter? Move to Rust. Do I need to integrate with Microsoft specific systems? Move to C#. Build for the use case instead of what you’re most comfortable with, that being said, if you don’t understand the code you shouldn’t deploy it. If something goes wrong and you don’t understand it, you’re in trouble.
2
60
Replying to @lenadroid
If I’m using anything other than typescript.
2
105
Replying to @lenadroid
matters more than ever. choosing a programming language never was (and never should be) just about personal preference, but about what the job needs: performance, readability, security, types. it’s like choosing the right infrastructure for a specific workload.
1
60
Replying to @lenadroid
Tools matter. Programming languages, like any system, are shaped by different design principles. Even when they serve the same purpose, the way they achieve it varies. And that difference matters.
1
100
Replying to @lenadroid
The language chosen affects the choices the AI tools make. You should pick a language with depth in your problem space unless you want to change something specific. For example I wanted to bring more visualization features to data engineering so I use JS not Python.
1
43
Replying to @lenadroid
It does but I would just stay with Erlang because it's unique features and unique runtime give a advantage for agents too
1
98
Replying to @lenadroid
Yes it does! Programmings languages are purpose oriented. You technically can write anything in any language but, you don't write a kernel in JavaScript and a webapp in C
1
32
Replying to @lenadroid
It matters, but only in the ways unrelated to authoring. Go has dead simple deployment. If you prefer the performance characteristics of a JVM, you have a few choices. Rust (from what I understand) is (most) memory “safe”. Python is still king for ML related workloads because of the ecosystem
1
73
Replying to @lenadroid
Ya it does. A lot depends on the purpose of work and capabilities of the tool/lang
1
31
Replying to @lenadroid
I’d switch to a language that offers a substantially higher level of abstraction, with clear and verifiable semantics, while still compiling predictably onto existing infrastructure. Even if agents write the implementation, and even if I rarely read it directly, I still need to express what the system should do and verify that the result preserves that intent. The language should shape the vocabulary I use to write specifications, making as much of their meaning, constraints, and guarantees machine-checkable as possible. Language choice still matters, but increasingly as the interface between human intent and generated systems rather than as a tool for writing code by hand. By “higher level,” I mean something like SQL, but for the entire system, not just queries. That language doesn’t exist… not yet, at least :)
1
1
106
Replying to @lenadroid
Nothing - only performance- customer need - developer experience (translating to velocity or stability)
1
93
Replying to @lenadroid
I don’t think it matters anymore but I still choose the ones I’m comfortable with. Makes it easier for me when I need to dive into something myself.
1
63
Replying to @lenadroid
IMHO a lang with a good compiler make the diference, if someting goes wrong the quality of errors decriptions make the diference
1
85
Replying to @lenadroid
Yeah it matters for the iteration speed of your agents. Frontend: Typescript Backend: Go
1
1
46
Replying to @lenadroid
baml!
1
33
Replying to @lenadroid
language choice matters not because agents or humans write it, but because of benefits it provides for your codebase/product and if migration costs covered by profits. idk, but it was always like this, no?
40