`README.md`: Talk about maturity of implementation in a more high level way

[sidkshatriya]

Thanks for the impressive README.md which comprehensively and transparently lists the status of the scryer-prolog implementation and the roadmap.

I think it would help prospective users to know what exactly can be done today with Scryer Prolog. Otherwise they might have the tendency to tell themself, "Hey, I'll only be back when this is more mature."

This might make it even more difficult to bootstrap a user base when everybody is just waiting for Scryer to mature.

Some examples of useful sign-posts:

• "We pass X% of the (ISO/xyz/etc) test suite. Here is a (link) to the passing and failing results"
• "These are some of the biggish Prolog programs that can run Scryer Prolog today: 1. ... 2. ..."

and so on...

It may be that you're not ready yet to make these statements, but if you are, then it would be very useful !

[mthom]

Sorry I took so long to address this. It's a good idea! There are projects from @triska, @aarroyoc and @josd that already make serious use of Scryer, just off the top of my head (sorry if I've left anyone out!).

[sidkshatriya]

Yes it would be great if the README.md lists some projects making serious use of Scryer.