PetorSFZ

We ran a randomized controlled trial to see how much AI coding tools speed up experienced open-source developers.

The results surprised us: Developers thought they were 20% faster with AI tools, but they were actually 19% slower when they had access to AI than when they didn't.

2008: "You can't trust everything that's on wikipedia"

2025: "Wikipedia is the last bastion of pure truth online."

here's how to have your own personal copy of wikipedia while it still persists.

I think the "safe" version of your original example would be:

Vec myVec;
int index = 2;
float v;
memcpy(&v, ((const char*)&myVec) + index * sizeof(float), sizeof(float))
return v;

But like, no on wants to write code like that...

I think it's probably fixed if you add "-fno-strict-aliasing".

Personally, I think it's too dangerous to build C++ with strict aliasing on. Too much code that potentially breaks. The workarounds to make said code defined behavior is usually quite obnoxious.

Other notable things include a custom voxel editor, controlled entirely by gamepad. I wrote it mainly because I got annoyed with limitations of MagickaVoxel and having to use keyboard+mouse all the time.

GitHub - PetorSFZ/sfz_tech: skipifzero technologies, core libraries, game engines, graphics apis, etc skipifzero technologies, core libraries, game engines, graphics apis, etc - PetorSFZ/sfz_tech

The voxel project is written mostly from scratch. C++, D3D12. All rendering is done through raytracing in compute shaders, the only rasterization is the UI.

I'm using a custom immediate mode UI lib and gpu library which I have written myself:
github.com/PetorSFZ/sfz...

Hi everyone!

I'm a professional AAA game developer at day, and working on a voxel game project at night as a hobby.

Some (old) screenshots from my voxel project