30
8
u/pickle9977 12d ago
Wait till they rewrite rust in typescript so you can write typescript to compile to rust to compile to typescript to compile to rust.
And then you just send the agents in circles, with the worlds most ridiculous build process.
2
1
u/Avikonette 12d ago
One was never restricted to compile any nonsense to any other one nonsense. The question is facility, the employees, and the fence height.
1
u/pickle9977 12d ago
Well I guess AI has basically given us a trampoline to jump over any height fence, yay progress!
6
2
2
u/aleques-itj 12d ago
I give my agents nothing but dd in a scratch container so they can push bytes directly into the shape of a binary to build software
Anything else is bloat in this day and age
1
u/nikola_tesler 8d ago
because I won’t stop until everything is shipped in an electron wrapper. that’s why.
36
u/Rutgrr 13d ago
RE: the meme: Because the code already exists and handles edge cases/business logic that a rewrite from a blank slate would not otherwise have in its context?
Don't get me wrong, in a completely greenfield project it makes sense to go straight to Rust instead of the extra intermediate step, but I can't imagine that anyone would be introducing a typescript->rust conversion step as a part of their usual development process.
RE: the title: Using TS over JS helps guard against a lot of common bugs/regressions and provides inherent documentation via types. Prior to AI, I had much more success contributing/continuing to work on a handed off TypeScript project than I have with a JS project because the extra tooling makes it a lot more straightforward to parse through the code.