Robert uerobert

1. What does the Rendering Engine Need?

Rendering Engine
- Support for Multiple Graphics APIs : OpenGL | Vulkan | DirectX12 | DirectX11 | Metal
- Content Export Pipeline : Create Maya/Max Plugins to export meshes based on Renderers needs. (Assimp Commercial Licence -> Pay)
- Texture Compression Libraries
- Material System : Artists Configure shaders, textures, parameters to import in game
- Game-side Manager of Models/Materials/Lights
- Good Visibility System (Frustum/Occlusion) (VisibilityBuffers?)
- Multi-Threded Submission System to reduce cost of submission to GPU
Lighting/Shadow Rendering System

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

	# set prefix to control-f
	set -g prefix C-f

	#unbind system defined prefix
	unbind C-b

	# helps in faster key repetition
	set -sg escape-time 0

	# start session number from 1 rather than 0