All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.
A number of methods in React are assumed to be "pure".
On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.
IMPORTANT! Remember to check out the wiki page at https://github.com/bebraw/jswiki/wiki/Game-Engines for the most up to date version. There's also a "notes" column in the table but it simply does not fit there... Check out the raw version to see it.
This table contains primarily HTML5 based game engines and frameworks. You might also want to check out the [[Feature Matrix|Game-Engine-Feature-Matrix]], [[Game Resources]] and [[Scene Graphs]].
| Name | Size (KB) | License | Type | Unit Tests | Docs | Repository | Notes |
|---|---|---|---|---|---|---|---|
| Akihabara | 453 | GPL2, MIT | Classic Repro | no | API | github | Intended for making classic arcade-style games in JS+HTML5 |
| AllBinary Platform | Platform Dependent | AllBinary | 2D/2.5D/3D | n |
| // TODO: make `pages` optional and measure the div when unspecified, this will | |
| // allow more normal document flow and make it easier to do both mobile and | |
| // desktop. | |
| import { | |
| createContext, | |
| useCallback, | |
| useContext, | |
| useEffect, | |
| useMemo, | |
| useRef, |
useSubscription and useMutableSource1 tearing and deopt behavior.
The tree below represents a React application mounting. During mount, two components read from an external, mutable source. The first one (List) reads version 1 of that data and the second one (Item) reads version 2.
N/A.
| /* | |
| * The reason for this is just a thought exercise | |
| * often people(myself super included) are so confused | |
| * when trying something new, but breaking it down | |
| * to it's simplest existence can be the best way to understand | |
| */ | |
| function createStore(reducer, initState) { | |
| let state = initState; | |
| let subscribers = []; |
This is a CFP for ReactiveConf 2017's open call for Lightning talks. If you'd like to see this talk become a reality, please ⭐ star this gist. #ReactiveConf
Please 🌟 this gist to vote for this proposal!
No other topic in software development probably has so much controversy as linting.
With a wrong workflow linting can be really a pain and will slow you and your team down. With a proper setup, though, it can save you hours of manual work reformatting the code and reducing the code-review overhead.
| <html> | |
| <head> | |
| <script> | |
| function debug(string) { | |
| var element = document.getElementById("debug"); | |
| var p = document.createElement("p"); | |
| p.appendChild(document.createTextNode(string)); | |
| element.appendChild(p); | |
| } |
| /** | |
| * Module dependencies. | |
| */ | |
| var express = require('express'), | |
| http = require('http'), | |
| RedisStore = require('connect-redis')(express), | |
| redis = require('redis'), | |
| cookie = require('cookie'), | |
| connect = require('connect'), |
| // requestAnimationFrame implementation as a custom function to allow blacklisting | |
| // devices with broken implementation. Currently needs timer-based fallbacks for iOS 6.x for | |
| // code running inside <iframe> elements. | |
| // Uses polyfills based on http://paulirish.com/2011/requestanimationframe-for-smart-animating/ | |
| (function() { | |
| var blacklisted = /iP(ad|hone|od).*OS 6/.test(window.navigator.userAgent), | |
| lastTime = 0, | |
| nativeRequest = window.requestAnimationFrame || null, | |
| nativeCancel = window.cancelAnimationFrame || null; |
