2 ms·
The problem with your claims is that once you start “debugging”, it gets complicated quickly. You’ll have to gain an intuition of how the language actually tri
by hnfong 4y ago
The problem with your claims is that once you start “debugging”, it gets complicated quickly.
You’ll have to gain an intuition of how the language actually tries so solve the problem under the hood.
sometimes the problem you encounter doesn’t match the capabilities of the language, and then you’ll have to state the problem in a roundabout way to coax the language to do what you intended.
It’s probably great for the small number of toy problems that it was designed to solve, but in my limited experience prolog doesn’t do well on real world problems that have all sorts of edge cases and dirty inputs.
- forgetfulness 4y agoYou see this often in the data side of things, we delegate very laborious or very complicated tasks to powerful the powerful engines behind Postgres, BigQuery, Spark, and the like, and while they provide you with a high level interface that make common tasks very convenient, mastery can take years as you have to study the architecture and implementation behind them. It's a huge investment on your end to do that, and people do it readily because the return is being able to process datasets of sizes and complexity that you otherwise wouldn't be able to. People haven't found it to be a good investment in their time to commit themselves to Prolog's engine.