I lucked out, I’m on a two year project that just wrapped up and we skipped useMemo for the most part. Then it got announced that the new React version will depreciate that.
There will be no wrapping up this project in the foreseeable future as it’s part of our main platform. I’m looking forward to moving from cra to vite and removing one ore more of the three css frameworks we are using. The App is also still incomplete as it’s replacing an ancient asp net project still partly in use … so it’s legacy hell over here. Also it’s all class components so … no useMemo atleast for now.
Maintaining old react apps that don’t use setState…
this.state.temp = val;Meanwhile elm programmers: look what they have to do to mimic a fraction of our powers
You have my full sympathy.
Thank you. Right now I’m upgrading our 5 year old react version while forking all unmaintained deps … fun
I lucked out, I’m on a two year project that just wrapped up and we skipped useMemo for the most part. Then it got announced that the new React version will depreciate that.
Good luck dude.
There will be no wrapping up this project in the foreseeable future as it’s part of our main platform. I’m looking forward to moving from cra to vite and removing one ore more of the three css frameworks we are using. The App is also still incomplete as it’s replacing an ancient asp net project still partly in use … so it’s legacy hell over here. Also it’s all class components so … no useMemo atleast for now.
Edit: thanks as well, appreciate it.