When I first looked into luvit I thought it would be perfect for a project I had always wanted to tackle right up until I realized it was a tight knit system not a library.
the reason I wanted to use luvit was because I wouldn't have to fail at tieing into libuv myself nor would I have to implement my own networking stack on top as luvit already had what I wanted. but trying to decouple those interfaces from the run-time proved too difficult at the time so I've mostly just been following it's development ever since hoping a topic like this would come up. personalty I was hoping dropping in luvit and a libuv blinding would "just work" in an existing luajit run-time. the existing luvit runtime couples system could certainly continue to exist but surely there is way to pull luvit away from it's Luv runtime and still keep a majority of it's functionality. -- 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.
