/
Similarly controls with state are a bad idea
Similarly controls with state are a bad idea
- Eliot Muir
Owned by Eliot Muir
For example - a “grid control” or a “tree control”
It becomes confusing where application state should live - there needs to be a single source of truth and the less duplication the better.
For instance if you write an application which needs to represent a file tree, then do it by:
Keep the state information in nested Javascript table. See why you don’t use the DOM.
Write a simple routine to take that state and output HTML which shows that state.
You’ll be rewarded with a much simpler and more reliable design.
, multiple selections available,
Related content
Another way to look at why the DOM is a bad place to store state
Another way to look at why the DOM is a bad place to store state
More like this
Typescript is a bad idea
Typescript is a bad idea
Read with this
Do not store application data in the DOM
Do not store application data in the DOM
More like this
Best practices for handle click events for GUIs with many child elements resulting from application data
Best practices for handle click events for GUIs with many child elements resulting from application data
More like this
DOM Elements versus HTML markup
DOM Elements versus HTML markup
More like this
Making DOM APIs give you plain old rectangles which you can manipulate.
Making DOM APIs give you plain old rectangles which you can manipulate.
More like this