rustdesk-server VS rust

Run 2 instances of the Docker container rustdesk/rustdesk-server with hhbr and hhbs and it will work locally. It can also work in a single container with the s6 overlay variant.

https://github.com/rustdesk/rustdesk-server

WD=/opt/rustdesk #rm $WD/ -R mkdir -p $WD/{setup,data,web} cd $WD/setup cat << 'EOF' >docker-compose.yaml version: '3.7' #Links #https://hub.docker.com/r/rustdesk/rustdesk-server/tags #https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/docker/ #https://github.com/DoTheEvo/selfhosted-apps-docker/tree/master/rustdesk #https://github.com/rustdesk/rustdesk-server#s6-overlay-based-images #https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/relay/ #https://rustdesk.com/docs/en/dev/build/web/ services: rustdesk_server: container_name: rustdesk_server hostname: rustdesk_server image: ${SERVER_IMAGE} # network_mode: host networks: - rustdesk_net ports: - 21115:21115 - 21116:21116 - 21116:21116/udp - 21117:21117 - 21118:21118 - 21119:21119 volumes: - type: bind source: /opt/rustdesk/data/ target: /data environment: - 'TZ=${TZ}' - 'RELAY=${RELAY}' - 'ENCRYPTED_ONLY=${ENCRYPTED_ONLY}' - 'KEY_PUB=${KEY_PUB}' - 'KEY_PRIV=${KEY_PRIV}' rustdesk_web: container_name: rustdesk_web hostname: rustdesk_web image: pmietlicki/rustdesk-web-client:latest # network_mode: host networks: - rustdesk_net ports: - 5000:5000 volumes: #docker cp rustdesk_web:/app . #sed -i -e 's/supportdesk.itportaal.nl/sub.domain.com/g' ./app/build/web/main.dart.js #sed -i -e 's/OvYPJS8I5xV+d6sx3a7Ce9TVakfKdT3Zy3T7C1jjx+A=/PUBKEY/g' ./app/build/web/main.dart.js - type: bind source: /opt/rustdesk/web/app/ target: /app - type: bind source: /opt/rustdesk/data/ target: /root environment: - 'TZ=${TZ}' networks: rustdesk_net: driver: bridge EOF

git clone https://github.com/rustdesk/rustdesk-server.git --branch 1.1.7-4

Rustdesk also may or may not require the installation of a relay/rendezvous server, which is where the confusion starts: one may use the free Rustdesk public server, or install one's own, custom-built server, for which Rustdesk provides a "free open source and free server program"; dub this "server2."

Ever wanted to remotely access your desktop from anywhere, then tried software like TeamViewer, but it eventually stopped working? Try open source RustDesk that is simple to set up, and you can even self-host your own rendezvous/relay server (or use the free public server). RustDesk allows you to access your desktop computer from your BOOX device. I often use it to see what is going on when I am running some simulations remotely (below is a screenshot of my Tab Ultra accessing my laptop). Because I use a dark theme on all my LCD/OLED devices, I invert the display colors of my laptop to get a better-looking video feed on my Tab Ultra (I believe light themes look much better on e-ink).

The last I checked the Windows version of the server was a few versions behind. So if you use that version it might not have all the features of the current server version on Linux. You can go here https://github.com/rustdesk/rustdesk-server/releases and look for release 1.1.6-2 to find the Windows version of the server.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.

Another week, another dive into Rust. This time, we're delving into structs. Structs bear resemblance to interfaces in TypeScript, enabling the grouping of intricate data sets within an object, much like TypeScript/JavaScript. Rust also accommodates functions within these structs, offering a semblance of classes, albeit with distinctions. Let's delve into this topic.

There’s also other reasons. For example, take binary search:

* prefetch + cmov. These should be part of the STL but languages and compilers struggle to emit the cmov properly (Rust’s been broken for 6 years: https://github.com/rust-lang/rust/issues/53823). Prefetch is an interesting one because while you do optimize the binary search in a micro benchmark, you’re potentially putting extra pressure on the cache with “garbage” data which means it’s a greedy optimization that might hurt surrounding code. Probably should have separate implementations as binary search isn’t necessarily always in the hot path.

* Eytzinger layout has additional limitations that are often not discussed when pointing out “hey this is faster”. Adding elements is non-trivial since you first have to add + sort (as you would for binary search) and then rebuild a new parallel eytzinger layout from scratch (i.e. you’d have it be an index of pointers rather than the values themselves which adds memory overhead + indirection for the comparisons). You can’t find the “insertion” position for non-existent elements which means it can’t be used for std::lower_bound (i.e. if the element doesn’t exist, you just get None back instead of Err(position where it can be slotted in to maintain order).

Basically, optimizations can sometimes rely on changing the problem domain so that you can trade off features of the algorithm against the runtime. These kinds of algorithms can be a bad fit for a standard library which aims to be a toolbox of “good enough” algorithms and data structures for problems that appear very very frequently. Or they could be part of the standard library toolkit just under a different name but you also have to balance that against maintenance concerns.