<story><title>How I made Google’s data grid scroll faster with a line of CSS</title><url>https://medium.com/@johan.isaksson/how-i-made-googles-data-grid-scroll-10x-faster-with-one-line-of-css-78cb1e8d9cb1</url></story><parent_chain><item><author>lxe</author><text>I&amp;#x27;ve been doing web development for 20 years now. I don&amp;#x27;t know if it&amp;#x27;s strictly endemic to web or frontend, but I feel like we&amp;#x27;re solving the same problems over and over again, using the same low levels of abstraction.&lt;p&gt;There&amp;#x27;s no reason for lists to scroll slowly after so many years of scrolling lists. There should just be one way to do a scrolling list, implemented natively and left alone. Yet, in web development, there&amp;#x27;s always a new and different way to do a thing, with either new, or pretty much the same ways for things to be broken.&lt;p&gt;Grumble grumble</text></item></parent_chain><comment><author>wildrhythms</author><text>I work in UX, I am constantly being given designs that don&amp;#x27;t work well with native&amp;#x2F;semantic elements- a great example is tables. As soon as the table needs some kind of animation, drag-drop behavior, anything like that, I can&amp;#x27;t use a &amp;lt;table&amp;gt; anymore; or it becomes some frankenstein kafkaesque amalgamation that is impossible to maintain. Does the table really need an animation? (probably not) drag and drop? (probably not) But management and the people in charge of OK&amp;#x27;ing these designs have a &amp;#x27;make-it-happen&amp;#x27; attitude and nobody really cares about semantic, native feel when they&amp;#x27;ve invested so much into a &amp;quot;design system&amp;quot; that is largely antithetical to that.&lt;p&gt;Select elements are the bane of my existence. Impossible to style. I am constantly re-implementing a &amp;lt;select&amp;gt; because it has to look a certain way. Just terrible.</text></comment>
<story><title>How I made Google’s data grid scroll faster with a line of CSS</title><url>https://medium.com/@johan.isaksson/how-i-made-googles-data-grid-scroll-10x-faster-with-one-line-of-css-78cb1e8d9cb1</url></story><parent_chain><item><author>lxe</author><text>I&amp;#x27;ve been doing web development for 20 years now. I don&amp;#x27;t know if it&amp;#x27;s strictly endemic to web or frontend, but I feel like we&amp;#x27;re solving the same problems over and over again, using the same low levels of abstraction.&lt;p&gt;There&amp;#x27;s no reason for lists to scroll slowly after so many years of scrolling lists. There should just be one way to do a scrolling list, implemented natively and left alone. Yet, in web development, there&amp;#x27;s always a new and different way to do a thing, with either new, or pretty much the same ways for things to be broken.&lt;p&gt;Grumble grumble</text></item></parent_chain><comment><author>vaughan</author><text>There is not one set of static requirements for lists. New UX paradigms are being invented all the time, which actually make things more usable.&lt;p&gt;E.g. Think about Airtable vs Google Sheets.&lt;p&gt;Also consider data sources and data binding. Do you bind a cell, a row, the entire table? How do you handle real-time updates or infinite scrolling. How is styling done?&lt;p&gt;It always feels like we should just standardize the current thing because we cannot see what will come next.&lt;p&gt;That said, there still does not feel like a good data grid for React, and trying to build one makes it feel like React is just getting in the way.</text></comment>