2 ms·
Which client stack have you used where state management was simple and easy? Pretty much all desktop/mobile SDKs have all the same problems of two-way data bind
by hombre_fatal 7y ago
Which client stack have you used where state management was simple and easy? Pretty much all desktop/mobile SDKs have all the same problems of two-way data binding that we moved away from in the web. Frankly, the web has the best experiments in state management simplicity yet that I wish we had long ago across all clients. It's taking way too long for the best ideas to trickle out into non-web clients.
macOS/iOS is a good modern example of the old way of doing things where you're stuck using this weird OOP-for-OOP's-sake Core Data abstraction that certainly doesn't feel like a local optimum. It's the polar opposite of simplicity. When things don't work, it gets complicated very fast as you try to credentialize in it.
By the way, client development was never easy. It's only gotten simpler over time. Painting a component to the screen (your example) whether you can use a built-in or have to make your own is still the easiest part of client development, not the hard part. State management and deciding on when to repaint is still the hard part. And just because the runtime gives you a solution doesn't mean it's simple or ideal. So I'm wondering which specific client development experience you're looking back on with such rose-tinted glasses.