Luvit is base on libuv, the same scalable event loop that powers nodejs.
 if anything, it will scale better than node since the vm (luajit vs v8) is
more powerful and more efficient.  The main reason that luvit hasn't
already overtaken node in the web space is the simple fact that it's not
JavaScript and web developers love JavaScript.

I don't see any technical issues that would block it from becoming a better
version of node.  The coroutines in lua are especially interesting because
they solve one of the largest problems in node (callback spaghetti).  You
can write blocking code without blocking the event loop.  In other words,
you can have the performance and scaleability of the non-blocking event
loop while still writing the majority of your code in simple blocking style
without manual continuation passing syntax.

The other practical thing stopping luvit from replacing node is the
difference in popularity and third-party libraries.  The lit system is
brand new and npm has been around for years.  We need a better interface to
lit to search what has been published.  We need better docs for luvit and
we need more libraries written.

The technical base is solid, the maturity is lacking.


On Fri, Apr 17, 2015 at 3:54 AM, Lionel Duboeuf <[email protected]>
wrote:

> hello again,
>
> I've noticed in luvit blog, that Luvit fits well in embedded and cloud
> monitoring uses cases.
> I was wondering if one day, Luvit will have enough good fondations to
> become a NodeJs, Nginx or other challenger in term of scalability for huge
> traffic site ?
>
>
>  --
> 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.
>

-- 
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.

Reply via email to