Sunshine VS parsec

> Would the Swift UI also work on an iPad?

Yes, but probably not for the first version.

> Do you have any comparisons with other tools (eg steam streaming, moonlight)

Steam streaming just doesn't really work on linux. Moonlight is somewhat similar in terms of direction, and has an established client base. I know of at least two projects to build servers for the Moonlight protocol[1][2].

The Moonlight protocol is a bit weird, because it's an open-source reverse engineering of a dead NVIDIA project, GeForce now. There are fundamental limitations to the protocol, for example that the cursor must be rendered in-stream or simulated. Using my tool, the cursor is rendered locally, and custom cursor images can actually be pushed to the client, for a seamless experience. This sounds like a minor detail but it matters a lot for subjective latency. I'm also working on employing tricks like hierarchical coding using FEC in the protocol, because I hate VBR encoding for games (it makes text blurry and breaks immersion). Those tricks aren't really possible in Moonlight.

All of the Linux solutions I know about have significantly higher latency compared to Magic Mirror, although I don't have numbers for exactly how much higher. (I have a benchmark to test the latency of my tool, but the others don't.) I'd encourage you to try them out and get a feel for the difference.

Finally, I think Magic Mirror is the easiest to install and get going on the server. It has almost zero runtime library or service dependencies (there's a pesky dynamic link against libxkbcommon which I haven't managed to remove), so you don't need to mess with pipewire or docker or anything - it's completely self-contained.

All that said, the existing tools have the advantage of a larger user and contributor base, whereas Magic Mirror is just me on a mission so far :) So they're likely to be much more stable and usable.

[1]: https://github.com/LizardByte/Sunshine

RDP as a regular or quick solution is actually really decent in this respect.

(1) https://app.lizardbyte.dev/Sunshine

Moonlight + Sunshine for a self hosted solution, works with every OS

server: https://github.com/LizardByte/Sunshine/

client: https://github.com/moonlight-stream

You could use sunshine (https://github.com/LizardByte/Sunshine) + moonlight (https://github.com/moonlight-stream/moonlight-qt). To be honest, at least for me, it works better than most of the RDP/VNC stuff.

EDIT: Just checked again, original was released early 2020, current maintained project started 2022.

On your pc, install Sunshine. It's an open source moonlight server. There's a good walk through on the sunshine github page. Connect your handheld to the wifi running the server & open moonlight. Should work.

I discovered the moonlight client and sunshine server a few months ago. These are open source solutions to provide remote gaming/desktop capabilities with built in input and audio passthrough. I tried NoMachine, but I wasn't able to get audio to work. This looks like a known issue on arch. On sunshine, I didn't have to do any extra tweaking! This allowed me to game on my desktop pc without having to sit at my desk. This was especially helpful while watching my 2nd son. I was really impressed by the performance, I could stream my host's display at high resolutions and frame rates with low latency despite my desktop being in the basement using WiFi. I was getting some instability with WiFi, so I wanted to try connecting my desktop to the router via Ethernet. I decided to go with a headless solution because that gives me more flexibility on the placement of the desktop; I ended up moving my desktop upstairs closer to my router. I figured out a way to stream my hosts display headless by using Nvidia TwinView to create the virtual display. This means I don't need to buy any HDMI/DP dummy plugs. I wrote a Linux Guide for sunshine on how to set this up. If you have any feedback on this guide, let me know! I haven't tried this, but wolf is an interesting docker alternative to sunshine.

Writing Haskell programs that rely on third-party packages is still an issue when it’s a not actively maintained package. They get out of date with the base library (Haskell’s standard library), and you might see yourself in a situation where you need to downgrade to an older version. This is not exclusive to Haskell, but it happens more often than I’d like to assume. However, if you only rely on known well-maintained libraries/frameworks such as Aeson, Squeleto, Yesod, and Parsec, to name a few, it’s unlikely you will face troubles at all, you just need to be more mindful of what you add as a dependency. There’s stackage.org now, a repository that works with Stack, providing a set of packages that are proven to work well together and help us to have reproducible builds in a more manageable way—not the solution for all the cases but it’s good to have it as an option.

The Parsec library for Haskell uses combinators, and there are a few good resources around the internet which explore it, if you know Haskell.

Parse the expression using parsec library ( if you're unfamiliar with it please check out https://hackage.haskell.org/package/parsec) it's a strong library for parer combinators. Once you parse the expression u need to define and sum up the similar terms. Check this example out - https://fpunfold.com/2020/05/18/making-a-calculator-in-haskell-with-parsec.html

Konbini is a functional parser combinator library inspired by Haskell parsing libraries like Parsec. It's (hopefully) fairly easy to use, and is about as performant as the better-parse library. In fact, it's quite similar to better-parse in many aspects. The main difference is in how parsers are composed. Where better-parse prefers operators and infix functions, Konbini instead uses plain functions.

Hi everyone, I'm learning F# and currently trying to do a Parsec-like CE, just to get comfortable with computation expressions.

good libraries for parsing: parsec, attoparsec etc.

Thank you! When I read the title I only knew about https://hackage.haskell.org/package/parsec, and for a moment I was very confused…

The more "idiomatic" way would be to use a parser library, e.g. parsec, attoparsec, or megaparsec. But even then I think it would be a lot easier to maintain if you could preserve the angle brackets <> in the input.