"There's no other scripting language that makes it as easy to add scripting abilities to native applications.
It is lightweight, simple, easy to learn, and not that hard to master. You can use it for anything: as a substitute for ini or json files, or to code entire games in it. Just like JS, just easier to embed and easier to use.
LuaJIT, in the hands of a skilled programmer, is a marvel when it comes to performance."
(Taken from reddit, by the way)
At the end, we'd go over some things that are probably not okay in typescript and Lua does better, but we'd be missing the point. The whole idea that it's not worth to rewrite whole systems in Lua just because you don't like some syntactic sugar's absence in typescript is totally lost on a junior dev. You can convince them, of course, but probably not to a full extent, and you'd still be considered a gatekeeper.
> and if you can convince me then I would let you try rewriting part of it as an experiment
What's wrong with a straight up opinion and saying: "this is probably not a good idea, considering we have 30 repositories, all using typescript, and no in-house knowledge of Lua"? Why do we have to endlessly coddle people and mislead them?
Imagine this scenario: somebody asking you to do something ludicrous and you enabling them, multiplied by the number of junior developers you have, month after month, busy with new experiments. Eventually, you'd have to allow some of these proofs of concepts into the codebase, or they’ll realize you’re just leading them on, right? Congratulations, your 30 repo react/typescript codebase is now 15 different versions of react, vue and angular, Lua, python and rust rewrites, and they are deployed (or are they) randomly on all your major cloud providers.
This is how, by being afraid to assert authority and not wanting to appear as a “gatekeeper,” you end up on a slippery slope, allowing junior developers to do whatever they want and dragging the quality of the codebase and the velocity of your team with it. How many competing experiments can your teams juggle?
If the junior devs want to learn, they should do so on existing systems, trying to understand and improve them, rather than we all pretending they are god's gift to humanity and giving them entire systems to develop from scratch and wasting months of work on experimentation.
You are doing the junior devs a disservice by leading them on like this, imo it's much better to coach them why existing systems are how they are, and help them improve along the way.
And I'd say:
"There's no other scripting language that makes it as easy to add scripting abilities to native applications.
It is lightweight, simple, easy to learn, and not that hard to master. You can use it for anything: as a substitute for ini or json files, or to code entire games in it. Just like JS, just easier to embed and easier to use.
LuaJIT, in the hands of a skilled programmer, is a marvel when it comes to performance."
(Taken from reddit, by the way)
At the end, we'd go over some things that are probably not okay in typescript and Lua does better, but we'd be missing the point. The whole idea that it's not worth to rewrite whole systems in Lua just because you don't like some syntactic sugar's absence in typescript is totally lost on a junior dev. You can convince them, of course, but probably not to a full extent, and you'd still be considered a gatekeeper.
> and if you can convince me then I would let you try rewriting part of it as an experiment
What's wrong with a straight up opinion and saying: "this is probably not a good idea, considering we have 30 repositories, all using typescript, and no in-house knowledge of Lua"? Why do we have to endlessly coddle people and mislead them?
Imagine this scenario: somebody asking you to do something ludicrous and you enabling them, multiplied by the number of junior developers you have, month after month, busy with new experiments. Eventually, you'd have to allow some of these proofs of concepts into the codebase, or they’ll realize you’re just leading them on, right? Congratulations, your 30 repo react/typescript codebase is now 15 different versions of react, vue and angular, Lua, python and rust rewrites, and they are deployed (or are they) randomly on all your major cloud providers.
This is how, by being afraid to assert authority and not wanting to appear as a “gatekeeper,” you end up on a slippery slope, allowing junior developers to do whatever they want and dragging the quality of the codebase and the velocity of your team with it. How many competing experiments can your teams juggle?
If the junior devs want to learn, they should do so on existing systems, trying to understand and improve them, rather than we all pretending they are god's gift to humanity and giving them entire systems to develop from scratch and wasting months of work on experimentation.
You are doing the junior devs a disservice by leading them on like this, imo it's much better to coach them why existing systems are how they are, and help them improve along the way.