|
> but what about non-js users or, maybe more importantly, SEO or crawlers Hoodie is more of a tool for applications, with user authentication etc, so SEO is not relevant here. I wouldn't build a public website with Hoodie. > Also, something else that really trouble me with javascript client-side is that, often, when something bugs, everything just stop working Yes. That's something we have to handle if we want dynamic web apps build on web technologies. But there are great tools today that help you 1. prevent JavaScript by automated testing in all the browsers / OS 2. track JavaScript errors, e.g. with errorception. And 3. todays browsers are more relaxed about errors, they try to continue running the app, even if one function errored out. > Is there a better solution than a hard-refresh? Would a first-level try/catch solve this problem If you can keep the state of an app and store user's data immediately, there is no big problem to reload the page, I do that in several occasions at minutes.io, the user usually doesn't realize, it's very fast. |