Previously I had begun a series of blog posts detailing how to port applications from OpenCL -> Vulkan. OpenCL -> Vulkan: A Porting Guide (#1) OpenCL -> Vulkan: A Porting Guide (#2) OpenCL -> Vulkan: A Porting Guide (#3) Instead of continuing this blog series, I’m converting the entire contents into a slide deck, and will be presenting it at the Munich Khronos Chapter meeting on the 13th of October 2017.

Vulkan is the newest kid on the block when it comes to cross-platform, widely supported, GPGPU compute. Vulkan’s primacy as the high performance rendering API powering the latest versions of Android, coupled with Windows and Linux desktop drivers from all major vendors means that we have a good way to run compute workloads on a wide range of devices. OpenCL is the venerable old boy of GPGPU these days - having been around since 2009.

Vulkan is the newest kid on the block when it comes to cross-platform, widely supported, GPGPU compute. Vulkan’s primacy as the high performance rendering API powering the latest versions of Android, coupled with Windows and Linux desktop drivers from all major vendors means that we have a good way to run compute workloads on a wide range of devices. OpenCL is the venerable old boy of GPGPU these days - having been around since 2009.

Vulkan is the newest kid on the block when it comes to cross-platform, widely supported, GPGPU compute. Vulkan’s primacy as the high performance rendering API powering the latest versions of Android, coupled with Windows and Linux desktop drivers from all major vendors means that we have a good way to run compute workloads on a wide range of devices. OpenCL is the venerable old boy of GPGPU these days - having been around since 2009.

I’ve added JSON 5 support to my json.h library. For those not in the know, JSON 5 (http://json5.org/) is a modern update to the JSON standard, including some cool features like unquoted keys, single quoted keys and strings, hexdecimal numbers, Infinity and NaN numbers, and c style comments! As is sticking with the design of my lib - each of the features can be turned on individually if you don’t want the full shebang, or just add json_parse_flags_allow_json5** **to enable the entire feature set.