harryhare harryhare

CUSTOM GAME ENGINES: A Small Study

A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.

Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) because d

What is the difference between Cerebral and Redux?

Cerebral and Redux were built to solve different problems

Redux was developed to achieve hot reloading global state and state changing logic. To achieve that it was necessary for state changes to be run with pure functions and the state has to be immutable. Now you can change the logic inside your reducer and when the application reloads Redux will put it in its initial state and rerun all the actions again, now running with the new state changing logic.

Cerebral had no intention of achieving hot reloading. Cerebral was initially developed to give you insight into how your application changes its state, using a debugger. In the Redux debugger you see what actions are triggered and how your state looks after the action was handled. In Cerebral you see all actions fired as part of a signal. You see asynchronous behaviour, paths taken based on decisions made in your state changing flow. You see all inputs and outputs produced during the flow and you even

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<title></title>
	</head>
	<body>
	<video></video>
	<br/>
	<input type="file" name="file" id="fileItem" onchange="onChange()" >

	# gcc -Wall -o match match.c && ./match
	#


	#include <stdio.h>
	#include <string.h>
	#include <regex.h>

	# Author: Pieter Noordhuis
	# Description: Simple demo to showcase Redis PubSub with EventMachine
	#
	# Update 7 Oct 2010:
	# - This example does not appear to work with Chrome >=6.0. Apparently,
	# the WebSocket protocol implementation in the cramp gem does not work
	# well with Chrome's (newer) WebSocket implementation.
	#
	# Requirements:
	# - rubygems: eventmachine, thin, cramp, sinatra, yajl-ruby