If read, why not write?

Some time ago I wrote a script to create an arbitrary self signed certificate. Then I made a DevOps pipeline task out of it. Now, I'm wondering about the same logic, running interactively.

I am globally unique, baby

UUIDs are supported everywhere these days. But what about binary compatibility?

Turducken or duckturken?

 A static library (a .a file) is a collection of object files. On MacOS, executable binary files can contain code for multiple CPUs - that is, an executable can be internally a collection of slices, each of them also an executable. 

Joomla 2 on PHP 7

 An archival instance of Joomla 2 broke on PHP 7.

Normally it's the other way around

 More from the department of bogus C++ behavior.

Sony is crazy

 Amazing discovery of the day: on PlayStation 3, a single binary file can contain a mix of 32-bit code (i. e. code using 32-bit addresses) and 64-bit code.

The binaries are nothing special on the surface, ELF targeting PowerPC-64, but here I am, looking at a DWARF CU where address_size is 4.

Is nothing a special case of something?

Is void a datatype? Trick question.