These are all valid concerns.  The biggest luvit user I know of is the
Rackspace Monitoring Agent.  I've heard of a few startups using it around
the world and I think the torch project still uses the luv bindings.

As far as benchmarks, I believe someone started writing a luvit version
recently.  I haven't spent a lot of time trying to optimize luvit for
synthetic benchmarks, but last time I tried (years ago), it was quite a bit
faster than node.js.


On Thu, Jun 23, 2016 at 7:56 AM, Marcio Andrey Oliveira <
[email protected]> wrote:

> Some time ago I discovered lapis when I was looking into TechEmpower
> Framework Benchmarks.
>
> I got interested in it and then I start learning a bit of lua (and
> moonscript). Then I came across luvit. I loved it too.
>
> Are you planning to participate in TechEmpower's Benchmarks? I think it
> would help both to show how fast it really is in an independent test
> (lapis, for instance, probed to be way faster than node.js - at least at
> those tests) and to call attention from people that have never heard of it.
>
> Also, I'd like to know which are the biggest sites powered by luvit.
>
> Lua seems a very interesting language and both luvit and lapis seems so
> cool, but I have problems to start using it in commercial projects because
> it seems their user base are too small and no big players are using it (so,
> how to convince clients / bosses if I myself wonder how long will them last
> and how easy will I get support for problems / bugs?)
>
> Notice that I'm not criticizing your efforts. I'm just telling you my
> concerns.
>
> Regards.
>
> --
> 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