The more I use HEY, the more I think it makes the case for & #39;modern& #39; SSR& #39;d SPA-ish development, rather than the Rails+Turbolinks+Stimulus model. I realise it& #39;s v1, but there are some rough edges that will be hard to fix, that you just don& #39;t expect to see in an app in 2020.

One example: if you have lots of unreads (which I always do https://abs.twimg.com/emoji/v2/... draggable="false" alt="🙃" title="Auf den Kopf gestelltes Gesicht" aria-label="Emoji: Auf den Kopf gestelltes Gesicht">), 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& #39;re back at the top with the initial 30. That& #39;s bad.

Overall, it& #39;s certainly not an unpleasant app to use, and I& #39;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& #39;t make me question my front end development philosophy — quite the reverse. (I& #39;ve articulated that philosophy a bit here, if you& #39;re interested: https://dev.to/richharris/in-defense-of-the-modern-web-2nia.">https://dev.to/richharri... And yes, I& #39;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.">https://twitter.com/mahemoff/... 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& #39;s subsequent interaction/navigation that matters most. (inb4 why-not-both.gif)