Talking about current LLMs while trying to assert future impossibility, and not mentioning an actual architectural problem, is giving a hint of not seeing past your own nose tbh
Unable to see the architectural problem mentioned is just icing on the cake.
How do you do this?
>> Its not happening, at least not with LLMs
> Correct.
>> Writing such a complex software as database engine requires strategy, awareness and rigor.
> Correct. Current LLMs are pathetic at architectural correctness without expert supervision at every turn.
> Try having a discussion on designing an architecture for a new kv engine with cache-oblivious algorithms that beats lmdb on generic random point-key lookups on a disk-backed mmap file.
> What happens in the future is up for debate,