@DmytroKrasun Two things: packaging density and security. For both docker is lacking and as such it will not be the final solution. Search Google for how WebAssembly is solving these and might/will replace docker.
Feature Friday @itemzen_app!
- The organization can now be modeled as a hierarchy of locations and sites.
- Templates can be made 'location assignable'.
- Assets can be assigned to a location or site.
@Matt_heyqq I second that. Current progress is made by doing more of the same at larger scale, but some very hard problems remain unsolved. Have a look at the work of Jeff Hawkins.
@MrPeterLMorris Sure, I'm mixing up Flux and Redux. I meant to refer to the Javascript world where the pattern is rooted right? The way state is mutated in flux seems relevant in loosely typed languages but not so much in static ones like C#.
@MrPeterLMorris The same things the redux pattern tries to solve right? 1/ uncontrolled changing of state and 2/ managing state which does not fit in a parent-child relationship
@MrPeterLMorris My feeling/experience is that MVVM, combined with messaging, can cover most of the problems flux is trying to solve (in addition to others). In case you do need state which is orthogonal to your context (or common to a lot of VM's), you can use/inject a service class.
@MrPeterLMorris Community toolkit.
Also: would you be interested in a blog post about MVVM in Blazor? I used to use Fluxor, but frankly after quite a bit of struggling with it I switched to an MVVM approach.
@sudobunni I've been teaching this for over a decade to developers and practice it myself as a religion. People think they need to write documentation for others, but you are the one who benefits the most.