Fixing typographical errors

This commit is contained in:
Kunle Ekunkonye 2017-06-07 10:10:08 -04:00 committed by GitHub
parent e0f9f6eeea
commit c556bb9ab5
1 changed files with 5 additions and 5 deletions

View File

@ -6,9 +6,9 @@ Status is largely written in two languages: Clojurescript & Golang and builds on
## React Native
Status (formerly known as Syng) has always aspired to have a single, unified codebase for multi-platform development. This is not so easy to achieve, as many of the non-web-based solutions out there allow you to have a semi-single codebase, but you find yourself creating a lot of seperate logic for handling user interfaces on each platform - Status is 80% frontend code and this presents a problem. We tried Xamarin & Java (EthereumJ was the first implementation we got running on Android & iOS - via RoboVM), and we quickly discovered this problem.
Status (formerly known as Syng) has always aspired to have a single, unified codebase for multi-platform development. This is not so easy to achieve, as many of the non-web-based solutions out there allow you to have a semi-single codebase, but you find yourself creating a lot of separate logic for handling user interfaces on each platform - Status is 80% frontend code and this presents a problem. We tried Xamarin & Java (EthereumJ was the first implementation we got running on Android & iOS - via RoboVM), and we quickly discovered this problem.
Mobile apps built on web-based technologies, such as those done in Cordova, are great for short-term projects or mvp, but you will quickly run into performance issues on resource-limited devices and may need to rewrite you app. In our tests displaying webview DApps in a chat history with iFrames and all the other bells and whistles we wanted turned out to be a futile effort.
Mobile apps built on web-based technologies, such as those done in Cordova, are great for short-term projects or MVP, but you will quickly run into performance issues on resource-limited devices and may need to rewrite you app. In our tests displaying webview DApps in a chat history with iFrames and all the other bells and whistles we wanted turned out to be a futile effort.
That limited our options to choosing between NativeScript & React Native. We chose React Native because it is more mature and is being used in production for popular apps like **Facebook**, **Instagram**, **Airbnb**, **Baidu** & **Discord**. This gave us the impression that this framework was here to stay with many Fortune 500 companies invested in its continuance.
@ -31,7 +31,7 @@ To read more quotes on Lisp read [Lisp, made with secret alien technology](http:
[![We lost the documentation on quantum mechanics. You'll have to decode the regexes yourself.](img/xkcd-224.jpg)](https://xkcd.com/224/ "We lost the documentation on quantum mechanics. You'll have to decode the regexes yourself.")
There's alot of resources online about why learning Lisps are so great. For us, it's largely about culture; we like the way Lispers think. We want functional programming, macros, homoiconic code and the flexibility that comes with a simple, unstructured language in which to think. The benefits of this become more apparent in later stage development, where functional language allows us to perform rewrites more easily, isolate many bugs to specific functions, as well as enforcing correct coding. Also, I prefer reading it.
There's a lot of resources online about why learning Lisps are so great. For us, it's largely about culture; we like the way Lispers think. We want functional programming, macros, homoiconic code and the flexibility that comes with a simple, unstructured language in which to think. The benefits of this become more apparent in later stage development, where functional language allows us to perform rewrites more easily, isolate many bugs to specific functions, as well as enforcing correct coding. Also, I prefer reading it.
Moreover, with [hiccup](https://github.com/weavejester/hiccup), working with React Native markup becomes a dream.
@ -67,7 +67,7 @@ re-frame is simple but expressive library for writing Single Page Applications i
## Reagent
[Reagent](http://reagent-project.github.io/) provides a minimalistic interface between ClojureScript and React. It allows you to define efficient React components using nothing but plain ClojureScript functions and data, that describe your UI using a Hiccup-like syntax.
[Reagent](http://reagent-project.github.io/) provides a minimalistic interface between ClojureScript and React. It allows you to define efficient React components using nothing but plain ClojureScript functions and data that describe your UI using a Hiccup-like syntax.
The goal of Reagent is to make it possible to define arbitrarily complex UIs using just a couple of basic concepts, and to be fast enough by default that you rarely have to care about performance.
- [Reagent website](http://reagent-project.github.io/)
@ -92,7 +92,7 @@ The best place to look for tasks to work on is our [Github Issues](https://githu
## Beginner Issues
<a href="https://github.com/status-im/status-react/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner" target="_blank"><img src="../img/beginner.png" style="height:28px;margin:0"/ ></a>
These are tickets we believe anyone willing to learn Clojurescript can handle. They involve minor UI and localisation changes. Even though they may seem minor that have a huge impact on the usability of Status.
These are tickets we believe anyone willing to learn Clojurescript can handle. They involve minor UI and localization changes. Even though they may seem minor that have a huge impact on the usability of Status.
## Intermediate Issues
<a href="https://github.com/status-im/status-react/issues?q=is%3Aopen+is%3Aissue+label%3Aintermediate" target="_blank"><img src="../img/intermediate.png" style="height:28px;margin:0"/ ></a>