3 ms·

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