> > But if you're wondering why Mojo::IOLoop is written this way, the > explanation is simple: it's not perfect, but that's not a big deal (because > nobody suggested a better implementation) and current implementation works > somehow. >
I can't agree with this at all. The current implementation of Mojo::IOLoop serves its purpose very well, and we know exactly why it works. -- sebastian -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
