> Component state should only contain volatile data that is not important to save, the opposite of LocalStorage.
Where do you store data that you retrieve from a server for rendering? Storing it in the state is perfectly fine. In this example, data is retrieved from local storage and stored in the state.
It's good to see UX design problems analyzed from a technical perspective. Designers working on the web should be proficient at understanding the medium on which they work, and look beyond generating static images to toss over the wall for implementation.
This is missing a critical web design aspect that I see most developers miss: Space.
Paying attention to how things align, how big they are, how much and how consistent the spacing around elements is will make a huge improvement to the perception of the UI.
I've started seeing more cooking clips that are actually pretty well made and work well on the medium. If more content creators of various interests adopt it as a platform, it might be worthwhile.
Despite the press of the young player-base, Fortnite fills what you describe for me. The building mechanic creates so much opportunity for think-fast, improvise, and outsmart your opponent moments. Plus, playing solo means you don't have to interact with anyone if you don't want to.
A more consistent documentation experience. A lot of code examples import various modules, but those modules have no documentation. For example: Docs > Client > Apollo Link mentions `graphql-tools` and schema stitching, with a link to read more. Clicking that link takes you to a page that says it's deprecated, and then links to a blog post about why.
Another example: Is `apollo-link-state` deprecated? The docs for `apollo-link-state` don't mention that, but the Local state management page in Apollo Client sure says it is.
This is mostly pervasive because of agency/client relationships. Most clients go to an agency with a budget, and the agency, in good faith, is out there paying location data services to target their ads. Then a report is generated, passed to the client along some sort KPI that increased, and everyone is happy. This fraud exists because the market allows it.
React is the closest to standard JS in my experience.