The introduction to Reactive Programming you've been missing
This tutorial as a series of videos
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
|// These window.navigator contain language information|
|// 1. languages -> Array of preferred languages (eg ["en-US", "zh-CN", "ja-JP"]) Firefox^32, Chrome^32|
|// 2. language -> Preferred language as String (eg "en-US") Firefox^5, IE^11, Safari,|
|// Chrome sends Browser UI language|
|// 3. browserLanguage -> UI Language of IE|
|// 4. userLanguage -> Language of Windows Regional Options|
|// 5. systemLanguage -> UI Language of Windows|
|var browserLanguagePropertyKeys = ['languages', 'language', 'browserLanguage', 'userLanguage', 'systemLanguage'];|
Proposal for a lightning talk at the Reactive 2016.
Keep calm and like/retweet it on Twitter and star this Gist to vote on this talk.
Road from UndefinedLand
I work at Grammarly. We like React and happily use it in our applications. However, sometimes something goes wrong and bugs creep into the code. Here comes testing. It helps make us confident about the quality of our code.
Deploy your site with git
This gist assumes:
- you have a local git repo
- with an online remote repository (github / bitbucket etc)
- and a cloud server (Rackspace cloud / Amazon EC2 etc)
- your (PHP) scripts are served from /var/www/html/
- your webpages are executed by apache
- apache's home directory is /var/www/