4 ms·

Debugging won't be a problem if the dev environment is on the cloud. 100ms latency works fine with Remote Desktop Protocol when typing. However, I don't agree w

Debugging won't be a problem if the dev environment is on the cloud. 100ms latency works fine with Remote Desktop Protocol when typing. However, I don't agree with the article for other reasons.

viraptor 4y ago
It really doesn't work well. As in, people who touch type are slowed down if there's 100ms delay. Moving the cursor around is also awkward, because you're often pressing a key multiple times per second or rely on repeat rate which does the same. I do it once a week or so (for a very short time) and would rage quit any job requiring this every day.
- spc476 4y ago
  I have to fill in a "time card" each week. The old system was a simple web page that I could navigate primarily via keyboard, tabbing from field to field. I think it was a company-developed web app, so the people who made it also had to use it. Then that was scrapped for an "enterprise solution." This is is also a web app, but it's slow. You have to click in a field, watch as the selection menus are filled in in a second or two (as the gigabytes of Javascript pulls data in via a database query in real time), and if it's a text field, you have to click in it, type real slowly, and click out of it. Don't tab to the next field because the tab key doesn't work as expected. What used to take a few seconds to fill out a days' worth of time now takes a few minutes. The C-suite, who bought into this crap, don't have to use it because that's what secretaries^Wassistants are for. If this is the future of computing, I want off at the next stop.
  - Karrot_Kream 4y ago
    At work we have a support portal, to help customer support folks out. It relies on queries through a legacy service to a legacy DB. Increased row counts in the DB (ish because this isn't SQL) have caused high query latency resulting in frequent timeouts, and the legacy service that manages the queries keeps constantly timing out. Our team owns it but management will never sign off on resources to fix it. None of the technical staff or upper management at the company uses the support portal so they don't care. Support folks don't have any way of offering feedback to us or our management in a way that threatens our careers. The result is that it never gets worked on and support continues complaining without anything ever happening. I spent my free time coming up with fixes but ran out of time to tie up loose ends. I'll be tasking an intern with doing that, so the support people can finally use the portal and not want to rip their hair out. This is what happens when you aren't forced to use a system and customer feedback has no effect on you, as is the case for most enterprise software. Have you tried to use Puppeteer or Selenium to automate the timecard entry? That might help reduce the pain.
Macha 4y ago
> 100ms latency works fine with Remote Desktop Protocol when typing. This may be the crux of the issue. I've been confused when proponents of the idea indicate the experience is fine or preferable to local use as if the latency wasn't there. I don't think we can agree if one side thinks 100ms latency when _typing_ is ok. Meanwhile other people are giving some of the new terminals flac for having 40ms vs 10ms latency (https://danluu.com/term-latency/ https://danluu.com/term-latency/). I tend to agree with the second group more.

Debugging won't be a problem if the dev environment is on the cloud. 100ms latency works fine with Remote Desktop Protocol when typing. However, I don't agree with the article for other reasons.

viraptor 4y ago

It really doesn't work well. As in, people who touch type are slowed down if there's 100ms delay. Moving the cursor around is also awkward, because you're often pressing a key multiple times per second or rely on repeat rate which does the same. I do it once a week or so (for a very short time) and would rage quit any job requiring this every day.

spc476 4y ago
I have to fill in a "time card" each week. The old system was a simple web page that I could navigate primarily via keyboard, tabbing from field to field. I think it was a company-developed web app, so the people who made it also had to use it. Then that was scrapped for an "enterprise solution." This is is also a web app, but it's slow. You have to click in a field, watch as the selection menus are filled in in a second or two (as the gigabytes of Javascript pulls data in via a database query in real time), and if it's a text field, you have to click in it, type real slowly, and click out of it. Don't tab to the next field because the tab key doesn't work as expected. What used to take a few seconds to fill out a days' worth of time now takes a few minutes. The C-suite, who bought into this crap, don't have to use it because that's what secretaries^Wassistants are for. If this is the future of computing, I want off at the next stop.
- Karrot_Kream 4y ago
  At work we have a support portal, to help customer support folks out. It relies on queries through a legacy service to a legacy DB. Increased row counts in the DB (ish because this isn't SQL) have caused high query latency resulting in frequent timeouts, and the legacy service that manages the queries keeps constantly timing out. Our team owns it but management will never sign off on resources to fix it. None of the technical staff or upper management at the company uses the support portal so they don't care. Support folks don't have any way of offering feedback to us or our management in a way that threatens our careers. The result is that it never gets worked on and support continues complaining without anything ever happening. I spent my free time coming up with fixes but ran out of time to tie up loose ends. I'll be tasking an intern with doing that, so the support people can finally use the portal and not want to rip their hair out. This is what happens when you aren't forced to use a system and customer feedback has no effect on you, as is the case for most enterprise software. Have you tried to use Puppeteer or Selenium to automate the timecard entry? That might help reduce the pain.

Macha 4y ago

> 100ms latency works fine with Remote Desktop Protocol when typing. This may be the crux of the issue. I've been confused when proponents of the idea indicate the experience is fine or preferable to local use as if the latency wasn't there. I don't think we can agree if one side thinks 100ms latency when _typing_ is ok. Meanwhile other people are giving some of the new terminals flac for having 40ms vs 10ms latency (https://danluu.com/term-latency/ https://danluu.com/term-latency/). I tend to agree with the second group more.