MarioKirby101 wrote:Whether you're copying the files or the content, it gets the same job done.
There has been a lot of work put into programming language design over the years, ever since "programming" was first invented. Teascript-vb ignores almost all of these design principles to leave you with a very simplistic language, and one important red flag for programming? Code duplication. A well-made programming language should almost never require you to copy and paste chunks of code, and in 99.9999% of cases, it's substantially better not to. Teascript-vb forces you to.
Here's an example of why.
In 2.0, I made a collision detection library. This is a fairly complex set of mathematical functions that people can make use of without having to understand exactly how they work (one of the main benefits of a library, or API). People could make use of complex collision detection without having to implement it. Now, about 2 months after this was being used in a number of places, I discovered a bug in one of the collision detection algorithms, that would cause it to give the wrong result. The fix was simple, just had to tweak one line of code.
See, the important thing here is that, because that code was
never copied anywhere, I could just apply the fix and push out an update. Problem solved.
However, if, every time that code needed to be used, the whole 2000-odd lines were copied directly into the script file, that fix would need to be applied individually for each use of the library, which is just an unreasonable task, especially when the library is shoved together with the rest of your code. Finding the line of code to apply the fix to would be a task in and of itself.
So, in actual fact, no, it does NOT do the same job. It does a superficially similar job, badly.
It's well established that LunaLua is by far the superior scripting interface to Teascript-vb. Yes, 38A has other benefits like more NPCS, but before too long, 2.0 should have that too. There is simply no contest on the scripting interfaces.