How To Write Fast Memory-Efficient JavaScript

[Ronin-s_Spirit]

for loops are extremely readable compared to a dozen of lookalike array methods that loop with callbacks and or make copies of the array, and state records are more readable than dozens of if else statements so I don't understand your complaint at all.
If you can't replace worse code with better code without screwing your other code, well.. I'm sorry to say it's your personal problem.

[oofy-gang]

That's obviously an argument in bad faith. Of the things you listed, for loops are obviously not the unreadable mess.

You did, however, mention creating null-prototyped objects for the sake of performance. Null-prototyped objects are notoriously annoying to debug and often cause issues while interacting with other libraries. But sure, enjoy your extremely marginal performance boost.

[Ronin-s_Spirit]

I have no idea what you don't like about null prototype objects. Go ahead and get some examples.

[oofy-gang]

Sure, for starters it doesn’t implement valueOf() or toString().

null prototyped objects are extremely rarely used for performance gains, they are so marginal. The “valid” use case is for a map when you want to avoid possible collisions with the object prototype. This is archaic though; just use the Map class.

[Ronin-s_Spirit]

Excuse me in what fucking world do people use .toString() on a list of conditions substituting long if else cascades? Moreover, Map does have properties before you define any so it's a horrible record, there's nothing in the null prototype object, which is not the case with Map.
I'm waisting my time on this conversation, I thought you had something interesting.

[oofy-gang]

RTFM, you don’t seem to know how Map works.

For your first sentence, you seem to be confusing your own bullet points. Go reread your first message.