4 ms·
The blog post is littered with React code (plus Apollo). Which part of the problem was specific to the workers - and how can this lesson be generalized to any F
by azangru 4y ago
The blog post is littered with React code (plus Apollo). Which part of the problem was specific to the workers - and how can this lesson be generalized to any FE framework, or no framework at all?
- tobyhinloopen 4y agoThis blog post has nothing to do with workers and everything with “just don’t use React with hooks”
- eyelidlessness 4y agoIt’s even simpler than that I’m afraid. It’s “we found a bug in our glue code with another library and we found it by debugging after overengineering.” It doesn’t implicate any of the technologies they use, just an oversight in their prior root cause analysis process.
- theogravity 4y agoOr don't use GraphQL subscriptions / Apollo for GraphQL.
- preommr 4y agoThe lesson is to understand how reactivity works with the tech stack your project is built with. This is a problem with react, and it's middlewares where things become a convoluted mess if there isn't at least one person that's experienced with what's actually happening and is attentive to avoid pitfalls with potential side-effects.
- NaughtyShiba 4y agoThe lesson is that, two objects aren’t equal even if their content is. This is what to, the issue boils down, and such incorrect React’s usage should be clear to junior-level developers.