Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • This is essentially the behavior we are going for. I would just like feedback on how to best handle the nasty global state. Commented Mar 13, 2014 at 15:30
  • The state is local to your UI. Depending on your UI state, you use the local copy or the state that is being continually updated. Commented Mar 13, 2014 at 16:25
  • Thats sounds massively stateful. State is evil, so evil I felt the need to start a bounty on how to manage a single global flag. It also does not give me any direction on how to manage that flag, just how I might implement based on that flag. In other words, this is still a non-answer. Commented Mar 13, 2014 at 18:55
  • "State is evil." Give me a break! The collection of data that your app displays is sometimes called the display state. It has nothing to do with "evil." DON'T make it a global flag. Make it a flag that is local to your UI. Commented Mar 13, 2014 at 18:58
  • Yes, its necessary, but things having more state then needed is often the source of bugs and should be avoid when possible in favor of statelessness. The flag is global in the UI, and only for the UI. I'm sorry if that was not clear. Commented Mar 13, 2014 at 19:01