Comment by mary-ext

Comment by mary-ext 11 days ago

The animations makes it feel slow, the lack of any throttling/debouncing means that my input feels slow too.

hexo 11 days ago

The animations are always a deal breaker. And then WASM.

tipiirai 11 days ago

Are you talking about this 150,000 record Rust version?

akx 11 days ago

Yes. On that version, Chrome 134.0.6998.89's devtools on my Macbook (M2 Max) are indicating 100 to 250 millisecond interaction times and a 160 ms frame when entering text into the search field.

Reply View | 2 replies
- tipiirai 11 days ago
  
  I get the same numbers. Interestingly, JavaScript performs faster below 100,000 entries due to the lack of a JS-to-WASM bridge, but it eventually crashes when the records keep increasing
  
  Reply View | 1 reply
  
  dimgl 11 days ago
  
  Why would you ever have 100,000 entities on a page? What is the business use case for this?
  
  Reply View | 0 replies
petetnt 11 days ago

Loading the page on Fast 4G connection takes 9,61 seconds before I see _any_ content on the screen. This is loading the "all contacts" page that shows 12 items with a title, excerpt, time stamp and user name. Is this expected performance? Network shows the app downloading huge 4/1 megabyte chunks.

Reply View | 0 replies