zlacker

Why is that? Ultimately someone has to work on the tooling for any project. If you're working in a group in particular, you can have different people working on different parts of the project. If you need a type system, you can have one programmer write it and maintain it, or be the product owner whatever the terminology is these days, then everyone else can use the type system and not have to worry about it any more.

To be clear, there are only some tools, or let's say abstractions, that you need to implement on your own. The good thing about Prolog is that it has a very mature ecosystem of libraries and packages that you can pick off the shelf and work with immediately. Although that is mostly true for SWI-Prolog, where most of those libraries are found. You normally have to write some translation layer to port them over to a different Prolog- and that is totally a PITA. But there's no reason not to use SWI-Prolog, which is free as in speech and as in beer.

For example, SWI-Prolog has http libraries that have everything you need to set up a web app, using Prolog itself as the database and the back-end language both- it's like a LAMP stack except the stack is LP: Prolog running on Linux:

https://us.swi-prolog.org/FAQ/PrologLAMP.md

I reckon the only reason this is not widely used in the industry is because web devs, like everyone else, don't have the time and energy to learn a whole new language, especially one so scary as Prolog. Quoting from the link above:

Our final problem is the lack of masses of Prolog programmers one can easily hire.