- cross-posted to:
- typescript@programming.dev
- cross-posted to:
- typescript@programming.dev
You must log in or register to comment.
Typescript 7 is here. Ron Buckton, not so much.
Bit fixing the title, the tsc compile is 10x faster, not the runtime.
Anyone this is relevant to assumed this I’m sure.
And it was slop coded by engineers who think it’s fine to talk in abusive mannerisms to chatbots inside of GitHub PRs.
I’m staying far, far away from this nonsense. Personally I only write in JavaScript anyway and only use tsc for type checking. Will pin to v6 for as long as humanly possible.
Are you thinking of Bun’s rewrite in Rust? Or else please share the deets, cuz I have not heard of this drama.
Just go look at the repo. 😅
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:
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.
