# Encouraging industry about Prolog

**URL:** <https://swi-prolog.discourse.group/t/encouraging-industry-about-prolog/1106>\
**Category:** Split Topic\
**Created:** [August 23, 2019, 2:21pm UTC](https://swi-prolog.discourse.group/t/encouraging-industry-about-prolog/1106 "2019-08-23T14:21:51Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\
**Post date:** [August 24, 2019, 7:49am UTC](https://swi-prolog.discourse.group/t/encouraging-industry-about-prolog/1106/4 "2019-08-24T07:49:07Z")

</div>

> [@Curious: How does Prolog "Byte code" compare to .NET IL (and some thoughts about enterprise ready systems)](https://swi-prolog.discourse.group/t/curious-how-does-prolog-byte-code-compare-to-net-il-and-some-thoughts-about-enterprise-ready-systems/1101/23):
>
> One thing that in my opinion Python did exceedingly well and I don’t quite see for SWI-Prolog is their “Tutorial”.

I fully agree. On the other hand, you might be pointing at a solution. There is plenty of material out there on many subjects at many different levels. Maybe something as simple as a reading guide could improve the situation quite a lot. Possibly we can do that as a joined effort here (e.g., on the wiki channel). Steps to take:

- Find the links
- Characterize them (topic, level, maturity, audience, …)
- Assemble (a) reading path(s)
- Merge them? Involves copyright …

Of course, the Tutorials menu on the home page is already a start.

---

_[View the full topic](https://swi-prolog.discourse.group/t/encouraging-industry-about-prolog/1106)._