If you have a complex user interface with the possibility that many parts might be in use at any given moment, full page refreshes mean your users could lose wo

If you have a complex user interface with the possibility that many parts might be in use at any given moment, full page refreshes mean your users could lose work. This would definitely be a bad user experience. But it doesn't mean refreshes are bad, just that the architect of that application hasn't factored them into the user experience appropriately, or they've made their interface unnecessarily complex. All modern browsers have enough tools baked in that we can work around this without reinventing the execution and rendering pipeline (e.g. localStorage).