So, PROLOG people, how excited should anyone be about this? This vs SWI, Visual Prolog, Prolog in a LISP like Allegro, or alternatives like Mercury. Is this significant in general or just for their community of users?
I'm first of all excited by the fact that this made first page on HN. I didn't realise there was that much interest in Prolog news (as in more than two or three people). Also, having more open-source Prolog engines is a very good thing, both for the language and for the project itself. For the project, it's good because it makes it easier for a community to grow around it. Swi has benefited enormously from its popula…
Or even between versions of the same implementation. E.g., I know of one project that sticks with SICStus 3, because in SICStus 4 findall/3 removes blocked goals from copied variables. This system relies quite heavily on blocked goals and working around this change turned out to be too expensive.
(If I recall correctly ;).)
Another example is SWI Prolog diverging from the ISO standard in version 7 (e.g. double quoted strings are now a type on their own, rather than a list of character codes). Luckily, there is a --traditional flag for older code.
In both cases, there are good reasons for the changes, but it makes portability hard.
Edit: wanted to add that this is not intended to be a critique of these particular (great) implementations of Prolog.