I've got one of those, and it houses a system with 8 CPU cores, 32 GB RAM (can be upgraded to 64 if need be), 1 TB NVMe and 4 TB SSD - and it's all inside, whereas with an RPi the SSD would have to be external. The only thing that's collecting dust now is the old RPi.
If this were indeed the average attitude, there wouldn't be this big of an outcry with regards to the move from fully open-source to source-available licenses (Mongo/ELK/Hashicorp/etc.)
wrong: source-available means you can look but you can't incorporate/change/copy-paste/get-inspired-by. "look at this wheel, learn but don't make your own". It's a travesty.
Don't you ever get inspired by reading good books? You can learn new tricks and apply them elsewhere, and it's much easier than actually contributing to a big open-source project.
Is that really how source-available works? I mean whos stopping me from screenshotting and using tesseract or some other OCR tool to get the actual no-bullshit source code
FWIW I had decent success with Xpra on Linux, and it's still being actively developed, e.g. the HTML5 client is considered stable now: https://github.com/Xpra-org/xpra/
To set up an open-source service mesh, the infra team anyway has to configure a private certificate authority and cert-manager to create k8s secrets for the service mesh components. From there, it's straightforward to extend the common deployment template (hopefully there is one) to mount a volume with an auto-rotated certificate. All an application developer has to do is to use that certificate, which is much less effort than what you are implying.
It’s not less effort. I’ve done both ways in production for large teams. What you described is literally entirely automated by the mesh in a more secure and maintainable way than a bespoke hand rolled solution.
A secretary applies for a job; the interviewer asks her: "In your CV you claim that you can type 1000 characters per minute - for real?!" "Yes!", she replies, then adds in a low voice: "but such nonsense comes out..."
