Ciekawe komentarze z hackernews
The master's answer is that you use one or the other depending on whether - you are representing
The expertise lies in
Summer time does not start and end on the same date everywhere. So you also might need to know the UTC offset corresponding to the time at that time not just the UTC offset of that time zone today
Split the parts that change from the parts that don’t change: 1) move state down or 2) lift content up, use {children}
Alfred Whitehead's observation that 'civilisation advances by extending the number of important operations which we can perform without thinking of them'. Progress is being made by holistically integrating knowledge in a way that makes it sort of ambient.
Maintaining state is an easily solved problem severely over engineered by frameworks. The central issue why this becomes so complicated is because developers who aren't comfortable writing original code would rather deal with an ocean of configurations than a few architectural decisions.
That is problematic because configurations are settings not decisions, which means you need work arounds for edge cases and work arounds for the work arounds. If instead you treat everything as a requirement instead of anything as an edge case then you are forced to make decisions and write the corresponding code. New requirements may necessitate refactoring of current decisions down the road, but the code stays clean, small, and deliberate.
At the most simple you only need three things: a central consolidated point of settings (object), storage (localStorage), and interactions isolated to their respective purpose (handlers).
the design incorporated white space in all of the usual places—around headers, content blocks, and in table rows. The breathing room was glorious. It lasted one month before the company was forced to retire it. Users absolutely hated the new system. Sure, the old system was ugly, but it had everything they needed, right at their fingertips!
Gdybym kiedyś zastanawiał się nad cssInJs, to komentarze mogą być przydatne
An alternative to Elasticsearch that runs on a few MBs of RAM
When [observation], I feel [emotion] because I’m needing some [universal needs]. Would you be able to [request]?
State management is messy, that's clearly an area where the problem still hasn't been solved. The main issue is that state means too much really.