>>1 >Services you should use
Throw your code on hastebin.com or gist.github.com or nobody will help you
Use GitHub for things that need to last more than a short while. No bitching.
>Useful (free!) programs
Blender - blender.org
Krita - krita.org
Atom - atom.io
>Chat!
#love on irc.oftc.net. If you aren't there, we're already laughing at you behind your back and talking shit about your waifu.
What brings you to Lua? Why do you like, dislike, or are somewhere in between on Lua?
I used to hate Lua when I was a kid. I thought it was confusing and meaningless because I never knew how to RTFM. After touching it again the past year, I have made a complete 180 and Lua may just be my favorite and most experienced language now.
I find that Lua's simplicity offers great freedom in the things you can do. The table structure allows so much depth and complexity with zero effort on the developer's part. It can be an array, a dictionary, an object, a pointer, a memory management system, all of those at once and even then a meaningful value in itself. It's C-like in its ubiquity yet safe as though it were specifically built to be all of those (which, for all I know, it may have been).
The use of truth value makes conditionals so clean and straightforward compared to (inferior) languages that demand explicit boolean conversion, not to mention the power of the logical operators with the power to condense a function into a single statement.
Lua's freedom with functions itself is wonderful. The Lua way of nullable/default arguments is straightforward yet nonrestrictive. Being able to override Lua functions so easily gives so much flexibility and power that other scripting languages would never dare to try. Having multiple return values handled so simply allows even more flexibility within a single function. Lua's closures then close this input-process-output masterpiece by providing a completely unlimited access to any above scope's variables, with so many uses, it'd be impossible to name them all.
And on top of all this, and more that I won't mention for the sake of brevity, Lua is fast. LuaJIT in particular is very fast, and many Lua-derived languages try to be faster while maintaining Lua's beauty (although, in my opinion, everything besides pure Lua is simply disfigurement).
So, in short, I guess this is a dumb löve letter to Lua. Let's all löve Lua.
Lua is compact, very fast and you can run it everywhere.
bad sides of Lua are:
1) no modern libs/frameworks
2) stdlib is trash (I came from JS, and Lua just doesn't have this rich stdlib functions like in JS)
3) no adequate community count (nobody will help you with smth)
Building a full stack app if anyone is interested to collaborate. I come from a python/javascript background and picked Lua a couple of weeks ago and absolutely love it.
Don't know what to build though but I finally have a good foundation with basic crud functionallity (todo). There is not a lot on how to make Lapis purely for API But I think I got it.
Also, what should the name of this stack be? Also dockerizing everything
javascript is trashjavascript hater2023-01-01 (Sun) 11:57:43No.396[Reply]
ok so javascript sucks we need to go march to mark Zuckerberg tell him to destroy react.js and then use Lua for everything and then take over the word :)
I should really learn OOPElperson2021-03-11 (Thu) 15:14:05No.192[Reply]
Like I look at the source code of this proj and oh wow I better start learning OOP so that my project isnt garbage. Ive heard metatables are hard. Is it true?
metatables aren't that hard really and you don't have to think about them for a pretty long time. most of the time even when you do need it you're just setting __call for a constructor and __index to another table though to give you a class prototype
oop is also kinda beside the point though (basic classes != oop) and not correlated with good code (it is correlated with over-engineered bullshit though)
most of the relevant stuff for organizing code is just basic lua syntax sugar, like being able to write function some_table:whatever() and it passes self automatically if you also call with :whatever()
Sure! I just updated it to run in Docker so it shoudl be WAY easier to set up now. I knwo the code is pretty messy, I am hoping to sit down and clean it up now that I have a better understanding of Lapis.
Short term wants is to make the code cleaner and less buggy, long term I want lapchan to run on a RESTful API.