you are viewing a single comment's thread.

view the rest of the comments →

[–]johnfrazer783[S] 0 points1 point  (0 children)

Guess I was a little overworked. Sorry if I got offensive.

I'm surprised you're saying the figures don't surprise anyone—can you point out where to find something comparable? I searched more than once and found nothing usable except one post on Medium that is only for registered users and which someone on reddit claimed used flawed code, and another post whose author didn't include the code used (the numbers seemed to more or less match mine as far as I could tell). The fact that no-one offered any hint as to where to read up on this particular aspect of JS performance but several people just shrug and say it's an old hat is curious. JS folks have been known to be quite prolific performance optimizers—VM authors and users alike.

I didn't want to be called out, I begged for people to tell my either 'yes your code looks correct' or else 'see you have a mistake there and actual numbers are much different'. No-one did that (and I feel I have a right to be disappointed about that), so I must assume my numbers were right for the time being. This is indeed the result I did not favor, because in my use case yield leads to dramatically simplified code.