The point about people not using it is not quite right.
But people don't quite use it in JavaScript indeed. JavaScript is a frontend language after all, at least it was initially meant for it. Right before React, frontend was driven by "dirty", functionally impure things like jQuery.
Memoization is only possible in pure environments. Thus, it was receiving almost no traction whatsoever.
Aside of JavaScript, look at the functional landscape – people thrive on memoization in lisps, as well as on lazy evaluation, pattern-matching and other good old functional things.
Good things to come – modern frontend is moving towards functional concepts.
Memoization and other good things are to be resurfaced.
Thanks a bunch for your input. You nailed the point. Because Javascript is easier to get started with it, it's easier to keep doing the dirty stuffs. But even at the moment React implements meomoization with React.Memo and stuffs.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The point about people not using it is not quite right.
But people don't quite use it in JavaScript indeed. JavaScript is a frontend language after all, at least it was initially meant for it. Right before React, frontend was driven by "dirty", functionally impure things like jQuery.
Memoization is only possible in pure environments. Thus, it was receiving almost no traction whatsoever.
Aside of JavaScript, look at the functional landscape – people thrive on memoization in lisps, as well as on lazy evaluation, pattern-matching and other good old functional things.
Good things to come – modern frontend is moving towards functional concepts.
Memoization and other good things are to be resurfaced.
@akashkava
Thanks a bunch for your input. You nailed the point. Because Javascript is easier to get started with it, it's easier to keep doing the dirty stuffs. But even at the moment React implements meomoization with React.Memo and stuffs.