Hey /g/ what do you think of Lua? I haven't seen anyone

>>61818287
Who keeps making these?

Yes Lua is still very much alive and powerful. Most people oversee it because using it properly requires alot of background knowledge.

Also what do you mean "learn Lua"? In what context? Lua just by itself is pretty useless.

>>61818562
This. Lua works like a charm when used with a program. By itself is not as good as other langs.
Excuse me for this /v/ tier speech, but I think that Source Engine scripters make a good part of the Lua community

>>61819068
Adding on to that, if one likes homebrew, Lua is usually available for basic programming, since it's easy to implement from just C.

>>61819068
>>61820415
While Lua theoretically has full C access through FFI its extremely tedious and somewhat unsafe (in standalone usage).

Lua should be used to dynamically extend existing applications. Also some people found it useful in web development, dunno how that works tho.

A key feature is LuaJIT which allows to change and update code while the application is running, in realtime.

>1 based indexing
Into the trash it goes.

>>61818287
It's pretty comfy for programming ESP8266 quickie apps with NodeMCU. Who even needs Arduino?

>>61818562
>In what context? Lua just by itself is pretty useless.
This. Bitops are optional last I heard.

>>61820963
>babby can't wrap his little brainlet around 0 being truthy
smug_anime_girl462179.jpg

>>61820963
0 indexing only makes sense when referring to memory addresses.

>>61820963
>>61821098
Not to mention you can index at 0 if you like

It's fucking awful for a lot of things, half the packages on luarocks are broken, unmaintained messes. Attempting to do anything remotely complex with it will make you want to die.
At least it's fast and easily embedded.

>>61822112
Basically this.

>>61818287
It's behavior is obtuse and often times contrarian to other languages for absolutely no reason (1 indexing, a bunch of weird nil behavior I can't remember right now), it's far more difficult to build into a C application than say, Python and it's so barebones anything you build in it will turn to unmaintainable gibberish.

The only argument for it over the far more standard, far easier to integrate and far more popular Python is it's small size.

>>61818287
>Hey /g/ what do you think of Lua?
The thing everyone integrates into their shitty C code and forget to sandbox properly and then get exploited.

>>61818287
Lua has a simple grammar and stdlib which makes it suitable for embedding into other software in place of a DSL (scripting language for user extensions, database with data and code, etc). Not suitable for general work.

I wrote a few web services in Lua for my school. OpenResty's non-blocking IO is easy as normal functions thanks to co-routines. It's something I wish a garbage collected C-like language with generic types (i.e. not Go) also had. Async/await is fine but it seems a burden in comparison.