Remix.run Logo
▲ egonschiele 6 hours ago

It's exciting to see the speed gains. I use TypeScript every day on a large codebase, and it is too slow to run locally. I don't love this change though:

> However, frontier AI models can now do large-scale ports almost independently in a matter of days

> I wrote zero code. Not "barely any". Zero

So we are going to move from a carefully handwritten port to an entirely AI-generated port. I know this is the way the industry is headed, I use coding agents a ton. But I still review their output because they often don't make sound architectural decisions. Maybe this is a sign that my way of working is going away. I'm not sure how to justify that kind of time spent when someone can do the same thing in a matter of days with barely any effort.

I am working on my own language now, I've spent most of this year on it. The idea that someone could just replace it in a matter of days is wild. Wonder how the TS team at Microsoft feels about this.

▲TheSamFischer 5 hours ago | parent | next [-]

> The idea that someone could just replace it in a matter of days is wild.

They didn’t design a language that millions of human engineers enjoy (?, lol) using. They took an existing codebase and ported it. Yes, the porting part is easier now but only because another project and spec exist.

▲FuckButtons 5 hours ago | parent | next [-]

While this is true - and I see the same sentiment as i am about to make ad nauseam - it is kind of amazing how far the goal posts have moved in such a short space of time.

▲TheSamFischer 5 hours ago | parent [-]

It’s not a goal post. It was literally a fucking benchmark of the very first LLMs.

▲pas 36 minutes ago | parent [-]

sorry, can please explain this? which benchmark are you referring to?

▲egonschiele 5 hours ago | parent | prev [-]

That's fair, I was thinking the same – porting must be simpler, especially if there's already a substantial test suite

▲onlyrealcuzzo 5 hours ago | parent | prev | next [-]

If TypeScript has the integration testing framework in place to verify that the compiler actually works (and it should) - then, presumably, you should be able to swap in a Chinese Room black-box and - at least - know that it works.

You do have to be worried that it's possibly installing trojan horses on your computer while compiling code, or any other number of unwanted side effects.

But you can and should be able to have integration testing in place to know that a compiler - at a minimum - actually works.

▲egonschiele 5 hours ago | parent [-]

Totally fair. The thing is, though, agents often write code in ways I don't expect, and I don't think any human would write, which makes me think that code may also break in a way that no human expects or would have written a test for.

▲filopedraz 3 hours ago | parent | prev | next [-]

[flagged]

▲spiderice 3 hours ago | parent | prev [-]

Your way of working is definitely going away. And quickly. The idea of reviewing code today is already a questionable use of time. In a few more months to a year it will clearly be a waste of time.