Nothing here yet.
Nothing here yet.
Nov 6, 2025 · 7 min read · DotCompute started as “make GPU compute sane for .NET”.A close second goal: use the hardware we already paid for instead of buying new toys every quarter. This post is about that second part. Why a GPU framework cares about carbon at all Green softw...
Join discussionNov 6, 2025 · 4 min read · Another framework? Yes.Another abstraction layer that hates your cache and your startup time? No. DotCompute’s first release candidate is ready. It gives you GPU and CPU acceleration from C# with: One kernel definition → multiple backends (CPU SIMD,...
Join discussionNov 4, 2025 · 6 min read · At some point you get tired of launching the same GPU kernel a few million times a day just to move a few bytes. RingKernels in DotCompute are the answer to that particular form of self-inflicted pain. Persistent kernels flip the model: launch once, ...
Join discussionSep 4, 2025 · 4 min read · Short version: we went from 8/70 passing CUDA tests to a stable, auditable path by fixing NVRTC name resolution, argument marshaling, and unified-memory sync in DotCompute. No mysticism—just careful pointers and fewer foot-guns. TL;DR NVRTC will ha...
Join discussionSep 3, 2025 · 4 min read · The good thing about agentic coding is, you can easily awake dead repos out of experiments back to life. Event sourced grain state machines is such an example. Short version: take a clean Stateless state machine, host it as a grain, and let events be...
Join discussion