🚀 go-pugleaf

> Because some of us do write large Prolog programs that depend on efficiency,
> and it's better to instill good programming habits from the beginning than to
> overcome bad programming practice later on.

Proof, I guess, that using a logic programming language does not make us
logical.  If I were willing to accept your equation of 'good programming
habits' with fast code, I wouldn't have posted my note about writing
Prolog as though it were Pascal with commas.  If you want to make anyone
believe it, you should provide an argument or two in favor of it, not
just say it again.

The real problem for me in your note, however, is your assertion that
relying on Prolog's declarative semantics is 'bad programming practice'.
The relative clarity of its declarative interpretation is one of the
most appealing things about Prolog -- God forbid we should begin to
think of it as a 'bad habit' if we take advantage of one of the best
features of the language!

If you write big systems that have to be optimized to be fast, you have
a right to worry about writing fast code.  You do not have the right to
spread the pernicious falsehood that speed is the only criterion of good
code.

-C. M. Sperberg-McQueen