> I still greatly prefer it to the alternative, which is to have merge commits cluttering up the commit history.
I've heard this many times before, but haven't been able to figure out why this is a problem. In your workflow is it a problem to have a cluttered commit history? If so, could you explain how?
> At the same time, what about people that still fall for Nigerian princes or go through their spam folder for "sex in your area" or "penis enlargement pills"?
Though I must say that if the intention of the video was to make me doubt abilities to spot deep fakes, it didn't manage to achieve its goal. Both Nixon's face movements and voice felt highly unnatural and robotic to me. Although I'm sure it won't be many years until the results of such experiments will be come indistinguishable, we are not quite there yet.
IMO, direct call (especially if those are common in your workplace) is much better than a vague "can we talk?" before a call. Doesn't give the mind a chance to wander and fill in the context.
Regardless of anything else, it's completely within the rights of an open-source maintainer to pick and choose which users they want to dedicate time to help.
The license doesn't forbid anyone to use the software, so cryptocurrency companies are still able to benefit from the library.
I'm glad that you're happy with the system, but I'm not satisfied with your comment. In my personal experience, people with "unlimited vacation" tend to take less overall vacation than I do, on a mandatory vacation time per year.
> (you'd have to explain going beyond, say, 4 weeks, but otherwise working)
Unless "I'd like to take a 5-week vacation" isn't enough explanation in itself, it clearly isn't working. An employee shouldn't have to justify _why_ they want to go on vacation.
> The real footgun is people not reading the documentation for the framework they use
I would argue that the real footgun with hooks is the case where a `useEffect` call inadvertently gets triggered on each render because one of its dependencies, passed through another hook, changes identity on each render. It can get quite maddening, and in many cases you don't notice it until someone points out the resulting performance issue with your app. The solution, of course, is `useMemo` and `useCallback`, but it's not intuitive and it can be easy to miss from time to time in a large project.
I don't have have an answer to your question, but one major factor that one should consider when making a popularity comparison between Flutter and React Native is that _React_ part.
Most problems and questions that developers encounter while working on React Native applications are not specific to React Native, but rather React itself. As such, I find it likely that many RN developers don't always use "native" in their search terms.
That said, I personally feel like the mentality of "We will fire you if you aren't doing an _exceptional_ job" reads as a serious red flag. The implication here is that you should expect to work overtime and prioritize your job over all else. Even then, we might still fire you.
Of course I'd rather have a company being open and upfront about their unsustainable expectations, but I'd still prefer a company that values work/live balance of their employees. Would I say that Netflix's approach is toxic? Honestly, yes. But I do understand that this is just my own opinion.