Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CDC File Transfer

github.com

Post reply on HN
Print view View original

131–140 of 229 posts

Re: CDC File Transfer

#131

Post by dijit »

winrid wrote: post #106

So game devs had to port their games to Linux to run on Stadia servers? That seems like a huge bottleneck...

Yes, it was a contentious topic when I was working on The Division and its sequel, since it runs on a game engine that was built in house.

However, even though the games did not ship on Linux proper, the work that went in to supporting stadia had a profound effect on the games ability to work under WINE.

People often overlook Stadia as putting significant pressure on devs to support Linux, and give a lot of credit to Valve, but the reality is that both are responsible.

Re: CDC File Transfer

#132

Post by dijit »

verdverm wrote: post #114
disqard wrote: post #109

Earlier quoted context omitted.

Yes, this was a core architectural requirement of Stadia (running the games on Linux), as opposed to hosting virtualized Windows machines (which would've allowed serving up Windows-based games). Whether this specific design choice alone killed Stadia, no one can say -- but it was probably one of the most important factors in its demise.

Input lag and pixelated graphics is why I quit, I had gigabit fiber at the time

Likely it was caused by your computer and browser not playing nice with x265 hardware decoding, I used to run the gamelet on the same network as my desktop and would get the same on some configurations.

Frustratingly, it was not easy to know at a glance that this was what was happening, but there were times (many times, actually) where my chromecast ultra at home was performing much better with Stadia than my gaming PC

Re: CDC File Transfer

#133

Post by yellow_lead »

c7b wrote: post #130

Slightly OT, but I like the schematic gifs used in the Readme.md (pretty amazing doc overall!) like this one [0]. Does anyone have suggestions what tools they might have used (or might be used in general) to create those? [0] https://github.com/google/cdc-file-transfer/blob/main/docs/l...

Maybe just draw.io plus Photoshop or some gif generator. The gifs don't look very complicated

Re: CDC File Transfer

#134

Post by Topgamer7 »

dleslie wrote: post #60
adastra22 wrote: post #46

Earlier quoted context omitted.

> I sort of took it for granted that people would spend the extra twenty bucks or so to make work from home a painless experience I think you took for granted the mere availability of fiber as an option. 30Mbps DSL is the best option I have, other than Starlink. And I live in San Jose!

You're not wrong. It's amazing how poor access can be. I live in a tiny town on Vancouver Island and I have gigabit symmetric, for a very reasonable price. When I lived in Vancouver that simply wasn't an option.

The Canadian government gives grants to telecoms to install fibre. And I think there is some relation to signing up end users too but I can't recall.

Re: CDC File Transfer

#135

Post by raverbashing »

manigandham wrote: post #103
raverbashing wrote: post #84

The real question is, why is this not part of the base internet protocols already? Only goes to show how TCP is not as reliable as it should

What does this have to do with TCP being reliable?

If TCP was reliable enough, then these chuncked transfers wouldn't need to be used

Re: CDC File Transfer

#137

Post by Tor3 »

LarryMullins wrote: post #126
remus wrote: post #123

Earlier quoted context omitted.

> Funding the development of yet another file transfer utility, interesting as this one is, definitely wasn't necessary. Interesting you say that as I thought they explained their motivation pretty clearly. Is there a tool they missed that already does the job?

I think most companies would have used an off the shelf solution and expected devs to simply deal with the inefficiency.

For devs it's only inconvenient and annoying, but for the devs' company the inefficiency means money. At our company we were almost all of us working remotely during the pandemic (and many still do), and anything which slowed down or made a developer inefficient was looked at and improved on where possible. Because it's about (though not only about) money.

Re: CDC File Transfer

#138

Post by ljusten »

c7b wrote: post #130

Slightly OT, but I like the schematic gifs used in the Readme.md (pretty amazing doc overall!) like this one [0]. Does anyone have suggestions what tools they might have used (or might be used in general) to create those? [0] https://github.com/google/cdc-file-transfer/blob/main/docs/l...

We used an internal Chrome extension to capture the gifs. There also seem to be some externally available GIF capturing tools, like https://chrome.google.com/webstore/detail/chrome-capture-scr... (disclaimer: I haven't tried those). We then used https://ezgif.com/optimize to remove dupe/unwanted frames, tweak timings and compress the gif. The actual content was done in Google Slides.

Re: CDC File Transfer

#140

Post by ddalex »

cwaffles wrote: post #99

CDC slides explaining the algorithm: https://www.usenix.org/sites/default/files/conference/protec...

What I don't get is how are the Gear CDC constants (the lookup table for gears) generated. Any insight ?
Post reply on HN