4 ms·
Clearly the issue is that you are going from Erlang/Elixir to Java, rather than the other way around :) Jokes aside, they are pretty different languages. I ima
by abrookewood 1y ago
Clearly the issue is that you are going from Erlang/Elixir to Java, rather than the other way around :)
Jokes aside, they are pretty different languages. I imagine you'd have much better luck going from .Net to Java.
- nine_k 1y agoThis mostly means that LLMs are good at simpler forms of pattern matching, and have much harder time actually reasoning at a significant depth. (It's not easy even for human intellect, the finest we currently have.)
- tsimionescu 1y agoSure, it's easier to solve an easier problem, news at eleven. In particular, translating from C# to Java could probably be automated with some 90% accuracy using a decent sized bash script.
- mattmanser 1y agoI once redid a project from VB.Net to C# and pretty much did that. People misjudge many tasks as 'hard' when they are in fact easy but tedious. The problem is you need a high degree of accuracy, which you don't get with LLMs. The best you can do is set the LLM on a loop and try and Brute force it, which is the current vibe 'coding' trick. I sound pessimistic but I'm actually shocked at how effective it is.