- >I've learned a lot of shit while getting AI to give me the answers
I would argue you're learning less than you might believe. Similarly to how people don't learn math by watching others solve problems, you're not going to learn to become a better engineer/problem solver by reading the output of ChatGPT.
- "Luddite" is the new "DEI" for tech-bros.
- Yeah, not sure what the point here is. Could see someone who reads this and comes away thinking that a cancer screening isn't worth it.
- >I never once considered my “main source of income” my current job. My main source of income was my ability to get a job.
Your "ability to get a job" is not what put money into your bank account twice a month. Your employer did.
- A sufficiently large profit margin is what constitutes AGI? What a fucking joke.
- That's deeply sad.
- Sabine Hossenfelder these days is a YouTube personality, who likes to discuss subjects she's not an expert in. I don't know if that's the metric for "crank", but anything I hear from her is taken with a massive grain of salt.
- >Ofc you'd have to require a certain level of hardware support
Have you used Vulkan? Specifying required hardware support for your physical device is literally one of the first thing you do when setting up Vulkan.
- I'm fairly sure Vulkan runs just fine on Android? You won't have access to dynamic rendering, so you'll have to manage renderpasses, but I don't think you're going to have issues running Vulkan on a modern Android device.
- This is not a statement on the hardware, it's a statement on what the APIs are trying to achieve. In this regard, they are remarkably different.
- In part, because Vulkan is a graphics API, not a GPGPU framework like CUDA. They're entirely different beasts.
Vulkan is also trying to expose as many options as possible so as to be extensible on as many platforms as possible. Also, Vulkan isn't even trying to make it more complex than it need be--this is just how complex graphics programming is period. The only reasons people think Vulkan/DX12 are overly complicated is because they're used to using APIs where the majority of the heavy lifting comes from the drivers.
- I think CUDA and Vulkan are two completely different beasts, so I don't believe this is a good comparison. One is for GPGPU, and the other is a graphics API with compute shaders.
Also, CUDA is targeting a single vendor, whereas Vulkan is targeting as many platforms as possible.
- Metal has the benefit of being developed by Apple for Apple devices. I'd imagine that constraint allows them to simplify code paths in a way Vulkan can't/won't. Again, Metal doesn't have to deal with supporting dozens of different hardware systems like Vulkan does.
- Why should these things be simple? Graphics hardware varies greatly even across generations from the same vendors. Vulkan as an API is trying to offer the most functionality to as much of this hardware as possible. That means you have a lot of dials to tweak.
Trying to obfuscate all the options goes against what Vulkan was created for. Use OpenGL 4.6/WebGPU if you want simplicity.
- I don't doubt OpenGL will live forever. But Vulkan 1.3/1.4 is not as bad as people make it out to be.
- I think Vulkan was originally called OpenGL Next. Furthermore, Vulkan's verbosity allows for a level of control of the graphics pipeline you simply can't have with OpenGL, on top of having built in support for things like dynamic rendering, bindless descriptors, push constants, etc.
Those are the main reasons IMO why most people say it's deprecated.
- CUDA toolkit comes with an occupancy calculator that can help you determine based on your kernel launch parameters how busy your GPU will potentially be.
For more information: https://docs.nvidia.com/cuda/cuda-c-programming-guide/#multi...
- Why would this be a bad thing? You're acting like technology isn't already widely regulated.
I have all of that but DX12 knowledge, and 50% of this article still went over my head.