remzmike

Hello C

A minimal guided introduction to getting started in programming using C.

This guide is for beginners who want to know practical fundamentals.

It is written for Windows users using Microsoft compiler tools.

This is intended to answer a question Casey Muratori had on twitter about why would anyone choose Unity over Unreal. The short answer is, I have no clue. Well, I kinda do know why you WOULDN'T choose it, so maybe I'll tackle it that way, pros/cons. Read on.

There's a few pros I could think for Unity:

Their text-based asset serialization which makes collobration work and resolving conflicts much easier. Unreal's assets are all binary and it's really built well for Perforce, if you're more than a handful of people working together not using Perforce (e.g. git) you'll have a less of an idea time.
Their undo/redo system I found is a lot more graceful/lightweight than Unreal's. Undoing in Unreal sometimes doesn't work reliably or go back a dozen entries in history, and just reverts back your selection state and is a bit intrusive (not sure if that was imporved in UE5)
Their animation editor (for me as a non-animator) I found was friendlier and easier to work with
The profiler is nice and very easy to us

Minimal D3D11

Minimal D3D11 reference implementation: An uncluttered Direct3D 11 setup + basic rendering primer and API familiarizer. Complete, runnable Windows application contained in a single function and laid out in a linear, step-by-step fashion that should be easy to follow from the code alone. ~200 LOC. No modern C++, OOP or (other) obscuring cruft. View on YouTube

Other gists in this series:

Minimal D3D11 part 2

Orthodox C++

What is Orthodox C++?

Orthodox C++ (sometimes referred as C+) is minimal subset of C++ that improves C, but avoids all unnecessary things from so called Modern C++. It's exactly opposite of what Modern C++ suppose to be.

Why not Modern C++?

What if... ?

Presentation by Michal Taszycki delivered at the Wroc_love.rb conference on 2015-03-13.

Below you can find various links I've mentioned during the talk.

The Video & Slides

Original Post

Evaluating Team Members

If people want to move, and the leads of those projects deem them qualified, there’s no reason not to allow this.

Deeming someone qualified is a pretty nuanced and difficult process. I wouldn’t expect all or even most temporary tech leads to get it right (or even be close) for a long time.

	/**
	* Fancy ID generator that creates 20-character string identifiers with the following properties:
	*
	* 1. They're based on timestamp so that they sort after any existing ids.
	* 2. They contain 72-bits of random data after the timestamp so that IDs won't collide with other clients' IDs.
	* 3. They sort lexicographically (so the timestamp is converted to characters that will sort properly).
	* 4. They're monotonically increasing. Even if you generate more than one in the same timestamp, the
	* latter ones will sort after the former ones. We do this by using the previous random bits
	* but "incrementing" them by 1 (only in the case of a timestamp collision).
	*/

	Per https://code.google.com/p/v8/codesearch#v8/trunk/src/runtime.cc


	%CreateSymbol
	%CreatePrivateSymbol
	%CreateGlobalPrivateSymbol
	%NewSymbolWrapper
	%SymbolDescription
	%SymbolRegistry
	%SymbolIsPrivate


	var E_PREFIX_RATE = 0.25;

	// All of our word lists:
	var _word_lists = {

	verb : [
	"implement", "utilize", "integrate", "streamline", "optimize", "evolve", "transform", "embrace",
	"enable", "orchestrate", "leverage", "reinvent", "aggregate", "architect", "enhance", "incentivize",
	"morph", "empower", "envisioneer", "monetize", "harness", "facilitate", "seize", "disintermediate",