yea steamlink is amazing BUT as far as I know, it cannot be used for arbitrary desktop streaming. You can certainly stream games wonderfully, but that's it.
Buy a Steam Link and a raspberry pi, and two usb eth adapters, create a ZeroTier network and configure the pi (openwrt) to get internet from one of the adapters and share both the internet connection and the zerotier connection over the second adapter. Configure the zerotier network on your computer and set ul Steam In-House streaming. Then you can take the pi and steam link anywhere, plug a mouse, keyboard and screen, and use your computer. I get 60fps at 1080p and no noticeable input lag over the internet (work to home).
If you use a nvidia card enable "force composition pipeline". There is also a Steam Link app for Android, and ZT client as well, works great.
ZeroTier is to fool the Steam Link to work over the Internet, or to improve latency?
How are the (physical) connections made? I understand one of the Pi USB/ETH adapters needs to be connected to the internet and the other to the native ETH Steam Link, what about the native ETH Pi port?
I bet it's using mesh networking a la ZeroTier, I have a similar setup, working on my home desktop while being at my customer's offices. I get 15-40ms latency, 1920x1080 at 60fps and no noticeable input lag. Gaming works really well, but I only really use it to code.
I keep saying I'll write on how to set this up for cheap, but I didn't find the time yet.
Basic recipe: fiber, zerotier, one raspberry pi and a steam link
Edit: latency above referrs the display latency, the latency between the machines is between 2 and 10 ms
Yeah but why? It's just applying CSS. You set the props, it applies those props as CSS. Why not cut out the middle man and just apply the css directly? And why is lazy loading bundled in? What's that got to do with image processing?
Why not cut out the middle man and just apply the css directly
Well one could extend this and argue that there's not need for frontend frameworks as you can manipulate the dom directly. Two way data binding is awesome.
I have no idea about the lazy loading.
And yeah, it's "kind of image processing".
Well, if you think that, why are you arguing over a submission about a component for one of those frameworks?
You think it's useless just because you don't use something like Vue?
I'm not sure if you're trolling or not at this point.
I wasn't saying "don't use Vue", I was saying there are good reasons to use a view layer library, and I used "VDOM" as a relevant example specifically because Vue implements one.
And two way data bindings are the best way to make a code base inscrutable. I'll put it another way. Wise developers avoid two way data bindings.
Vue components are structured in such a way (props, methods, data, computed properties, etc.) which is the same of the file you can find within the SRC folder of the project.
But what advantages does a Vue component offer over just doing the same thing with CSS? It's not going to be any more performant because it's not addressing a part of the rendering engine that Vue has any influence over. And you're not saving keystrokes because you've still got to instantiate the component and pass values to the props. All it does as far as I can tell is abstract away something that's trivial to do manually.
you can do steam in-home streaming over zerotier.
it's actually faster than geforce now
i have a raspberry set up so that i can plug it anywhere and work on my home computer
latency is so low that shooters are very much playable
you can use steamlink hardware as a client, or the newish raspberry pi release