

You can slam semicolons at the ends of lines in Python, interpreter doesn’t care
P sure you can do multiple lines in one line by slamming semicolons too, though idr for sure and I can’t be arsed to check


You can slam semicolons at the ends of lines in Python, interpreter doesn’t care
P sure you can do multiple lines in one line by slamming semicolons too, though idr for sure and I can’t be arsed to check
I just had some G Skillz DDR4 3200CL16 2x8GB go bad. Sticks had caused problems before. I lowered the clocks to 2133 and then it passed when I had instabilities before, but when they came back nothing changed it. Degredation I guess? Def odd for RAM, but maybe bad batch. Mine were made 2018 Sep.
Do clean the contacts and reseat to be sure.
But about a month ago I did the RMA form, had to email them to remind them to send me the info, got the RMA info, sent it in, and a week or so later they sent me back newly manufactured identical RAM sticks new in box.
There’s absolutely no info when you send it in till when you get it back, but they did send the replacement. You will be without RAM for a bit. They did not want an invoice since its lifetime babyyy
Containers lower the bar since the developer doesn’t need to make their program work on every system - just the container’s system.
Price we pay for more programs. And they bring boons like read-only, rootless, limited capabilities, and constrained perf limits (esp if you use Podman with Quadlets).
And don’t feel trapped - the Dockerfile is a recipe to build that program. Probably want to do it in an LXC container since it’ll want to use /data for its data or something. But the LXC container can also be run as a user but the program thinks it’s root. Plenty of security abounds!
I think it’s worth the price and you’re not trapped. They’re trapped with you and your robust Quadlet files