4 ms·

This is very welcome and a long time coming! If you're eager to learn WebGPU, consider checking out Mach[0] which lets you develop with it natively using Zig t

This is very welcome and a long time coming! If you're eager to learn WebGPU, consider checking out Mach[0] which lets you develop with it natively using Zig today very easily. We aim to be a competitor-in-spirit to Unity/Unreal/Godot, but extremely modular. As part of that we have Mach core which just provides Window+Input+WebGPU and some ~19 standalone WebGPU examples[1]. Currently we only support native desktop platforms; but we're working towards browser support. WebGPU is very nice because it lets us target desktop+wasm+mobile for truly-cross-platform games & native applications. [0] https://github.com/hexops/mach https://github.com/hexops/mach [1] https://github.com/hexops/mach-examples/tree/main/core https://github.com/hexops/mach-examples/tree/main/core

bobajeff 4y ago
I'm actually keeping a close eye on mach after seeing your talk about gkurve. That has made GPU accelerated 2D graphics look much more approachable to me. I plan to experiment with that after I get a better understanding of the WebGPU c API.
ArtWomb 4y ago
Zig is the "language I'm learning next" ;)
johnfn 4y ago
The Mach project led me to this, uhm, _interesting_ article: https://devlog.hexops.com/2021/i-write-code-100-hours-a-week/ https://devlog.hexops.com/2021/i-write-code-100-hours-a-week... What a maniac!
- lightbendover 4y ago
  2 years isn’t long enough to really experience burnout. As soon as rewards slow down, it will seep in if nothing else changes.
  - slimsag 4y ago
    Closer to 3.5 years now, maybe I'll do an update at 4 years. The 2.5 year initial duration (when I posted that article) was like working two full-time jobs, 100h/week, 80% writing code. Past year has been more like 85h/week, my dayjob has required more time (48h -> ~60h), now with only 30% of that being /writing code/. ~25h/week going to my gamedev passion projects, of which a good chunk has also gone to helping others with their code/issues. The -15h/week 'loss' has gone to caring for pets, and a gentle touch more travel/sleep/gardening.
    - johnfn 4y ago
      Hey, it's the man himself! I'd love to read a followup post if you have the time (hehe) to write it. I'd also be curious to read about how you spend your non-working hours in more detail!
- mlsu 4y ago
  I appreciate the candor of this article. And I'm not making any judgements. But that calendar. That calendar is wild.

bobajeff 4y ago

I'm actually keeping a close eye on mach after seeing your talk about gkurve. That has made GPU accelerated 2D graphics look much more approachable to me. I plan to experiment with that after I get a better understanding of the WebGPU c API.

ArtWomb 4y ago

Zig is the "language I'm learning next" ;)

johnfn 4y ago

The Mach project led me to this, uhm, _interesting_ article: https://devlog.hexops.com/2021/i-write-code-100-hours-a-week/ https://devlog.hexops.com/2021/i-write-code-100-hours-a-week... What a maniac!

lightbendover 4y ago
2 years isn’t long enough to really experience burnout. As soon as rewards slow down, it will seep in if nothing else changes.
- slimsag 4y ago
  Closer to 3.5 years now, maybe I'll do an update at 4 years. The 2.5 year initial duration (when I posted that article) was like working two full-time jobs, 100h/week, 80% writing code. Past year has been more like 85h/week, my dayjob has required more time (48h -> ~60h), now with only 30% of that being /writing code/. ~25h/week going to my gamedev passion projects, of which a good chunk has also gone to helping others with their code/issues. The -15h/week 'loss' has gone to caring for pets, and a gentle touch more travel/sleep/gardening.
  - johnfn 4y ago
    Hey, it's the man himself! I'd love to read a followup post if you have the time (hehe) to write it. I'd also be curious to read about how you spend your non-working hours in more detail!
mlsu 4y ago
I appreciate the candor of this article. And I'm not making any judgements. But that calendar. That calendar is wild.