<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ubernostrum</author><text>Channels will get there. It just wasn&amp;#x27;t quite ready on time for 1.10. Hopefully it will be ready on time for 1.11, and then it&amp;#x27;ll ship in Django.</text><parent_chain><item><author>orf</author><text>Shame about Channels, but I see the logic in not including it. Django is pretty awesome as a backend, and while it&amp;#x27;s not a &amp;#x27;cool&amp;#x27; framework anymore (I feel old!) it&amp;#x27;s amazing for writing back-office applications.&lt;p&gt;I use it as an API backend with Django-rest-framework. The advantage is you get ridiculous amounts of packages that all integrate with Django that does pretty much anything you want. Also the ORM doesn&amp;#x27;t suck now so that&amp;#x27;s a bonus.</text></item></parent_chain></comment><story><title>Django 1.10 released</title><url>https://www.djangoproject.com/weblog/2016/aug/01/django-110-released/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>hrayr</author><text>Why a shame? What would Channels buy you if it were included into the framework?&lt;p&gt;I would love to see Django split up into smaller official external packages and repackaged as two or three different official starter packs (Traditional, API, SPA, etc.) with each containing a different set of packages that make sense (DRF, Channels, Models, Views, Forms, etc.).&lt;p&gt;I know this goes against the current &amp;quot;Batteries are included&amp;quot; model, but why can&amp;#x27;t we treat Django as the standards body, and the various starter packs as the more targeted &amp;quot;batteries are included&amp;quot; frameworks.</text><parent_chain><item><author>orf</author><text>Shame about Channels, but I see the logic in not including it. Django is pretty awesome as a backend, and while it&amp;#x27;s not a &amp;#x27;cool&amp;#x27; framework anymore (I feel old!) it&amp;#x27;s amazing for writing back-office applications.&lt;p&gt;I use it as an API backend with Django-rest-framework. The advantage is you get ridiculous amounts of packages that all integrate with Django that does pretty much anything you want. Also the ORM doesn&amp;#x27;t suck now so that&amp;#x27;s a bonus.</text></item></parent_chain></comment><story><title>Django 1.10 released</title><url>https://www.djangoproject.com/weblog/2016/aug/01/django-110-released/</url></story>