6 ms·

This is a great blog post. Concise, lacking fluff or extraneous prose, it gets right to the point, presents the primary-source reference and then gets right to

This is a great blog post. Concise, lacking fluff or extraneous prose, it gets right to the point, presents the primary-source reference and then gets right to the solution. A bit of editorializing in the middle but that's completely allowed when writing this tightly. Well damn done, OP. And also it's great information that I - like I'm sure many of you - also never noticed. THANK YOU!

isoprophlex 4y ago
Well, I don't know, I kinda miss the human angle. I'd have loved to first read six paragraphs about how the author's grandmother raised them on home grown threads and greenlets :^)
- nickjj 4y ago
  > I'd have loved to first read six paragraphs about how the author's grandmother raised them on home grown threads and greenlets. With recipes, often times your problem is you want to learn how to make something where having the steps listed out is the most important thing. The story behind the recipe isn't important to solve your problem but for tech the story around the choice is important. Often times the "why" is really important and I really like hearing about what led someone to use something first. Often times that's more important or equally as important as the implementation details. It wouldn't make sense for this post given its title but if someone were making a post about why they chose to use async in Python I'd expect and hope that half of the post goes into the gory details of how they tried alternatives and what their shortcomings were for their specific use cases. That would help me as the reader generalize their post to my specific use cases and see if it applies.
  - bialpio 4y ago
    Off-topic but the life story is there to make them eligible to be protected by copyright. IANAL. Source: https://copyrightalliance.org/are-recipes-cookbooks-protected-by-copyright/ https://copyrightalliance.org/are-recipes-cookbooks-protecte...
    - flandish 4y ago
      Interesting. I always thought it was search engine optimization.
      - aidenn0 4y ago
        SEO is definitely a big part of it; Google penalized pages where people closed or navigated away quickly.
        fbdab103 4y ago
        I immediately bounce from those Stackoverflow clones that keep appearing up at the top of searches. So, I am wondering how much this is still weighted in the scores.
        jonas21 4y ago
        You might. But many people don't. They just want an answer and don't care if it's a clone or not.
        deleted 4y ago
        [deleted]
        gdprrrr 4y ago
        https://github.com/quenhus/uBlock-Origin-dev-filter https://github.com/quenhus/uBlock-Origin-dev-filter
        kevin_thibedeau 4y ago
        Leaked Google code: if(bounced && hosts_doubleclick_ads) pagerank++;
      - water-your-self 4y ago
        Its engagement optimization. Adsense pays more if you spend more time on the page
  - rendaw 4y ago
    For recipes, it also signals effort and provides a hint about quality. There's a lot of low effort, broken, "would anyone enjoy eating this?" recipes out there dumped on recipe sites. A few pages of text says that the author thought the recipe was at least worth that amount of effort, and usually confirms that the author thinks the recipe is at least as good as X other recipes, etc.
  - toyg 4y ago
    It's not about recipes and tech blogs. It's about how American journalists have been taught to write, ever since the days of Capote and Hemingway. Everything else flew from there. As an European, this is painfully evident every time I read something from a US journalist: I have to fast-forward through several paragraphs of useless "human angle" before I can get to the actual meat of the article. Unfortunately the rot is spreading further and further every year.
mgsk 4y ago
What does this add this isn't already right there in the documentation?
- Jtsummers 4y ago
  It draws attention to a problem that a lot of people have created for themselves by not reading the documentation (or not recalling it if they read it). I guess the author could have just linked the documentation but then they couldn't have added the additional context of the github search demonstrating how common it is.
  - newaccount74 4y ago
    I must have looked through the docs for create_task a dozen times while trying to figure out how async/await works in Python but still managed to overlook this part.
    - edflsafoiewq 4y ago
      That is unsurprising. It was first added as a brief note only in 3.9, and expanded to its present length only in 3.10.
    - wnolens 4y ago
      Same.
- nkrisc 4y ago
  If there was nothing to add then there wouldn’t be loads of projects on GitHub making exactly this mistake.
