IMO it's more like anyone who doesn't spend over 50% of their time thinking about React re-renders whenever they're in a React component. The level of effort to properly use hooks is insane, so them being touted as a "less boilerplate!" way of writing "more functional" (literally the opposite in practice) code is egregious.
I agree with this take! And class-scoped callbacks kept the render function so clean, I feel like hooks really muddled up the API with regards to render. It also created far-more proprietary-to-React logic.
Except in the real world opinionated leads and team members forced teams to adopt ONLY hooks going forward, or have to maintain two separate implementations - hook compatible or class component compatible code.
So yes, this is a very sensible concern that transpired with hooks. Simply allowing reverse compatibility doesn't change the fact that hundreds of workplaces forced people to use a less ideal paradigm.
React hooks were a huge mistake because they (along with the huge push by Gaaeron to ditch redux at the same time) disrupted the more declarative styles in React that subjectively relax the mind. Boilerplate code is tedious, but gives the brain a rest from reasoning that many developers actually enjoy. You can really get in the zone wiring up a react/redux app and isolate yourself from re-render logic by focusing on individual stores, reducers, and action logic.
The hooks people came in and said F all that, lets instead create an API that garbles up all the code in one spot, with imperatively nested functions required for more complex use-cases, oh and lets use CONTEXT for state management and just partition items up to deal with re-renders.
They didn't do it on purpose, the react team is highly skilled, but they lacked the wisdom to understand how lower tier or mid-tier developers would use it. I knew plenty of devs that had 3-4 YOE and couldn't grok hooks for years.
Coming from an Argentine family Yerba Mate is great. I'm American but have been drinking it frequently since the time I was 14 or so. I drank tons in college but took a multi-year break a few years down the line due to reflux issues that it made worse. Those are some things to look out for - heartburn, sinusitis, negative changes in mood, tension headaches.
I notice that there is a huge difference between Yerba Mate brands in terms of the perceived effects. Lately Union Suave and Rosamonte have not been sitting well in my stomach or mind (irritability, lack of concentration, tension headaches, etc). Taragui Liviana and my new favorite Playaditos are the best for me. I've been drinking them twice a day with no perceivable ill effects. Although I do lose some endurance performance on the high end when drinking Yerba Mate before running which I've tracked with a chest mounted heart rate tracker.
I'd like to send the different brands off to a lab to have a better understanding of WHY I feel such a difference in the effects when going brand to brand. I'd assume its due to different concentrations in the three primary Xanthines - Caffeine, Theobromine, Theophylline. Anyways, definitely worth the squeeze, but don't be surprised if you need to try a few different brands to see which affects you the best.
Thanks for the insight! I think you've convinced me that it's not a huge deal. I was mostly shocked at the ease of reverse engineering my "MVP", but it would be unlikely for my specific targeted niche.
Any tips on electron build tools to secure Electron apps that have proprietary logic like this seems like it would have? I saw your posts and was curious since this seems like it would have a lot of proprietary JS to protect against cracking. I've seen Bytenode and asarmor but they don't seem as though they're very well maintained or ready for primetime.
I'm working towards releasing my first Electron app now and this has been a concern for me.