but there are literally dozens of strategies you probably don’t know about
Oh please tell me, wise old man! You can't be talking about garbage collection, reference counting, smart pointers, never-free, arenas, defer, or god forbid, the "I am perfect and can do it manually and never make mistakes" method. Because I know about all of those methods.
What are these other dozens of methods that I don't know about that mean Rust is unnecessary? 🙄
Sorry I misread, VNC is slow. RDP is a lot better. Does not appear to be rootless though, even though IIRC the RDP protocol does support that? I might have misremembered.
You have to launch an app, log in twice and then you get an annoying VNC-style remote desktop, not native windows. Also it doesn't run at all on Wayland. Apart from that it works pretty well - fast, and stuff like copy/paste works. I would just like something that is as convenient as remote X, but not dog slow.
Pretty unclear if this has any actual teeth - if you don't pay it says "don't create issues" etc. but is anyone going to stop you?
But let's assume that it did stop you. I'm going to give a dissenting opinion - I don't think it's a necessarily bad idea. Phabricator had that business model for years; without paying you got zero support. No ability to open issues, etc.
My company ended up paying for support... so that we could get support. There's absolutely no way they would have paid if it was a standard license and you could just open a GitHub issue, even if the issues were ignored.
Don't tease gossip? Either say "I'm quitting due to personal reasons" or give actual details "I'm quitting because I received ongoing abuse about being trans on X from several users and I'm fed up with it" (or whatever the reason was; I just guessed that).
Normally when I merge a PR I put the long PR message (if there is one) in the merge commit (again if there is one), rather than shitty Merge PR from patch1 that people seem to use.
If I'm not keeping the branch (usually PRs are not big enough to make preserving multiple commits useful) then I squash & merge which gives you the chance to edit the commit message and copy details from the PR message in.
Sorry rootless in this context means it doesn't have a big window showing the whole remote desktop, instead each remote window shows up as if it were a local window. Nothing to do with the root account. Kind of confusing, sorry!
Seems like one of the areas where Rust is least pressing, but I guess if uutils does become dominant it will be a lot easier to work on the code and add new features & tools.
I'm just asking for the same level of lag as I get from basic modern remote desktop solutions like Rustdesk, VMware VDI, Chrome, etc. As far as I know these all just capture the desktop, feed it into a standard low latency video codec and bob's your uncle. They achieve very good latency.
I currently use VMware VDI and it runs fine. All of these complex factors you've mentioned are not an issue at all. The only complexity is the actual integration with X/Wayland.
Yeah it's more complex. I don't think there's any more overhead though, and there's no reason it will be slow.
No, unfortunately not.