I agree. With the blocking style I can do things with traditional protocols like HTTP FastCGI FTP very easy. But these protocols focus on one thing at the same time. Now I often need to push messages to the many clients and also accept commands from clients from one connection such as a WebSocket connection. With blocking APIs I have to create as many coroutines as clients to simply push a message. In this situation callback style saves more memory. But to do logical job I need synced style that shows me the logic clearly and avoids me making mistakes. With both styles luvit will be able to fit more proposes than node.
I have taken great advantages from Lua's simple APIs and clear manual. And node's APIs made me feel difficult to learn it. But I still think node's event emitter interface is a great design. I don't need packing the app into one package because I often switches between GNU/Linux and Windows. -- You received this message because you are subscribed to the Google Groups "luvit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
