4 ms·

Its not just something me, and you disagree on. I would say it's me, plus a good amount of other, and also most browsers. If the browser is locked over X secon

Its not just something me, and you disagree on. I would say it's me, plus a good amount of other, and also most browsers. If the browser is locked over X seconds it will actually tell you that the script is unresponsive, and ask if it should stop it. But you can of course work around this, and disable it in your browser of choice (http://www.reginout.com/nflp/fix-unresponsive-script-error-in-firefox-chrome-ie.html http://www.reginout.com/nflp/fix-unresponsive-script-error-i...). Or you could just use a webworker, and not lock the UI.

thinkMOAR 10y ago
If my opinion differs from you or anybody else, that would be considered a disagreement. I never see my browser being locked, and if it is locked waiting for the information i desperately want to see, i honestly couldn't care of my UI locks up during that. I don't care about anything else at that point. I understand this is not how most people look at it and to you there is just one way and thats the responsive UI way. But i see it as they rather have nice spinning wheels but a car that won't drive anyway.. And if that test uses a sleep, which is specifically says it does not, it would have even been a bad showcase. Now it performs bad (people suggest using multiple workers.. lol for a bubble sort)... Be critical about a non locking UI that doesn't show your information anyway. Fix the application it self so it wouldn't need to lockup in the first place.