Typescript’s port to Go was done (or at least the vast majority of it was done) by hand, before AI porting was feasible.
In any case, AI is quite good at 1:1 porting these days. I wouldn’t class the result as slop unless the input was slop or you did an especially bad job.
I personally haven’t looked at the port myself, but generally LLM/AI agents generate “slop” until a human expert reviews all of it. Which in most cases never happens. Instead they just review with another “higher tier” model.
As someone on hacker news put it regarding a subject about using LLMs for everything:
A decent proxy right now is that if you have zero external dependencies then your solution is probably a toy.
This can be related because unless they are actually using the best libraries in the ecosystem while they are porting then it’s going to be a mess to maintain and also alienates the ecosystem.
Typescript’s port to Go was done (or at least the vast majority of it was done) by hand, before AI porting was feasible.
In any case, AI is quite good at 1:1 porting these days. I wouldn’t class the result as slop unless the input was slop or you did an especially bad job.
Well that’s just demonstrably wrong. Go look at the commit history of the go port. Extensive use of Copilot. Slop.
Copilot is the second biggest contributor lol
I personally haven’t looked at the port myself, but generally LLM/AI agents generate “slop” until a human expert reviews all of it. Which in most cases never happens. Instead they just review with another “higher tier” model.
As someone on hacker news put it regarding a subject about using LLMs for everything:
This can be related because unless they are actually using the best libraries in the ecosystem while they are porting then it’s going to be a mess to maintain and also alienates the ecosystem.