Wasn’t that OrangePi?

C because it’s what is used for low-end linux & embedded work.

Shell scripts because they’re the caulk that holds a Linux distro together.

Rust when possible because it’s how I wish systems programming could be.

I use PiHole+Unbound in a podman quadlet, and give it its own macvlan. Works great for me.

Did the citizens of that country take the loan? No

Did they benefit at all from the loan? No

Did the world bank make any effort to ensure the above were answered ‘yes’? No

When you make a leveraged loan are you supposed to be guaranteed that the it was risk free? No

If leveraged loans could be made risk-free ‘breal your legs’ style the way the world bank does to countries, banks would be offering loans to every punter who wanted to bet on the dogs.

deleted by creator

No, I’m saying that when people run into strange bugs, sometimes they put together an issue (like the person behind cve-rs), and sometimes they quietly work around it because they’re busy.

Seeing as I don’t often trawl through issues on the language git, neither really involve notifying me specifically.

My lack of an anecdote does not equate to anecdotal evidence of no issue, just that I haven’t met every rust developer.

Yes, the problems rust is solving are already solved under different constraints. This is not a spicy take.

The world isn’t clamoring to turn a go app into rust specifically for the memory safety they both enjoy.

Systems applications are still almost exclusively written in C & C++, and they absolutely do run into memory bugs. All the time. I work with C almost exclusively for my day job (with shell and rust interspersed), and while tried and tested C programs have far fewer memory bugs than when they were first made, that means the bugs you do find are by their nature more painful to diagnose. Eliminating a whole class of problems in-language is absolutely worth the hype.

If someone did, why would I hear of it?

The code used in cve-rs is not that complicated, and it’s not out of the realm of possibility that somebody would use lifetimes like this if they had just enough knowledge to be dangerous.

I’m as much a rust evangelist as the next guy, but part of having excellent guard rails is loudly pointing out subtle breakages that can cause hard to diagnose issues.

The link you posted has nothing to do with this SoC?

You’re not going to get 2.5G over wireguard on the 3588, but you are definitely going to get over 1G.

Wireguard scales well with cores, but due to the way big.LITTLE is implemented on the 3588, it could lose performance if it tries to split the workload between core complexes.

I’m honestly more worried about science communicators projecting life-changing properties onto it because “superconductor”, and then the public coming away with “these scientists are all hyperbolic hacks”.

This looks a lot less like diamagnetism than the previous videos, but is still using way larger magnets than they should need; still very sceptical.

Also a reminder to anybody reading a news article about this: LK99 is likely a ceramic, so the attributes specifically for metallic superconductors would not apply.

As far as ARM SBCs go, I’d say B tier. Not as good as a RaspberryPi or RockPi but armbian installed great. Had a pain debugging the rockchip video decoder in a container, and still have issues with USB hard drives.

If you’re coming from x86_64, be prepared for some unique challenges.

• *arr media services
• tailscale
• mullvad
• Jellyfin
• qbittorrent
• pihole
• unbound
• Minecraft server
• Portainer-CE

On an OrangePi with a powered USB hub using a bunch of SSDs.

All except the Minecraft server running on Podman.

The GPU driver should already be in mesa, no?

I haven’t managed to get the GPU properly working when passed through to a Jellyfin docker container, I think you need to recompile ffmpeg or something. If you can get that working I imagine the G610 would be great for it.

Software transcoding though has been great, I don’t need it too often but it’s a lot beefier than the Pi4 so I’ve had no troubles.

I don’t know much about other alternatives, but my understanding is they’ll mostly be between the performance of the Pi and any RK3588 board like the OrangePi. When you’re looking for one, make sure it has an armbian image.

Edit: I managed to get hardware transcoding using docker.io/jjm2473/jellyfin-mpp.

What do you intend to use it for? I replaced my ryzen box with an OrangePi5 for power consumption reasons. Obviously the performance is not even close but turns out it was enough for Jellyfin, torrenting, pihole, and a Minecraft server.