Map.c is a lot more powerful since you can write any algorithm you want in script. For example, with the landscape.txt lines algorithm you're bound to implementation details of that algorithm, such as the random offset. In Map.c, if you don't like what the algorithm does, you can just write your own loop that iterates over all pixels and draws lines. On an unrelated note, the Map.c lines algorithm also supports arbitrary offsets.

You also have more control over the landscape. So if you want for instance exactly three batches of gold, placed anywhere on the landscape, you can write a loop that does exactly that. In landscape.txt, such control was impossible.

You can use extra parameters in the map. For example, you can place as many batches of gold as there are players activated for the game.

You can reuse script functions you wrote for one map on another. For example, there's a helper function to fix liquid borders so you don't have batches of water floating in the sky. This helper function can be called from any script. In landscape.txt, every landscape had to invent its own method using some variation of the border algorithm (and it usually didn't work perfectly).

You can post-process parts of the map already drawn. For example, you can create the left side of the map randomly and then mirror it to the right. You should also be able to combine that with Landscape.txt (Although admittedly that's still untested). E.g. : Create a landscape with Landscape.txt for the base map and then use a Map.c script to free space for starting positions, mirror the map, fix liquid borders, etc.

If people still want to use Landscape.txt for some reason, I'm fine with that. But they have to live with the limits of the old generator then; I don't see a reason to add more features to it.

At the moment, yes :(