I think this is an artifact of "source code is text" that our current tools assume (and is invalid IMO).
Otherwise I agree
I think this is an artifact of "source code is text" that our current tools assume (and is invalid IMO).
Otherwise I agree
- precise "decompilation" to readable, idiomatic text - comments - line numbers or some semantic equivalent
There is no more efficient way unless you go to down to writing assembly or go down to writing 1 and 0.
Everything you build up as low code has to create much more data which takes obviously much more space than high level languages we use today and if you want to do change control - any other data structure will take even more space. Then all of it will be obviously slower because more data is not just a bit more data but at least order or two orders of magnitude more.
LLMs are great at compression but compression with them is not lossless so even if we write behavior to be interpreted by LLM to be executed it might turning out differently each time you run it.
That last one is not a tradeoff we can deal in I would guess 95% of applications. People expect 2+2=4 from applications but they want to say „computer add two numbers that add up to 4” and they don’t really want to to crash because pi+x=4 and LLM went hanging because it is now calculating PI and then it will move to finding X.
So this is why it will never work other way than „source code is text”.