3 ms·
Additionally, html documents inside browser windows are naturally stateless content systems, but applications have never had this constraint. The design pattern
by seanalltogether 6y ago
Additionally, html documents inside browser windows are naturally stateless content systems, but applications have never had this constraint. The design patterns that are successful on a browser are usually overkill in application development. Android has baked a few of these stateless design patterns into their core frameworks and then spent years coming up with various support libraries to overcome them.
- uryga 6y ago> html documents inside browser windows are naturally stateless content systems what about inputs? or do you consider them stateless because their entire¹ "state" is reflected in the DOM, i.e. <input type="checkbox"/> // *click* <input type="checkbox" checked=""/> --- ¹ - well, except focus, open/closed for <select>, and probably a bunch of other things
- seanalltogether 6y agoIn this context stateless usually refers to access to the wider system. When an html page loads, it has no state it can access right away, it has only raw data in the url and cookies. You are constantly having to recreate the state of the system as a user moves from one page to another. Design patterns like react are a natural fit for this system, its turtles all the way down. Applications on the other hand start their lifecycle as a singleton and because you can guarantee a parent child relationship from top to bottom it tends to facilitate design patterns with sharing of state more easily between pages.
- uryga 6y agoah gotcha! for some reason i thought you were talking at the component level, not app level.