While I think the cynicism is well-earned, we should pay attention to when we’re proven wrong and highlight when companies do something right. Bitwarden’s fuck-up gave them an opportunity to signal that they’re not intending to build a wall for their garden, and they took it.

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

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.

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.