Low-Level JavaScript Performance Best Practices (Crash Course)

[@klarafall4281]

Good examples. Also keeping the folder view open actually helps understanding what currently explained. 👌

[@bombardo2489]

man this exactly what i needed. could you spoil us further and make us video about user auth on enterprise level that would be sick

[@SoftwareDeveloperDiaries]

Happy to hear, mate! I'll put that on my list 😉

This one sounds really good

[@W1ngSMC]

I'm pretty sure JS strings are pooled so only the pointers to the actual c strings are compared. (V8 for sure pools constant strings you declare with "...") That is a reason you can't just set some nth character in the string, like in C.

[@SoftwareDeveloperDiaries]

Good point

[@gamingwolf3385]

I was waiting for this video , thank you a lot I am learning C# , i see some new concepts like domain entity , value objects and this stuff , can you explain hiw to do it in node ?

[@SoftwareDeveloperDiaries]

Will check if there are such alternatives in Node!

[@NathanielBabalola]

Thank you, can you please drop the links to the jsbenchmarks ?

[@SoftwareDeveloperDiaries]

Unfortunately they are not persisted, but you can find the approx. results in the original article linked in the description

[@repenning1]

"Premature optimization is the root of all evil" - Donald Knuth. Why would you bother rewriting arguably more readable code (e.g., the array method example)? First of all, an improvement of, say, 38% in most use cases is quite pointless unless you are having a hard constraint such as 16ms FPS rendering budget. Second, the performance gain, if there even remains one, may be gone with the next version of JS engines. In short, stick to the more readable and more maintainable code and only optimize if there is an actual reason to do so.

[@adwaitbokade2890]

Magnificent !!

[@prashlovessamosa]

Great

[@_Greenflag_]

This is ok for a general knowledge, but this is (and should be) useless in programming. Yes, due to how things have been build, there is a difference of performance of objects "not having the same shape" but nobody (or there is a code problem) will do some 1 million iterations on an array or objects. So build readable and concise code instead of some esoteric performance optimisation.

[@Serjgap]

Speed optimization advices here are ok, but code style is very bad and inconsistent. You should have cleaned it up a bit instead of directly copying the article

[@GoetzGehgetz]

t-10 ;)

[@HardikRudra-g3m]

Great