| diff --git a/node_modules/react-native/React/Views/RCTScrollView.m b/node_modules/react-native/React/Views/RCTScrollView.m | |
| --- a/node_modules/react-native/React/Views/RCTScrollView.m | |
| +++ b/node_modules/react-native/React/Views/RCTScrollView.m | |
| @@ -136,7 +136,7 @@ | |
| * default UIKit behaviors such as textFields automatically scrolling | |
| * scroll views that contain them and support sticky headers. | |
| */ | |
| -@interface RCTCustomScrollView : UIScrollView<UIGestureRecognizerDelegate> | |
| +@interface RCTCustomScrollView : UIScrollView<UIGestureRecognizerDelegate, RCTClippingView> | |
This is a basic guide on how to learn Elm rather than actually teach you. I'm going to mostly link to resources that I feel are valuable and try to "teach you how to fish".
The main purpose is to accelerate your learning and save you a lot of googling and weeding through bad explinations.
| /** | |
| * @providesModule ReactConsole | |
| */ | |
| 'use strict'; | |
| const colors = require('colors'); | |
| const ReactDOMFrameScheduling = require('ReactDOMFrameScheduling'); | |
| const ReactFiberReconciler = require('ReactFiberReconciler'); |
Author: Chris Lattner
tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.
A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.
But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.
How do we solve this with React?
How do you send information between clients and servers? What format should that information be in? What happens when the server changes the format, but the client has not been updated yet? What happens when the server changes the format, but the database cannot be updated?
These are difficult questions. It is not just about picking a format, but rather picking a format that can evolve as your application evolves.
By now there are many approaches to communicating between client and server. These approaches tend to be known within specific companies and language communities, but the techniques do not cross borders. I will outline JSON, ProtoBuf, and GraphQL here so we can learn from them all.
I wrote this answer on stackexchange, here: https://stackoverflow.com/posts/12597919/
It was wrongly deleted for containing "proprietary information" years later. I think that's bullshit so I am posting it here. Come at me.
Amazon is a SOA system with 100s of services (or so says Amazon Chief Technology Officer Werner Vogels). How do they handle build and release?
| let cache = new Map(); | |
| let pending = new Map(); | |
| function fetchTextSync(url) { | |
| if (cache.has(url)) { | |
| return cache.get(url); | |
| } | |
| if (pending.has(url)) { | |
| throw pending.get(url); | |
| } |
| # Remove previous installations | |
| sudo apt-get remove vim vim-runtime vim-tiny vim-common | |
| # Install dependencies | |
| sudo apt-get install libncurses5-dev python-dev liblua5.3-dev lua5.3 python3-dev | |
| # Fix liblua paths | |
| # You have to compile luajit for yourself. | |
| sudo ln -s /usr/include/lua5.3 /usr/include/lua | |
| sudo ln -s /usr/lib/x86_64-linux-gnu/liblua5.3.so /usr/local/lib/liblua.so |
