I've worked now for 3 years on a large lua game code base, over 4000 files, 1.5 million lines of code. In the first week or so, I was a bit weirded out by the

I've worked now for 3 years on a large lua game code base, over 4000 files, 1.5 million lines of code. In the first week or so, I was a bit weirded out by the lack of language features, as I come from C#/Typescript/C++, but I was very surprised that after 2 or 3 weeks, I was already doing very complex tasks on the code base. I think a lot of that comes from the simplicity of the language. It's very difficult to surprise you, everything works in pretty much the same way. Here are some things that I will miss once I move to other languages: (note that most of these are not things that come from simply using lua, you have to implement it into your framework/engine, but they are still pretty common) - stack traces print the contents of the variables in the stack. Not all lua code bases have this, but it is easy to implement. - if the code crashes, you can fix the code and continue. This doesn't always work, and requires the code base to be written in a way that supports it, but it is definitely possible and I've used it many times. - debugging works really well. You can easily attach and inject code, stop on exception and inspect the state. - settings are also lua code. This is probably the biggest thing I'll miss. I love being able to have simple functions as part of settings (e.g. things like tweening functions), being able to generate settings based on other settings, or run simple sanity checks, all on the same file. - index starting on 1, this is definitely an unpopular opinion, but IMO it just makes things so much easier. When you need to access the last element, you just do tbl[tbl_length], no need to decrease by 1, or doing a for loop, you only specify the indices you're actually accessing "for i = 1, last_index do end". I think it really helps with off by 1 errors. I used "normal" indices for over 10 years before this project, and I would still occasionally have these errors, but with lua, I don't really remember having them. - not having to fight the compiler to quickly try out different things. Need something from a completely different system? Just add it to the global table and access it from the other place. A big learning I got from transitioning from languages with a very strong type system to a dynamic language like lua, is that in order to be effective, you really need to use code architecture patterns, otherwise things become very hard to reason with. This might be counter intuitive, but I think you need to be a better programmer to use lua effectively, than you need to with a language like C# or Typescript. With the latter languages, the compiler helps you a lot, but with lua, you have to know how to use these things on your own, because you can pretty much do anything and that can be reeeeally bad :)