4 ms·
Lapis: A Web Framework for Lua
- prezjordan 2y agoI find Lua so dang pleasing to look at
- christophilus 2y agoI agree, but I miss static types. Has anyone here ever used Nelua[0]? [0] https://nelua.io/ https://nelua.io/
- iTokio 2y agoLuau from Roblox is gradually typed and has great support
- stefanos82 2y agoI do and I'm quite pleased with it.
- otikik 2y agoTeal, man
- ngrilly 2y agoI read too fast and thought you wrote something like "I like Lua so dang please look at it" :)
- CableNinja 2y agoYea, but who starts an array index at 1!?!?
- deleted 2y ago[deleted]
- jecel 2y agoAlgol 68, APL, AWK, COBOL, Fortran, Julia, Mathematica and Wolfram Language, MATLAB and Octave, PL/I, RPG, R, Smalltalk, etc (including Lua).
- raytopia 2y agoLapis is the framework that itch.io uses. [1] It also uses MoonScript [2] as the programming language which was also written by the creator of itch.io/Lapis. 1. https://leafo.net/posts/introducing_itchio.html https://leafo.net/posts/introducing_itchio.html 2. https://moonscript.org/ https://moonscript.org/
- natrys 2y agoOne thing people might need to keep in mind is that Lapis isn't particularly interested in adding features that itch.io doesn't need. Been almost a decade since websocket support was requested e.g. https://github.com/leafo/lapis/issues/233 https://github.com/leafo/lapis/issues/233
- xrd 2y agoWhat about SSE? If that's there, then I'm happy without websockets.
- biftek 2y agoLooks like you can bypass the lapis renderer and use ngx.print() and ngx.header() to control the response yourself Look under skip_render here: https://leafo.net/lapis/reference/actions.html#render-options https://leafo.net/lapis/reference/actions.html#render-option...
- CaptainOfCoit 2y agoWhat in that issue says that Lapis would only implement things needed for itch.io? Seems there is a off-hand comment by a non-contributor that it seems to be like that, but hardly a confirmation it actually is like that.
- dubcanada 2y agoThis is completely incorrect comment. There is no rejection of any form, it is logical that the main developer who used it to build itch.io is not going to put in the effort to do something they don't care about. But the product is open source, anyone can write that functionality, and I am sure it would be accepted. What you are complaining about is a developer who is not willing to put in free effort for a feature you care about, but are not willing to contribute to.
- pfd1986 2y agoGreat name! (Portuguese word for 'pencil')
- jszymborski 2y agoHuh, here I was just assuming it was a reference to "lapis lazuli" but seeing as lua is Portuguese for moon, "pencil" makes most sense here. Thanks!
- qsort 2y agoIt's Latin for "stone". Also used in Italian as a regional/alternative word for "pencil".
- VWWHFSfQ 2y agoWe started out using lapis in nginx but unfortunately had to abandon it because it basically takes away all the power of using regular location {}. You have to mount your whole app under like location / which is lame for an nginx-native framework. It's got some nice utilities that we use, but we ended up just using regular location {} routes each with their own content_by_lua code block and none of the lapis routing/handler stuff.
- pacifika 2y agoWhy is that a problem?
- VWWHFSfQ 2y agoBecause we want to use rewrites, jumps, named handlers, etc. in nginx too. But you can't do that once you delegate all your routing to Lua. At that point all nginx is doing is a socket event loop. We weren't happy to lose all the power of nginx just to use a framework.
- binary132 2y agoI would think you would treat the OpenRESTy component as just an executable binary application server just as you would with any other webservice, and put your nginx stuff in front of it, just like you would with any other webserver's front end lb. I agree that it does sound nice to handle it as another component in a regular nginx config, but it doesn't sound like a dealbreaker. Just treat the nginx stuff as incidental to the implementation and it seems like it would be no big deal.
- xrd 2y agoDo you know if you can use lapis to proxy to a backend, essentially getting the benefits of nginx proxy, but perhaps allowing you to layer an authz/authen handler on top using lapis? Thanks for your comment.
- leafo 2y agoI suppose I haven't really fully considered this use case, but... There's no requirement to put your entire app in a location / {} block. You can freely use as many location blocks as you want, and those that you want to be rendered by Lapis can call serve to the app as normal. eg. location = /exact-match { content_by_lua 'require("lapis").serve("app")'; } location /directory-match { content_by_lua 'require("lapis").serve("app")'; } Keep in mind pattern matching will still happen in the app: You will need to define the routes handled by Lapis within the definition of the Lapis app. Why is it done this way? Primarily, for named routes. Typically you want to be able to generate the URL of a resource within your app's code, so by having routes defined in Lua you can easily reference those. Secondly, easy parameter parsing and the parameter validation. > It's got some nice utilities that we use, but we ended up just using regular location {} routes each with their own content_by_lua code block and none of the lapis routing/handler stuff. Although it's very possible to pick and choose what components to use, keep in mind that the `serve` function does some important work with connection pooling. If you are using any query related functionality outside of a dispatch it will open and close connections per request, which is not ideal for performance.
- xena 2y agoI used to use Lapis for my website, it is a lovely framework. For a long time it was what I reached for when I needed something like Rails but didn't want to deal with Rails. Been thinking about using Moonscript for some Kubernetes templates, I love its table creation shorthand.
- deleted 2y ago[deleted]
- xrd 2y agoNot knowing much about MoonScript and only knowing a tiny bit of Lua, does anyone have a recommendation on which is "better" if you are starting from where I'm at with these languages? MoonScript looks class based; I avoid classes like the plague in JavaScript because of "this" but maybe that is the wrong starting assessment?
- qgc 2y agoFennel is a neat Lisp-flavored Lua language that I've been using for around 2 years now.
- _heimdall 2y agoI wouldn't run from classes just because JS historically has, though coming from JS I'd lean towards lua for a more familiar function calling syntax.
- elpocko 2y agoMoonScript supports classes via keyword, while in Lua you have to implement them yourself. That's about it. You can ignore them, even more so than in JS. MoonScript is dead anyway. Check out yuescript instead: https://github.com/pigpigyyy/Yuescript https://github.com/pigpigyyy/Yuescript
- hnax 2y agolua-classy (https://github.com/siffiejoe/lua-classy https://github.com/siffiejoe/lua-classy) works like gem and is fast!
- elpocko 2y agoIt's 10x larger than it needs to be, and seems to do a lot of unnecessary stuff. I would call this one hopelessly bloated and overengineered and recommend something like https://github.com/Yonaba/30log https://github.com/Yonaba/30log instead.
- otikik 2y agoStart with Lua. Moonscript produces Lua so you will have to deal with Lua if you’re ever to debug a Moonscript program. The opposite isn’t true
- orange_fritter 2y agoI've spent probably 200 hours with MoonScript, was obsessed with it for a bit, and love it 90% of the time. The problem is that MoonScript's grammar is INCREDIBLY permissive. Common typos(often involving spaces) don't break your code, whereas in Lua or Python the mistake wouldn't compile. MoonScript is awesome but I lean on compilers pretty heavily to catch my mistakes, so I sadly and regrettably admitted that I was more productive with other toolchains.