Liste des Groupes | Revenir à cl prolog |
I don't feel adressed by you critique. Since IThe ISO standard is *broken*, not just totally *inadequate* and totally *impractical*. Which of course is a contribution to, but is rather orthogonal and additional to the problem of the sorry state of pretty much the whole implementation compartment. And yet another side of that coin is how it is all hijacked essentially by marketers, the very rationale that goes with what it is, what it is good for, and how to use and/or learn it. Happy you who are fine to keep playing that game.
think the idea of an Prolog engine is the wrong
approach. The idea should be a Prolog language,
like the ISO core standard.
SWI-Prolog did everythingSWI-Prolog remains one of the best available of the non-commercial ones: it does start failing under heavy duty, plus indeed in some even critical areas it has been informed by decisions I couldn't agree less with, but it's comparatively a reasonably decent product, and comes with tons of libraries, a module system and an online package system, support for code documentation and testing, native extensibility, constraint programming, and what-not: the whole shenanigan pretty much, and if it had a JS runtime proper it would super. We are lucky that it exists,
to be different and better from the ISO core standard.
And ended up with a bloathed engine that runs
non-portable code. I did a little bit the same error
with formerly Jekejeke Prolog, it did not pay attention
to apply the KISS principle:
https://en.wikipedia.org/wiki/KISS_principleThe level of incompetence in our field is shocking:
If you develop againstThat was not even true once upon a time, that one can just develop for a "language". Then again, happy who is simply oblivious: maybe.
an idea of a Prolog language and not against an idea of
a Prolog engine, chances are higher that stay agile and
can easily switch Prolog engines, and protect your investment.
Les messages affichés proviennent d'usenet.