Anyone have workflows or tooling that are highly compatible with the entrenched notebook approach, and are easy to adopt? I want to prevent theses people from learning well-trodden lessons the hard way.
That said, I consider `just` very language-agnostic and useful because of that, and I consider mix pretty bad at any workflow needs that isn't directly concerned with BEAM.
Last I tried using the .kube files I ran into issues with specifying container networks (https://github.com/containers/podman/issues/12965).
This is sort of "fixed" by using a Quadlet ".kube" but IMO that's a pretty weak solution and removes the "here's your compose file, run it" aspect.
Recently (now that Deb13 is out with Podman 5) I have started transitioning to Podmans Quadlet files which have been quite smooth so far. As you say, its great to run things without all the overhead of kubernetes.
I agree about quadlets, amazing.
Docker has one of the most severe cases of not-invented-here. All solutions require a combination of a new DSL, a new protocol, a new encryption scheme, a new daemon, or any combination there-of. People are sleeping on using buildah directly; which OP alluded to with Bakah (but fell short of just using it directly).
Ever wish you could run multiple commands in a single layer? Buildah lets you do that. Ever wish you could loop or some other branching in a dockerfile? Buildah lets you do that. Why? Because they didn't invent something new, and so the equivalent of a dockerfile in buildah is just a script in whatever scripting language you want (probably sh, though).
This will probably give you the general idea: https://www.mankier.com/1/buildah-from
I came across this when struggling and repeatedly failing to get multi-arch containers built in Circle CI a few gears ago. You don't have access to an arm64 docker context on their x86 machines, so you are forced to orchestrate that manually (unless your arm64 build is fast enough under qemu). Things begin to rapidly fall apart once you are off of the blessed Docker happy path because of their NIH obsession. That's when I discovered buildah and it made the whole thing a cinch.
We need to stop participating in this brouhaha as an industry. If your employer wanted to demonstrate loyalty you would see it in your contract.
Operating a business is hard? Well, yes, so is surviving.
Edited to Add:
Yeah, the above seems right. This seems like standard fare. See the below FAQ from https://philzcoffee.com/stakeholderfaqs:
How many employees who invested in your company lost their money and/or stock options as a result of this transaction?
A total of 10 former employees who chose to invest in Philz Coffee by buying common stock years ago at much higher prices than the current price of the shares will unfortunately lose the value of that stock. There are no other Philz Coffee common stockholders or broader group of Philz common stockholders who were affected by the transaction and no current employees are Philz common stockholders who were affected by the transaction. Additionally, out of our approximately 1,500 current employees, 47 were granted stock options (the right to buy stock at a certain price in the future) in 2022 and earlier that are not exercisable based on the current price of the shares. Unfortunately, those options will expire per their original terms, but since the employees did not buy stock, they did not lose any money.
(I'm accepting it because "Transfers"/"T" as unit is quite rare outside of PCIe)
Personally, I would learn any of them for a job - but not for joy. Exceptions subtract joy.
V is definitely worth looking at (but I have found the time yet).