Hey HN!
This is my first post and i wanted to share my backstory for this project.
enki is a project that I developed to fix one problem (GPU programming hell)
when i first started programming with OpenGL (and later Vulkan) i was really shocked by the amount of pain and Boilerplate code required just to run a single triangle or a basic matmul, and that because i was coming from CPU language (C# and later rust), i assumed the experience would be the same, but it was really frustrating to see the actual reality (and i don't need to talk about it).
so i tried to forget about it and just accept it.
after more than a year, I was building my game engine using vulkan, During that time i created an internal library called "utu" to help me abstract vulkan Boilerplate code, during that time an idea has clicked "why don't i try to fix the main problem my self?", utu was the main driver for this idea, so i threw away all the code and decided to focus on a single goal and it's to make my first expectation of the GPU world come true "Writing cpu code and run it on the GPU", now after a lott of pain building this project i finally did it, using rust bitcode (.bc llvm ir) that has the same logic of the user kernel (the nam function), then compile it to spir-v (and that was the most painful thing to do, i called the compiler "parsu"). now we can use crates.io & iters & enums & generics directly inside the kernel and it will run on the GPU! want to run it on the CPU? because it's a native rust syntax and version (stable rust) it would run on the CPU natrully without touching the code.
Hey HN! This is my first post and i wanted to share my backstory for this project.
enki is a project that I developed to fix one problem (GPU programming hell)
when i first started programming with OpenGL (and later Vulkan) i was really shocked by the amount of pain and Boilerplate code required just to run a single triangle or a basic matmul, and that because i was coming from CPU language (C# and later rust), i assumed the experience would be the same, but it was really frustrating to see the actual reality (and i don't need to talk about it).
so i tried to forget about it and just accept it. after more than a year, I was building my game engine using vulkan, During that time i created an internal library called "utu" to help me abstract vulkan Boilerplate code, during that time an idea has clicked "why don't i try to fix the main problem my self?", utu was the main driver for this idea, so i threw away all the code and decided to focus on a single goal and it's to make my first expectation of the GPU world come true "Writing cpu code and run it on the GPU", now after a lott of pain building this project i finally did it, using rust bitcode (.bc llvm ir) that has the same logic of the user kernel (the nam function), then compile it to spir-v (and that was the most painful thing to do, i called the compiler "parsu"). now we can use crates.io & iters & enums & generics directly inside the kernel and it will run on the GPU! want to run it on the CPU? because it's a native rust syntax and version (stable rust) it would run on the CPU natrully without touching the code.