Ahhh ok I see where you're coming from now. I was really confused because I didn't understand why you were (from my perspective), going on and on about something I already knew.
What I was trying to point out was that it is a bit more difficult to create an infinite loop in php because one of the basic parameters is specifying when it starts and stops. In bos, that is defined within the loop, which is a little strange imo (not the least of which, the fact that the sleep can be accidentallied). Without the second parameter of a loop in php the loop will completely fail, whereas without the sleep in bos, it becomes infinite. This seems inefficient to me.
I was only trying to illustrate that it was much more difficult to majorly screw it up in php.
Moreover, php and servers generally have protections in place to protect vs infinite loops without causing the entire script to die a painful death.
This in stark contrast to one missing sleep bringing spring to it's knees. Quite radically different.
As shitty as scriptor is, if lua had a parser that told you where the fuckups were, that would be really neat. I do not consider spring to be a good debugger. Like swatting flies with an elephant stampede. Course, I'm sure everyone disagrees with that for one reason or another. For me, I would like a parser just so i can know if the code will run. If I want to see the result I would load up spring.
As a friend of mine says, Wish in one hand and Shit in the other, see which one fills up faster