Currently luvit is a self-contained binary complete with luajit, zip asset handling, openssl, miniz, and a variety of other tools baked in. It has it's own require system that works like node.js and not like lua. The lit package manager works off the assumptions of this require system and has it's own package repository apart from luarocks.
I could repeat all the reasons why we made these decisions, but as time goes on, I'm starting to wonder if I was catering to an audience that doesn't exist. Most JS developers could care less about Luvit because it's not JavaScript. most Lua developers don't like it because it doesn't play nice with existing tools and ecosystems. I would love to start a conversation about two things: 1. Are you even interested in a version of luvit that works with normal lua binaries? 2. What would such a luvit look like? Would we keep lit and the custom require system? How would we continue to support the current luvit system? -Tim Caswell -- 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.
