4 comments

  • simonw 1 hour ago
    This is an intimidating amount of code! 12,303 lines of C and 244,740 lines of Python, which looks to be a ton of monkeypatching plus huge amounts of test code.

    Only one commit added all of that, just two hours ago.

    The published numbers are impressive, but its hard to evaluate how much trust can be put in a project of this complexity at this early stage.

    • CamouflagedKiwi 36 minutes ago
      > its hard to evaluate how much trust can be put in a project of this complexity at this early stage.

      I don't know, I'm not finding it hard to evaluate that at all.

      I've had bad enough experiences with gevent in the (now fairly distant) past, and that's a well-established project, just a subtle one with a large blast radius. This has all of those problems, plus is _much_ larger and I don't think can possibly have been tested as widely as I would want. I get maybe there's a lot of test code, but I think this kind of thing you only really know when the rubber meets the road.

    • tfrancisl 53 minutes ago
      250k lines of code in one commit is reason enough to disregard the project entirely, IMO. Vibe code if one wants, but that is just madness...
  • ksdme9 2 hours ago
    How does this compare with gevent?
    • korijn 1 hour ago
      Exactly this is very reminiscent
  • hsnewman 1 hour ago
    Why not just use Go?
    • foxygen 1 hour ago
      Because you are have an existing app in Python. Because you need some library that is not available in Go. Because you prefer Python. All are valid reasons.
      • vorticalbox 5 minutes ago
        then why not just use threads/processes in python?
        • foxygen 4 minutes ago
          Because they are not the same as Go-style green threads/coroutines?
    • 7bit 44 minutes ago
      Someone desires attention ..
  • Onavo 1 hour ago
    Is Python about to have its Project Loom moment?