awesome-love2d VS lua-language-server

I tried both and honestly the experience with love is better because it's actually made for lua. There's a vscode extension for love, a ton of lua libraries etc.

For OOP, look into metatables. I got started with Lua through Love2D and through that I found some OOP modules that are pretty helpful. Here’s a full list of them: https://github.com/love2d-community/awesome-love2d (I’ve been using classic with my projects)

Such a great Lua gamedev framework! And there's lots of libraries in GitHub. Many collected on awesome-love2d so you don't have to build everything yourself.

love2d is open source and runs on PC and phones. Someone's even ported it to Nintendo3DS/Switch homebrew. nata is the ECS I use, but you can also checkout more libraries on awesome-love2d. I really enjoy using love2d (especially if you enjoy the engine building parts), but one caveat is that major version number bumps will break compatibility. It's usually easy to port and they deprecate functions long in advance. But there's lots of old libraries out there for older versions that won't just work on the latest love2d (like the code for Harvard's CS50 course).

This is example is just the simple version, a state managers can be very powerful, some examples can be found here

I've used tiny ECS a bit, and I like it a lot. Check out this list

It depends on what you want to display that will dictate the limitations on how you can adjust to different resolutions. There are probably libraries that can help you with this.

Once you've done a few tutorials, you can start doing your own thing. Use the LÖVE Wiki (first link) to your advantage. It has the whole love API documented, and you'll probably need to have it open while you work. At this point, you can also look at this GitHub repository for a list of cool libraries that work with LÖVE.

Check the documentation of lua_ls

You can use LLS extension for VSCode. Documentation: https://github.com/LuaLS/lua-language-server/wiki/Annotations

There's lua-language-server which works with types defined in definition files and/or annotations in comments.

Lastly, neovim now supports semantic token highlighting which uses semantic tokens from LSP servers to provide even better, language specific highlighting. Some LSP servers support semantic tokens for doc comments. The lua language server is a good example. Unfortunately, if you're using a language like C or C++, the language servers do not provide semantic tokens for comments because doxygen style comments are not specific to those languages so you might be out of luck for semantic token highlighting.

I think it is because the language server send a different type for the first line: https://github.com/LuaLS/lua-language-server/blob/eeffd1462b892fda5d01282acf840ba0e154e467/script/core/hover/label.lua (might be one of the other files here, not label)

And I was reading this installation guide and after "./bin/lua-language-server " I get this in terminal

Not sure about typescript but there is a jsdoc equivalent: https://github.com/LuaLS/lua-language-server/wiki/Annotations

Lua with lua-language-server and annotated types is a much nicer experience.

For it to be language-aware (like provide suggestions for module/table/class methods/fields) you also need language server (like lua_ls for Lua). But even without it you should see suggestions from fallback method. If you don't, then 'mini.completion' is not installed and/or activated.

I also want to thank current & past GitHub sponsors who help finance costs associated with the plugin. I regularly pay the surplus forward to other devs whose tooling I heavily rely on (huge shout-out to sumneko for working on the Lua language server, without it a plugin of the complexity of mason.nvim would be impossible, go sponsor them here).