AFIK it’s only NVIDIA that allows containers shared access to a GPU on the host.
With the majority of code being deployed in containers, you end up locked into the NVIDIA ecosystem even if you use OpenCL. So I guess people just use CUDA since they are limited by the container requirement anyways.
That’s from my experience using OpenGL headless. If I’m wrong please correct me; I’d prefer being GPU agnostic.
I think the pine hobby panels will be fine structurally. I think you mean the ones that are a bunch of smaller pieces glued together. In using these I have found not all the glue joints are great, though.
But, I suspect its the glue in the plywood that might damage the saw. Glued up hobby panels will likely act the same.
Might want to pick up a cheap crosscut saw / general carpentry saw for utility cutting and save the nice pull saw four detail work.
I bet the people you work with are very happy to have you as a lead.
I’ve been in this scenario and I didn’t wait for layoffs. I left and applied my skills where shit code is not tolerated, and quality is rewarded.
But in this hypothetical, we got this shit code not by management encouraging the right behavior, and giving time to make it right. They’re going to keep the yes men and fire the “unproductive” ones (and I know fully, adding to the pile is not, in the long run, productive, but what does the management overseeing this mess think?)
Thanks for replying, instead of just downvoting!
I think the bloat is not (primarily) in the end users experience, but in the extra code that the nginx maintainers must now continue to support, test, etc on an ongoing basis, which is not core to its function as a http server and proxy.
To me, this change goes against the Unix philosophy of simplicity, modularity, and the idea that programs should do one thing well.
Nginx should not contain logic that is not expressly related to serving or proxying web requests. The content it serves is up to the end user.
If we accept this change, should they also provide localized versions of all the error pages, too? I’m happy if their responsibility ends at just serving the content I provide.
They were just trying to make us smarter.
https://studyfinds.org/chewing-on-wood-brain-function-memory/
[kidding]
To be fair, if you give me a shit code base and expect me to add features with no time to fix the existing ones, I will also just add more shit on the pile. Because obviously that’s how you want your codebase to look.
I’m not sure why no one is direct linking it.
(the data looks incredibly incomplete)
Good. You can already do this via custom pages. Leave the bloat out.
There is value in just using something like this to break spending habits of the population.
A lot of people may find that a portion of their spending wasn’t that necessary after all, and will stop beyond the boycott. The businesses will need to improve services or lower prices to win customers back.
At least, that’s what I hope this achieves. The organizers might have varying goals.
Check out ibuildit.ca
He has made a vise from a screw jack, and has some videos of it in action.
While I’ve not built his vise, I have roughly followed his instructions for other projects, and I think he really suggests things that actually work (not just “content”)
You really piqued my interest. I use docker/podman.
W/ an AMD graphics card, eglinfo on the host shows the card is AMD Radeon and driver is matching that.
In the container, without --gpus=all, it shows the card is unknown and the driver is "swrast" (so just CPU fallback).
To make --gpus=all work, it gives the error
I was doing a bad job searching before. I found that AMD can share the GPU, it just works a little differently in terms of how to launch the container. https://rocm.docs.amd.com/projects/install-on-linux/en/latest/install/amdgpu-install.html#amdgpu-install-dkms
But sadly my AMD GPU is too old/junk to have current driver support.
Anyways, appreciate the reply! Now I can mod my code to run on cheaper cloud instances.
(Note I'm an OpenGL/3D app developer, but probably OpenCL works about the same architecturally)