Re:GitHub’s engineering team has moved to Codespaces
by soheil on Wednesday August 11, 2021 @01:47PM
(#28145242)
If you work from a park how do you manage your latency/connectivity to a remote server? It must get annoying fast when a pigeon flies over causing your hotspot to cut out.
[ Parent
| on HN ]
Re:GitHub’s engineering team has moved to Codespaces
by mbreese on Wednesday August 11, 2021 @01:51PM
(#28145282)
I think the point is that a small random drop in latency affects the local connection, but not the remote server. So, if your SSH connection is a little flakey for a minute, that’s fine. The remote server is itself stable. It is also likely connected to a much bigger pipe, so pulling in a remote container is much faster than if you were doing the same thing from your laptop in the park.
If you’re worried about your SSH connection being stable, mosh is another option.
Re:GitHub’s engineering team has moved to Codespaces
by JoeQuery on Wednesday August 11, 2021 @01:59PM
(#28145373)
Exactly this. I used a combination of mosh, byobu, gnu screen, and vim. These days I use vscodes remote development setup more often.
Re:GitHub’s engineering team has moved to Codespaces
by tpoacher on Wednesday August 11, 2021 @02:33PM
(#28145852)
Mosh sounds interesting! Thanks for mentioning!
Re:GitHub’s engineering team has moved to Codespaces
by theshrike79 on Thursday August 12, 2021 @03:05AM
(#28152986)
On the front page right now: https://news.ycombinator.com/item?id=28150287 =)
Re:GitHub’s engineering team has moved to Codespaces
by soheil on Wednesday August 11, 2021 @02:46PM
(#28146018)
If latency is high/nondeterministic every time you hit refresh in your browser to see your dev changes the delay gets compounded, productivity suffers and frustration intensifies.
Re:GitHub’s engineering team has moved to Codespaces
by albertgoeswoof on Wednesday August 11, 2021 @01:52PM
(#28145299)
Files are stored in memory locally so there’s no network trip when editing, only on save, and it’s kilobytes per edit in the worst case
Re:GitHub’s engineering team has moved to Codespaces
by brian_herman on Wednesday August 11, 2021 @01:49PM
(#28145265)
He could use something like GNU screen, or tmux, or his server could use something like XRDP or even RDP to continue when his connection goes out.
Re:GitHub’s engineering team has moved to Codespaces
by JoeQuery on Wednesday August 11, 2021 @02:06PM
(#28145478)
Hah! Thankfully that doesn't happen too often. Worst thing that happens is I forget to turn off my Hotspot when I get home and drop into a Zoom meeting on it and use all my 4g data on accident.
Re:GitHub’s engineering team has moved to Codespaces
by jimmyvalmer on Wednesday August 11, 2021 @02:04PM
(#28145440)
I believe he's using the word "work" very loosely here.
Re:GitHub’s engineering team has moved to Codespaces
by JoeQuery on Wednesday August 11, 2021 @02:08PM
(#28145509)
I don't know what you mean by this. I've often worked in the park so I can be around my kids playing and get some more glimpses of them growing up than I otherwise would in an office. Plenty of commits have been made at a picnic table.
Re:GitHub’s engineering team has moved to Codespaces
by jimmyvalmer on Wednesday August 11, 2021 @02:11PM
(#28145553)
I mean your work suffers when you're distracted by pigeons and small children.
Re:GitHub’s engineering team has moved to Codespaces
by JoeQuery on Wednesday August 11, 2021 @02:15PM
(#28145614)
I've never been one to go 8 hours straight. The refresher pays off in the long run. Not to say my way of working is any better, but the things get done and I'm more satisfied with my work life balance.
And with us soon going back to home schooling (thanks delta...) children happily playing outside is much less distracting than pent up children yelling inside. And mama can't do it all.
Re:GitHub’s engineering team has moved to Codespaces
by whateveracct on Wednesday August 11, 2021 @02:19PM
(#28145664)
eh let it suffer
even my (and many devs') "suffering" work is worth good money - or at least our employers continue to think so :)