RunJS VS why-did-you-render

If you would like to follow along or try the code examples for yourself, I strongly recommend using RunJS.

Is there an app for Python similar to https://runjs.app ?

If you're starting out, I recommend using a sandbox to test your code. Run JS is a very useful tool as it logs

RunJs https://runjs.app/ is pretty cool for playing with JavaScript by itself.

RunJS: https://runjs.app/

Hey! Former bootcamp student here. What I learned is that medication like Adderal, Vyvance, Ritalin, etc, doesn't help with learning because learning is a slow process. You have to chew through things to understand them and take breaks to let your brain consolidate new information. The beginning of a bootcamp is always the hardest, but after a while you figure out what routine/habits/learning style/etc works for you. Additionally, after getting the hang of Javascript basics, things usually get easier. (sidenote - RunJS is a great tool to use to learn)

OK, I see. My machine has node v12.22.9 installed, probably since I installed it from apt. I downloaded 18.12.1 from the site above, but alas, I do not know how to install it. I'll have to read the docs it seems. It will be helpful to learn as I've tried to install runjs on my Ubuntu laptop, but I can't figure how as it seems I have to install it from binaries also (which I have no idea how to).

https://runjs.app/ is the closest I can think of.

Check out why-did-you-render. It may tell you some more information.

It's a combination of many things, but imo one of the worst is all the footguns regarding state and the rerenders they cause

https://emnudge.dev/blog/react-hostage

It's so easy, that we monkey patch react to debug it https://github.com/welldone-software/why-did-you-render

Plus the vdom... Isn't great, the bundle size puts react at an inherit disadvantage, and the community has a knack for over reliance on bloated packages

When we implemented the MVP of the fintech app, we had a quite complicated form. At that time, I was still young and inexperienced. And eventually, we realized that our project was slowing down. We had to spend additional hours figuring out the reason. We had many unnecessary re-renders because we ignored basic rules related to props in React. I wanted to do everything possible to avoid such situations in the future. So, I added to the project linters like this and an additional starting configuration to package.json to run why-did-you-render. In short, this plugin issues a warning if something is re-rendered unnecessarily and suggests how to avoid it. Also, we included running Lighthouse in headless mode. Some people say that premature optimizations are bad, but for me, it's a principle: do it right from the start.

maybe somethin like https://github.com/welldone-software/why-did-you-render

This might help you out a bit.