Is swi-prolog being used in domains that requires multi-threading at scale?
I think it would be very worthwhile to present case studies, and design patterns for Prolog in enterprise settings, where such features are a must.
Analogous to like those J2EE enterprise patterns – whatever is currently the approach of choice (serverless? microservices?), etc.
It seems to me that in particular in the enterprise environment prolog should shine … and could perhaps further motivate adoption.
I am saying this due to a discussion I had with a solution vendor were prolog was quickly dismissed out of hand for supporting enterprise systems – and (enterprise) Java was seens as the choice at hand. And, i think, its not because of capability but due to perception.