| /** | |
| * example C code using libcurl and json-c | |
| * to post and return a payload using | |
| * http://jsonplaceholder.typicode.com | |
| * | |
| * License: | |
| * | |
| * This code is licensed under MIT license | |
| * https://opensource.org/licenses/MIT | |
| * |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
I have two Github accounts: oanhnn (personal) and superman (for work). I want to use both accounts on same computer (without typing password everytime, when doing git push or pull).
Use ssh keys and define host aliases in ssh config file (each alias for an account).
| package main | |
| import ( | |
| "golang.org/x/net/websocket" | |
| "log" | |
| "net/rpc/jsonrpc" | |
| ) | |
| // In a real project, these would be defined in a common file | |
| type Args struct { |
| function createStore (reducers) { | |
| var state = reducers() | |
| const store = { | |
| dispatch: (action) => { | |
| state = reducers(state, action) | |
| }, | |
| getState: () => { | |
| return state | |
| } | |
| } |
This is the CFP for my React Rally talk, which was eventually accepted and given here: https://www.youtube.com/watch?v=nyFHR0dDZo0.
If you are a first time speaker, my CFP advice for new speakers is here.
Functional-reactive libraries like RxJS make it easy to understand how data changes, giving us tools to declaratively handle events and manage state. But while our render methods react to state changes, React isn’t reactive. Instead, we write imperative event-handlers, and trip up on gotchas like async setState and race conditions. Why? In this talk we build a Reactive React to show the difference between the "push" and "pull" paradigms of data flow and understand why React chooses to manage Scheduling as a core Design Principle, enabling awesome features like async rendering and Suspense!
Theme: This talk is a deep dive into React's core design principle around scheduling. Instead of abstr
MonoGame already supports installing templates from the official installer
This works for all IDEs that support .net core (which is pretty much anything up to date nowadays). Use this if you can't get any other methods to work.
Install the latest .net core sdk. Run the following command:
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
| shader_type canvas_item; | |
| uniform sampler2D spritesheet; // Should be a slice image as exported from Magica Voxel | |
| uniform int slice_count = 1; // The number of slices | |
| uniform vec2 camera_vec = vec2( 1., 1. ); // Recomend using (1,1) or (1,1.5) | |
| uniform float camera_ang = 0.0; // change this to change the view angle of the object | |
| const vec2 center = vec2( 0.5 ); | |
| bool scale_and_rotate_with_offset( inout vec2 uv, vec2 sxy, float ang, vec2 cent, vec2 offset ) |
