Amin Mesbah mesbahamin

Because cross-compiling binaries for Windows is easier than building natively

I want Microsoft to do better, want Windows to be a decent development platform-and yet, I constantly see Microsoft playing the open source game: advertising how open-source and developer friendly they are - only to crush developers under the heel of the corporate behemoth's boot.

The people who work at Microsoft are amazing, kind, talented individuals. This is aimed at the company's leadership, who I feel has on many occassions crushed myself and other developers under. It's a plea for help.

The source of truth for the 'open source' C#, C++, Rust, and other Windows SDKs is proprietary

You probably haven't heard of it before, but if you've ever used win32 API bindings in C#, C++, Rust, or other languages, odds are they were generated from a repository called microsoft/win32metadata.

There is a nice GIF illustrating a technique called "frustum culling" in this Kotaku article: http://kotaku.com/horizon-zero-dawn-uses-all-sorts-of-clever-tricks-to-lo-1794385026

The interwebs being what they are, this has also led to some controversy.

Some people have interpreted the opening sentence "Every time you move the camera in Horizon Zero Dawn, the game is doing all sorts of under-the-hood calculations, loading and unloading chunks of world to ensure that it all runs properly," as being about the GIF; that's not what frustum culling does, but that's probably not what the article's author meant anyway.

	#include <stdio.h>
	#include <stdlib.h>
	#include <stdint.h>
	#include <assert.h>
	#include <string.h>
	#include <stdarg.h>
	#include <limits.h>

	#define cast(t,p) ((t)(p))
	#define szof(a) ((int)sizeof(a))

	$ clang --version
	clang version 5.0.1 (tags/RELEASE_501/final)
	Target: x86_64-unknown-windows-cygnus
	Thread model: posix
	InstalledDir: /usr/bin

	$ clang --help-hidden
	OVERVIEW: clang LLVM compiler

	USAGE: clang-5.0 [options] <inputs>

	struct path_iter {
	const char *begin;
	const char *end;
	/* internal */
	const char *next;
	const char *eof;
	};
	static void
	path_begin(struct path_iter it, const char str, const char *end)
	{

	#define _USE_MATH_DEFINES
	#include <math.h>

	struct Point
	{
	double x, y;
	};

	// A class that contains a 2D angle as a pair of sine + cosine values.
	// Sometimes, this approach saves substantial CPU time that would be wasted running these trigonometry functions.

	#!/bin/bash
	#
	# 4633c8a2a16a8e0428d253baafb76bbc18f29562390c84d1c85ba98865531a2b

	CRYPTER="base64 -b 78"
	HEADER="----BEGIN PGP MESSAGE----"
	FOOTER="-----END PGP MESSAGE-----"

	do_encryption() {
	local plain="$1"



	# OBJECTIVE: Install Arch Linux with encrypted root and swap filesystems and boot from UEFI.

	# Note this encrypted installation method, while perfectly correct and highly secure, CANNOT support encrypted /boot and
	# also CANNOT be subsequently converted to support an encrypted /boot!!! A CLEAN INSTALL will be required!

	# Therefore, if you want to have an encrypted /boot or will want an encrypted /boot system at some point in the future,
	# please ONLY follow my encrypted /boot installation guide, which lives here:

	LIBRARY WRITING REFERENCE LIST
	===============================
	1.) Designing and Evaluating Reusable Components (Casey Muratori: http://mollyrocket.com/casey/stream_0028.html)
	----------------------------------------------------------------------------------------------------------------
	_THE_ reference on API design up to this day on the internet. Nobody should write a library without having seen this.
	I come back to this talk every N number of weeks it is that good.

	2.) stb_howto (Sean Barrett: https://github.com/nothings/stb/blob/master/docs/stb_howto.txt)
	--------------------------------------------------------------------------------------------
	Sean Barretts single header libraries (https://github.com/nothings/stb) was the first time for me that I came across

	/*
	I'm dropping this from the game in favour of a more dynamic system, but I wanted to keep this around somewhere because
	I'll be using this 'pattern' for something similar again and didn't want to fuss with sytax. Maybe you'll find it useful
	*/
	#define ANIM_LIST \
	/* EnumName, var_name, max */ \
	ALF(Invalid, invalid, 1) \
	ALF(Idle, idle, 4) \
	ALF(Spawn, spawn, 4) \
	ALF(Taunt, taunt, 2) \