3 ms·

Just a little feedback: the typing does not keep up with me (and I only type around 80wpm), and lags so far behind that I can get around 15-20 characters in bef

Just a little feedback: the typing does not keep up with me (and I only type around 80wpm), and lags so far behind that I can get around 15-20 characters in before it registers that a mistake was made 15 characters ago. I'm running it on Firefox, on Windows 10. Based on other responses, I'm assuming this doesn't happen for everyone, so if it's just me, feel free to ignore. Just putting it out there in case you'd like to investigate.

amalgamated_inc 4y ago
15 characters ago feels excessive, I get maybe 1-2 at 120-140wpm. Do you know what your ping to the US east coast is?
- catapart 4y ago
  Yeah, it definitely feels sluggish, so I assumed it was bugging out. It started pretty snappy and then slowed way down. Ping tester says somewhere between 50 and 75ms to Amazon's Virginia center.
  - amalgamated_inc 4y ago
    I think it ran out of memory and the BEAM crashed and restarted. Gave it a bit more memory, hoping it'll hold out haha
    - catapart 4y ago
      Ha ha! Nice. Yeah, I saw on another comment that you're apparently running this with SSR, which is pretty crazy, to me! I'm surprised it's as snappy as it is, honestly, but the lag makes a lot of sense, now. Also shocked that you'd want to incur that much bandwidth cost - assuming you're being charged for it. Something like this should be able to run in the client effortlessly, so I would think even experimenting with SSR, you'd want to do most of the processing client side and then just dribble in the server re-renders, for more batched processing. In any case, good job! Definitely does the thing you set out to do with it, and is a clear demonstration of SSRs capabilities (and current weaknesses).
- deleted 4y ago
  [deleted]
- weeksie 4y ago
  I'm in NY and this was happening for me. I'd be 10-15 characters down and get a stream of red. One thing that was sort of annoying is that because it's using a custom text box (or something) when I control-w to kill the previous word for an error, nothing happens. I tried option-delete as well but no luck.
  - amalgamated_inc 4y ago
    You can do ctrl-backspace or meta-backspace. I tried ctrl-w but that actually closes the window in Firefox :D
ipython 4y ago
Same, I just clocked 199 wpm and at times I actually had to wait for the screen to catch up before I could continue typing (Firefox on macOS)
- amalgamated_inc 4y ago
  Holey moley, 199?! Did you run out of text?
  - ipython 4y ago
    shrug it's what it showed me when I finished. I think it overestimated my speed near the end as it seemed to respond slower as I got further along in the text. Cool demo tho! I should show it to my kids, they'll have a kick out of it.
LastNevadan 4y ago
I confirm this comment: the UI is way too slow for what it is trying to measure. I also type about 80 WPM and found the response speed of this site unbearable. Also using Firefox on Windows 10.
KomoD 4y ago
Yep, extremely laggy, makes it impossible to type correctly at a decent speed (100+)

amalgamated_inc 4y ago

15 characters ago feels excessive, I get maybe 1-2 at 120-140wpm. Do you know what your ping to the US east coast is?

catapart 4y ago
Yeah, it definitely feels sluggish, so I assumed it was bugging out. It started pretty snappy and then slowed way down. Ping tester says somewhere between 50 and 75ms to Amazon's Virginia center.
- amalgamated_inc 4y ago
  I think it ran out of memory and the BEAM crashed and restarted. Gave it a bit more memory, hoping it'll hold out haha
  - catapart 4y ago
    Ha ha! Nice. Yeah, I saw on another comment that you're apparently running this with SSR, which is pretty crazy, to me! I'm surprised it's as snappy as it is, honestly, but the lag makes a lot of sense, now. Also shocked that you'd want to incur that much bandwidth cost - assuming you're being charged for it. Something like this should be able to run in the client effortlessly, so I would think even experimenting with SSR, you'd want to do most of the processing client side and then just dribble in the server re-renders, for more batched processing. In any case, good job! Definitely does the thing you set out to do with it, and is a clear demonstration of SSRs capabilities (and current weaknesses).
deleted 4y ago
[deleted]
weeksie 4y ago
I'm in NY and this was happening for me. I'd be 10-15 characters down and get a stream of red. One thing that was sort of annoying is that because it's using a custom text box (or something) when I control-w to kill the previous word for an error, nothing happens. I tried option-delete as well but no luck.
- amalgamated_inc 4y ago
  You can do ctrl-backspace or meta-backspace. I tried ctrl-w but that actually closes the window in Firefox :D

ipython 4y ago

Same, I just clocked 199 wpm and at times I actually had to wait for the screen to catch up before I could continue typing (Firefox on macOS)

amalgamated_inc 4y ago
Holey moley, 199?! Did you run out of text?
- ipython 4y ago
  shrug it's what it showed me when I finished. I think it overestimated my speed near the end as it seemed to respond slower as I got further along in the text. Cool demo tho! I should show it to my kids, they'll have a kick out of it.

LastNevadan 4y ago

I confirm this comment: the UI is way too slow for what it is trying to measure. I also type about 80 WPM and found the response speed of this site unbearable. Also using Firefox on Windows 10.

KomoD 4y ago

Yep, extremely laggy, makes it impossible to type correctly at a decent speed (100+)