Comments by "miraculixx" (@miraculixxs) on "ArjanCodes" channel.

  1.  @superfliping  tell me you have never used Python without telling me. LOL your post is hilarious
    10
  2. This. People are wayyyy overestimating the benefits of GIL free multithreading.
    6
  3.  @superfliping  python's energy use is dwarfed by AI power needs. Regardless, Python's alledged energy use is a non-issue. For comparison look at all the idling CPU energy use.
    5
  4. "The GIL has been holding back Python for years" - that's just not true. Multithreaded numeric computations are done by libraries like numpy, and they have been multithreaded since ever. The GIL does not apply. Stop spreading this false narrative.
    2
  5. It was not a security issue. It is a management issue. Perhaps MBAs should not run engineering orginizations.
    2
  6. Exactly. And that's why Cython exists.
    2
  7. This 💯
    2
  8. Legally required
    2
  9. It won't. The GIL is not limitting openstack.
    1
  10.  @edweard  that's not the point. Also numpy is not written in C.
    1
  11.  @edweard  It is 60% Python, 35% C, 2.5 C++, 1% Cython. The remainder of the code base is in various languages.
    1
  12.  @edweard  because it is irrelevant in practice. In practice I want to use Python bc it is easy to use, but I also want high performance in my computations so I use numpy, a Python library, and I get full utilization of all CPU cores (if the math allows it). I don't care what language the library is written in, or if it applies magic, or whatever.
    1
  13.  @edweard  🤦‍♂️
    1
  14. ​​ @AustinWitherspoon  famous last words 😂 "shouldn't" does a lot of lifting in that sentence. The JVM took nearly a decade before it had a stable, as in predictably working memory & threading model. The Python core devs are way in above their heads if they think it is as easy as adding a few locks here and there. There will be a ton of unexpected side effects of this change once people start using it in production code, and each one will be a nightmare to debug. I am firm in my opinion that GIL free Python the worst idea since sliced bread. In fact Python with the GIL has been so successful not least due to the fact that it enforced a well designed approach to parallel code (either using mp or extensions), so that the hard stuff was left to experts, while the core language is easy to use. We'll now start seeing people blame Python for being too complex when in fact it is not the language but the problem solving approach which is flawed (or the way it is programmed). Modern CS has mostly agreed that the best way to build scalable systems is by having no shared state and to communicate soley by messages between processes. The whole world is moving in that direction, except Python now suddendly wants to be the cool kid on the block by going back at least 1 decade 😢 /rant
    1