Be the change. Make a dockerfile for it.
Follow the kbin install instructions, but convert them to dockerfile syntax.
Build it and push to docker.io or ghcr.io or whatever flavour you want.
Its a great learning experience, and containerisation is a huge part of the future (and present)
How the Linux kernel "made it" and is still free and open source is - imo - one of the pinnacles of humanity.
It's inspired so much other software to adopt the same philosophy, and modern humanity/science/society stands on those shoulders.
I think science has missed that boat.
Or that pinnacle was before the tools to support such an open source atmosphere/community were around... So not missed the boat, but swam before the boat was built
How to you vet papers that are being submitted?
If it is outside of your specific experience, how do you get someone else who is specialised to vet the paper?
Getting a blowjob wasn't the crime. Lying under oath was the crime.
Same with this. The sex and hush money isn't a crime, it's the false business records that are
It's not a 10s soindbite, nor a 144 character tweet.
Of course he has no idea what is going on
"broker" as a service-between-services is a great name
Invalidating creds sent over http is a great point!
It's sad. Also, not really surprising. KSP2 has had a very rough development cycle, and a very rough release.
Do they still support KSP?
No idea. Probably cause it's a bit gate-keepy in the way I say "any tuner worth their salt" as if it's the only way to achieve good results.
I haven't met a tuner that uses anything other than forks. Maybe that's because all the pianos I've worked with have been in good condition, so haven't needed drastic measures applied. As I haven't met a tuner that uses anything else, I can't say if they are better/faster/whatever. I just assumed it's the industry standard, like how orchestras tune by ear
I haven't, but I've had many grand and baby grand pianos tuned after being moved onto stage, and a guy comes in and does it by ear.
I asked them why they didn't have a stroboscopic tuner or something, and they've always found it easier with a couple forks and by ear
Im 99% sure any piano tuner worth their salt tunes by ear
It's not a workaround.
In the old days, if you had 2 services that were hard coded to use the same network port, you would need virtualization or a different server and make sure the networking for those is correct.
Network ports allow multiple services to use the same network adapter as a port is like a "sub" address.
Docker being able to remap host network ports to containers ports is a huge feature.
If a container doesn't need to be accessed outside of the docker network, you don't need to expose the port.
The only way to have multiple services on the same port is to use either a load balancer (for multiple instances of the same service) or an application-aware reverse proxy (like nginx, haproxy, caddy etc for web things, I'm sure there are other application-aware reverse proxies).