Sort of meta, but pretty much every article related to a google service will get a comment like this. It seems HN goes through these cycles where something gets

Sort of meta, but pretty much every article related to a google service will get a comment like this. It seems HN goes through these cycles where something gets a lot of attention and then every article even tangentially related gets at lease one boiler plate comment like this. It happened a lot a while back when "questions as headlines" was the hot topic to jump on. There'd always be that one person that'd be there to post the wikipedia link to the article about it. I see it when there's articles about animal intelligence. You'll get someone who posts that Hitchhiker's quote about dolphins. It's boring and a lot of times, those comments end up at the top of the thread. Now to address your comment about Django. It supports Django, just fine[0]. The problem hasn't been with supporting Django, but supporting the Django ORM and that's merely because of the GAE data store. And that wasn't ever limited to GAE, you couldn't use it with any non relational data store. That problem seems to have been mitigated by the existence of django-nonrel[1], however. [0] https://developers.google.com/appengine/articles/django https://developers.google.com/appengine/articles/django [1] https://github.com/django-nonrel https://github.com/django-nonrel