Luau is to Lua what Typescript is to Javascript. I am curious why they are choosing it in particular.
I'm hardly an expert in these matters but, again, from what I'm told, it seems that SL imposes particular requirements -- particularly that any resident can compile scripts in-world with results that are immediately visible to all residents on the region, and that scripted objects can move from one region/simulator to another while preserving their script state unless they're explicitly told to reset on rez/region change -- that narrow the available choices quite considerably.
The thing is, that is not some inherent limitation of LSL, it is just that there is no function to allow that. I suppose if this is somehow structured completely different in terms of how it exposes functionality to being scripted, then maybe, but otherwise, Lua would run into the same issues.
This Lua thing sounded like it's more client side though, so I wasn't sure if it may have access to some things LSL doesn't in world.
Right, I get that, but ultimately your shape is an inventory item, so it is doing server side changes once you save. I do hope they allow scripting of a lot of stuff we can't do now, we will see. I am excited by the possibilities.
That was kind of my thought, since it's client side based. If the viewer can do it, the script could do it.
ouch... but yes.... introducing a new powerful scripting language probably does come with a host of new security risks.
LOL.
SL has certainly not been without its security exploits and griefing issues, but I am hopeful that they will take a measured approach to this. It has tremendous potential, but only if they implement it well and securely. LL is not always known for doing either. Still, I am optimistic because I am silly like that.
Not exactly the standard procedure of Linden Lab, is it?
