4 ms·

To get conversations started.. Lapis[1] on Openresty[2] is one of the most simplest, documented, and performant full web framework stack out there, yet almost

To get conversations started.. Lapis[1] on Openresty[2] is one of the most simplest, documented, and performant full web framework stack out there, yet almost no one knows it. Hello World Open[3] - 2.5k teams, only 17 ( < 0.7% ) teams used Lua. This is an open competition, which means people can use their favorite language instead of Java, and less than 1% uses Lua. The lua community really need to start doing something about this. 1. http://leafo.net/lapis/ http://leafo.net/lapis/ 2. http://openresty.org/ http://openresty.org/ 3. https://helloworldopen.com/teams https://helloworldopen.com/teams

_pmf_ 12y ago
> The lua community really need to start doing something about this. Why? A small community has advantages, too.
- loup-vaillant 12y ago
  Could you name three?
  - otikik 12y ago
    - Can make backward-incompatible changes (see: Javascript, Python) - Less trolls & nasty people in general. - All the advantages of a niche language (I got my current job because no one else in my country knows Lua :P).
    - catwell 12y ago
      Advantage 1 is the main reason why today's Lua is not as complex as today's JavaScript, despite Lua being older.
      - ANTSANTS 12y ago
        It also significantly helped that Lua's main users could easily use an older implementation if something they depended on/didn't feel like fixing was removed. In contrast, breaking backwards compatibility for Javascript would be unthinkable. OTOH, there is real fragmentation between 5.1 and 5.2, so not even Lua is immune to the downsides of breaking backwards compatibility.
catwell 12y ago
I wrote Lua Toolbox in Lapis mostly to experiment with it. I think the framework has a lot of potential but I have two main issues with it: 1) It is written in Moonscript, which makes understanding its internals harder for Lua programmers. On the application side, Lua support used to be a second thought but now I think you can do almost everything without writing a single line of Moonscript. 2) It is tied to OpenResty. This is both a good and a bad thing, because it means you cannot use several of the existing libraries in the Lua ecosystem. If you are looking for alternatives, a new framework called Sailor was presented at Lua Workshop 2014 (slides: http://www.lua.org/wshop14/Dalcol.pdf http://www.lua.org/wshop14/Dalcol.pdf)
berdario 12y ago
Lua has 15 teams (not 17, since it's not a lang query, but a full text search) by looking up `document.getElementsByTagName('tbody')[0].children.length` after looking up a language (on this page: https://helloworldopen.com/teams https://helloworldopen.com/teams )... for all the not-so-popular languages: Lua: 15 Haskell: 75 F#: 13 Rust: 4 Clojure: 94 Scala: 82 Erlang: 6 Also, I thought these 2 would've got more teams: Perl: 2 coffeescript: 28 I'd say that Lua is not doing so bad after all

_pmf_ 12y ago

> The lua community really need to start doing something about this. Why? A small community has advantages, too.

loup-vaillant 12y ago
Could you name three?
- otikik 12y ago
  - Can make backward-incompatible changes (see: Javascript, Python) - Less trolls & nasty people in general. - All the advantages of a niche language (I got my current job because no one else in my country knows Lua :P).
  - catwell 12y ago
    Advantage 1 is the main reason why today's Lua is not as complex as today's JavaScript, despite Lua being older.
    - ANTSANTS 12y ago
      It also significantly helped that Lua's main users could easily use an older implementation if something they depended on/didn't feel like fixing was removed. In contrast, breaking backwards compatibility for Javascript would be unthinkable. OTOH, there is real fragmentation between 5.1 and 5.2, so not even Lua is immune to the downsides of breaking backwards compatibility.

catwell 12y ago

I wrote Lua Toolbox in Lapis mostly to experiment with it. I think the framework has a lot of potential but I have two main issues with it: 1) It is written in Moonscript, which makes understanding its internals harder for Lua programmers. On the application side, Lua support used to be a second thought but now I think you can do almost everything without writing a single line of Moonscript. 2) It is tied to OpenResty. This is both a good and a bad thing, because it means you cannot use several of the existing libraries in the Lua ecosystem. If you are looking for alternatives, a new framework called Sailor was presented at Lua Workshop 2014 (slides: http://www.lua.org/wshop14/Dalcol.pdf http://www.lua.org/wshop14/Dalcol.pdf)

berdario 12y ago

Lua has 15 teams (not 17, since it's not a lang query, but a full text search) by looking up `document.getElementsByTagName('tbody')[0].children.length` after looking up a language (on this page: https://helloworldopen.com/teams https://helloworldopen.com/teams )... for all the not-so-popular languages: Lua: 15 Haskell: 75 F#: 13 Rust: 4 Clojure: 94 Scala: 82 Erlang: 6 Also, I thought these 2 would've got more teams: Perl: 2 coffeescript: 28 I'd say that Lua is not doing so bad after all