Hi all, I have a statement I just published that I'd like the communities take on.
For background, I've been a frontend and backend engineer over the years, and have noticed that there are nuances in each domain worth considering.
It has been common to encounter companies with more leadership from their backend engineers, and I question how much of the usual best-practices have been shaped without enough front end domain consideration.
here is the statement, what do you think?
The Case for Variables on Elements
It's a good idea to keep state in as few places as possible right?
Not always... locality is the best chance a user-interface has for making sense during development.
This is not a casual idea, it's because immutability is a loosing battle when there are a lot of user events involved.
Localized ownership of internal state is a more scalable solution, and it leads to a "what you see is what you get" authoring process, which is more discussable, and thereby maintainable.
Top comments (0)