- klyrs 4y ago
  The author doesn't go into much detail on that point: this warning should be present in documentation of many Python libraries that use create_task and return the result to the user unless that library stores those tasks in a collection as is recommended -- at which point the library author had better roll their own garbage collection!
deleted 4y ago
[deleted]

isoprophlex 4y ago

Well, I don't know, I kinda miss the human angle. I'd have loved to first read six paragraphs about how the author's grandmother raised them on home grown threads and greenlets :^)

nickjj 4y ago
> I'd have loved to first read six paragraphs about how the author's grandmother raised them on home grown threads and greenlets. With recipes, often times your problem is you want to learn how to make something where having the steps listed out is the most important thing. The story behind the recipe isn't important to solve your problem but for tech the story around the choice is important. Often times the "why" is really important and I really like hearing about what led someone to use something first. Often times that's more important or equally as important as the implementation details. It wouldn't make sense for this post given its title but if someone were making a post about why they chose to use async in Python I'd expect and hope that half of the post goes into the gory details of how they tried alternatives and what their shortcomings were for their specific use cases. That would help me as the reader generalize their post to my specific use cases and see if it applies.
- bialpio 4y ago
  Off-topic but the life story is there to make them eligible to be protected by copyright. IANAL. Source: https://copyrightalliance.org/are-recipes-cookbooks-protected-by-copyright/ https://copyrightalliance.org/are-recipes-cookbooks-protecte...
  - flandish 4y ago
    Interesting. I always thought it was search engine optimization.
    - aidenn0 4y ago
      SEO is definitely a big part of it; Google penalized pages where people closed or navigated away quickly.
      - fbdab103 4y ago
        I immediately bounce from those Stackoverflow clones that keep appearing up at the top of searches. So, I am wondering how much this is still weighted in the scores.
        jonas21 4y ago
        You might. But many people don't. They just want an answer and don't care if it's a clone or not.
        deleted 4y ago
        [deleted]
        gdprrrr 4y ago
        https://github.com/quenhus/uBlock-Origin-dev-filter https://github.com/quenhus/uBlock-Origin-dev-filter
        kevin_thibedeau 4y ago
        Leaked Google code: if(bounced && hosts_doubleclick_ads) pagerank++;
    - water-your-self 4y ago
      Its engagement optimization. Adsense pays more if you spend more time on the page
- rendaw 4y ago
  For recipes, it also signals effort and provides a hint about quality. There's a lot of low effort, broken, "would anyone enjoy eating this?" recipes out there dumped on recipe sites. A few pages of text says that the author thought the recipe was at least worth that amount of effort, and usually confirms that the author thinks the recipe is at least as good as X other recipes, etc.
- toyg 4y ago
  It's not about recipes and tech blogs. It's about how American journalists have been taught to write, ever since the days of Capote and Hemingway. Everything else flew from there. As an European, this is painfully evident every time I read something from a US journalist: I have to fast-forward through several paragraphs of useless "human angle" before I can get to the actual meat of the article. Unfortunately the rot is spreading further and further every year.

mgsk 4y ago

What does this add this isn't already right there in the documentation?

Jtsummers 4y ago
It draws attention to a problem that a lot of people have created for themselves by not reading the documentation (or not recalling it if they read it). I guess the author could have just linked the documentation but then they couldn't have added the additional context of the github search demonstrating how common it is.
- newaccount74 4y ago
  I must have looked through the docs for create_task a dozen times while trying to figure out how async/await works in Python but still managed to overlook this part.
  - edflsafoiewq 4y ago
    That is unsurprising. It was first added as a brief note only in 3.9, and expanded to its present length only in 3.10.
  - wnolens 4y ago
    Same.
nkrisc 4y ago
If there was nothing to add then there wouldn’t be loads of projects on GitHub making exactly this mistake.
klyrs 4y ago
The author doesn't go into much detail on that point: this warning should be present in documentation of many Python libraries that use create_task and return the result to the user unless that library stores those tasks in a collection as is recommended -- at which point the library author had better roll their own garbage collection!

deleted 4y ago

[deleted]