Very relatable post. Isn&#x27;t NLTK primarily a teaching &#x2F; demonstration tool though?<p>I just checked their website and the claim of <i>&quot;NLTK is a leading platform for building Python programs to work with human language data...  a suite of libraries for classification, tokenization, stemming, tagging, parsing, and semantic reasoning&quot;</i> does sound a little odd. But I think everyone in the industry knows NLTK&#x27;s place and purpose -- you practically cannot avoid finding out quickly. NLTK&#x27;s scope is clearly too broad to be meaningfully cutting edge at any one thing.<p>New libraries and implementations will always have an advantage. It&#x27;s easier to tout &quot;simplicity and leanness&quot; when you don&#x27;t have to carry over all the baggage and backward compatibility accumulated over the years.<p>For that reason, an occasional &quot;complexity reset&quot; is expected, and if a library would not or can not do it, another library will. Will SpaCy&#x27;s fate be different, 10 years down the road?