Read on Twitter
The more I use HEY, the more I think it makes the case for 'modern' SSR'd SPA-ish development, rather than the Rails+Turbolinks+Stimulus model. I realise it's v1, but there are some rough edges that will be hard to fix, that you just don't expect to see in an app in 2020.
One example: if you have lots of unreads (which I always do 
), you might scroll to find a specific one, which causes additional emails to load (it starts with 30). Open it, navigate back, and your scroll position is lost â you're back at the top with the initial 30. That's bad.
), you might scroll to find a specific one, which causes additional emails to load (it starts with 30). Open it, navigate back, and your scroll position is lost â you're back at the top with the initial 30. That's bad.
Overall, it's certainly not an unpleasant app to use, and I'm glad that we have an example of a real, non-trivial product that has so little JS and scores so well on Lighthouse â this is the benchmark that JS-forward frameworks and their users should aspire to beat.
But HEY certainly doesn't make me question my front end development philosophy â quite the reverse. (I've articulated that philosophy a bit here, if you're interested: https://dev.to/richharris/in-defense-of-the-modern-web-2nia. And yes, I'm aware of the irony that that blog post is served by a Rails app.)
This is an excellent point: https://twitter.com/mahemoff/status/1276673603065442305. A lot of people, me included, keep their email open in a tab all day. For that kind of app, Lighthouse score etc is mostly a distraction â it's subsequent interaction/navigation that matters most. (inb4 why-not-both.gif)
