I think the person typing is always the person typing - kind of a truism (in this case it's Ilan Tochner)
The problems aren't with script compatibility but rather with understanding that if you constantly update an object the server needs to constantly do work to save new object states and send those object state updates to everyone in range - this wastes CPU, disk I/O and network bandwidth. Scripts that only set an object property once on rezz, or in response to an event, do work when those things happen but they don't create a constant drain on server resources (which in the aggregate creates lag).
I think the person typing is always the person typing - kind of a truism (in this case it's Ilan Tochner)
The problems aren't with script compatibility but rather with understanding that if you constantly update an object the server needs to constantly do work to save new object states and send those object state updates to everyone in range - this wastes CPU, disk I/O and network bandwidth. Scripts that only set an object property once on rezz, or in response to an event, do work when those things happen but they don't create a constant drain on server resources (which in the aggregate creates lag).
Yes..which is why someone I knew who was smart on those things taught me about the --show updates-- thing and I use it regularly for my own regions to try to keep them optimized...often it being a give and take kinda thing where I have to ask myself is the shiny worth it...
And, oh, yea....guess it was me typing...lololol [fun to see you add some humor to that too-))]