<story><title>DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search</title><url>https://m.twitter.com/dhh/status/1275901955995385856</url></story><parent_chain><item><author>ch4s3</author><text>&amp;gt;  the UX is fairly laggy&lt;p&gt;I don&amp;#x27;t really find that to be the case. All of the actions seem to be done for me in under 400ms which is to say under the Doherty Threshold. That mean&amp;#x27;s that they are largely imperceptible. Sure it doesn&amp;#x27;t have fancy animations, but there isn&amp;#x27;t really any time for them.&lt;p&gt;Can you cite an example of a popular React SPA that is less &amp;quot;laggy&amp;quot; in your opinion? I&amp;#x27;m curious to compare the UX.</text></item><item><author>piazz</author><text>Noteworthy how they tout the success of their &amp;quot;magic&amp;quot; frontend stack made with vanilla JS, lack of a trendy framework, etc. But if you use the app, the UX is fairly laggy, requires frequent refreshes, all the animations and interactions are off - the list goes on and on. It&amp;#x27;s noticeably subpar (and I &lt;i&gt;like&lt;/i&gt; Hey).&lt;p&gt;Seems to me that the proof is in the pudding wrt their stack, but it&amp;#x27;s probably not what they wanted to prove. I would take a well tuned React SPA over this any day of the week.</text></item></parent_chain><comment><author>JamesSwift</author><text>Ive never heard of the Doherty Threshold, but looking it up, it seems that its actually saying &amp;gt; 400 ms &amp;quot;is painful&amp;quot;, not that its &amp;quot;imperceptible&amp;quot;. And that aligns with previous rules of thumb I&amp;#x27;ve used for mobile UX -- you generally want things to be &amp;lt; 100ms, and ideally &amp;lt; 50ms. If something results from user interaction the bar is much closer to the 50ms side of the range.</text></comment>
<story><title>DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search</title><url>https://m.twitter.com/dhh/status/1275901955995385856</url></story><parent_chain><item><author>ch4s3</author><text>&amp;gt;  the UX is fairly laggy&lt;p&gt;I don&amp;#x27;t really find that to be the case. All of the actions seem to be done for me in under 400ms which is to say under the Doherty Threshold. That mean&amp;#x27;s that they are largely imperceptible. Sure it doesn&amp;#x27;t have fancy animations, but there isn&amp;#x27;t really any time for them.&lt;p&gt;Can you cite an example of a popular React SPA that is less &amp;quot;laggy&amp;quot; in your opinion? I&amp;#x27;m curious to compare the UX.</text></item><item><author>piazz</author><text>Noteworthy how they tout the success of their &amp;quot;magic&amp;quot; frontend stack made with vanilla JS, lack of a trendy framework, etc. But if you use the app, the UX is fairly laggy, requires frequent refreshes, all the animations and interactions are off - the list goes on and on. It&amp;#x27;s noticeably subpar (and I &lt;i&gt;like&lt;/i&gt; Hey).&lt;p&gt;Seems to me that the proof is in the pudding wrt their stack, but it&amp;#x27;s probably not what they wanted to prove. I would take a well tuned React SPA over this any day of the week.</text></item></parent_chain><comment><author>piazz</author><text>Sure, a fairly best in class example would probably be Notion. Switch between pages, move some elements around, etc. There&amp;#x27;s a level of interactivity and responsiveness that I just don&amp;#x27;t see with Hey.</text></comment>