I definitely felt this. I thought "If I have to redo this in Flutter or in Swift, I can". I don't know either, so have to move with some caution (but it's all very exciting).
At first glance, it seems like _porting_ code to another language / api .. is probably a good sweet spot for these code LLMs ..
.. and even automating the testing to check results match, coming up with edge cases etc.
... and if thats true, then they could be useful for _optimizing_ by porting to other apis / algos, checking same-ness of behavior, then comparing performance.
The whole "vibe coding" doesn't grab me - as I feel the bottleneck is with my creativity and understanding rather than generating viable code - using a productive expressive language like javascript or lisp and working on a small code base helps that.
eg. I would like to be able to take an algo and port it to run on GPU for example... without having to ingest much arcane api quirks. JAX looks like a nice target, but Ive held off for now.
> At first glance, it seems like _porting_ code to another language / api .. is probably a good sweet spot for these code LLMs ..
I recently ported skatevideosite.com from svelte/python to ruby on rails. I leaned on AI heavily to translate the svelte files to ERB templates and it did a wonderful job.
My experiene generally with these systems is that they are good with handling things you _give_ it, but less so when coming up with stuff from scratch.
For example I've tried to use it to build out additional features and the results are subpar.
