We require all of our code to work without Javascript (although in the most basic sense, it's perfectly fine to use Javascript to enhance an experience), and th

We require all of our code to work without Javascript (although in the most basic sense, it's perfectly fine to use Javascript to enhance an experience), and there's advantages even if you ignore "people who turn off Javascript in their browser": - Certain problems, like ensuring that browser navigation works properly, either disappear or are massively reduced. - We wrestle with bundle sizes a lot less, since a majority of our code ends up being genuinely server-rendered only - there's little to no advantage to doing additional client side rendering of a straightforward form or other mostly static content. - Integration tests can be faster and more straightforward to write if you don't need to worry about JS. Of course, they're not full end-to-end if you're not testing JS, but for secondary flows they can suffice for the "good enough" category, and often (but not always) failures in your client JS will allow the SSR code to keep running fine as a backup.