Search Results for "race"

Tame async code with battle-tested promises. Because async code is hard to write, hard to read, hard to reason about. A pain to maintain. By using a then keyword that enables you to write aSync code that reads like an English sentence. Async code is now concise, flexible and maintainable.

...Unless the requesting screen is no longer visible. Unless some other currently visible bit of UI happens to need the same data. Or is about to need it. You should show a loading indicator (but watch out for race conditions that leave it stuck spinning forever), display user-friendly errors (but not redundantly, no modal alert dogpiles!), give users a retry mechanism, and hide all of that when a subsequent request succeeds. Remember not to retain your ViewController/model/helper thingy by accident in your callback closures. Unless you’re supposed to.

...A StateUpdater is an intent to transform the state, and contains all the information to do so. Because all the changes are centralized and are happening in a strict order, there are no subtle race conditions to watch out for. We feel that Katana helped us a lot since we started using it in production. Our applications have been downloaded several millions of times and Katana really helped us scale them quickly and efficiently. Bending Spoons's engineers leverage Katana capabilities to design, implement and test complex applications very quickly without any compromise to the final result.