For me personally, blender uses ROCm and ROCm hiprt for Cycles tracing and cycles raytracing acceleration. I am using a Radeon RX 6800 and AMD Ryzen AI 7 350, and it works on Linux. ROCm HIPRT really does speed up cycles rendering (at the cost of more Vram usage). Of course, using the AMD driver on Linux, you get access to the system's RAM with GTT.
My introduction to NFS was first at Berkeley, and then at Sun. It more or less just worked. (Some of the early file servers at Berkeley were drastically overcapacity with all the diskless Sun-3/50s connected, but still.)
And of course I still use it every day with Amazon EFS; Happy Birthday, indeed!
I'm going to push back hard on the folks dunking on "vibe coders" -- I have been programming longer than most of you have been alive, and there are times when I absolutely do vibe coding:
1) unfamiliar framework
2) just need to build a throwaway utility to help with a main task (and I don't want to split my attention)
3) for fun: I think of it as "code sculpting" rather than writing
So this is absolutely a utility I would use. (Kudos to the OP.)
Remember the second-best advice for internet interactions (after Wheaton's Law): "Ssssshh. Let people enjoy things."
I too have probably been programming longer than most people here, and I'll vibe code on occasion for your #2 reason. (Recently I needed to take an OpenAPI spec file and transform/reduce it in some mechanical ways; didn't feel like writing the code for it, didn't care if it was maintainable, and it was easily verifiably correct after a quick manual skim of its output.)
I don't think #1 is a good place to vibe code; if it's code that I'll have to maintain, I want to understand it. In that case I'll sometimes use an LLM to write code incrementally in the new framework, but I'll be reading every line of it and using the LLM's work to help me understand and learn how it works.
A utility like pyscn that determines code quality wouldn't be useful for me with #1: even in an unfamiliar framework, I'm perfectly capable judging code quality on my own, and I still need and want to examine the generated code anyway.
(I'm assuming we're using what I think is the most reasonable definition of "vibe coding": having an LLM do the work, and -- critically -- not inspecting or reviewing the LLM's output.)
we can have a pissing contest. I don't begrudge anyone their fun, but when my job becomes taking hundreds of thousands of lines of vibe code and just finding that one little change that will make it all work, we have a serious problem with expectations.
I don't think we're at odds: I think "vibe coding" is strictly for fun and for prototypes. However, people will misuse any tool, so having utilities to mitigate the risk isn't a bad thing.
Okay but we also know how it started, which was not as a bilateral trade agreement. I don't think imperial japan has eternally tarnished the concept of 'prosperity' in the same way that hitler forever tarnished that style of mustache.
My dad had his bladder removed. Cancer came back 18 months later and he was gone 4 months after that. It sucks.
Plus, I regret that he had to live with a colostomy bag for that time. His quality of life probably higher if they do the other option (name escapes me).
