marcianosr

Keybase proof

I hereby claim:

• I am marcianosr on github.
• I am marcianosr (https://keybase.io/marcianosr) on keybase.
• I have a public key ASAPSZ9YQP5P4HGiP6xWj3VfHNk2vtJQvULyWlmSWFWugQo

To claim this, I am signing this object:

marcianosr

ES6Notes / JavaScriptNotes

Why did I make this?

Wrote this document for my own learning purposes to extend my javascript/programming skills. Made it public for other people who think this is useful for themselves. I'm doing my best to write my explanations down in my best english, as straight, practical and as simple as possible. I'm not going in on deep details. Providing code aswell. At this stage of writing, I probably skip and jump over (important) things, but that would probably be because I don't know about it yet. Improvements will come in time :-)

I personally will use this as my reference or handbook so that I have the 'knowledge' in one place until I have it in my head.

---

1 - Basic workings and terms of JavaScript

marcianosr

ReactNotes

For learning purposes and getting better at React, I created 'ReactNotes' to describe what I learned from React, how I interpret the workings of React and how to apply best practices, with little code examples as much as possible.

Why React?

Apart from the Virtual DOM advantages (more on this later), I listed my reasons on why I would use React:

• No Manual DOM traversal: It's easy to get lost in a complex app and while updating data in the DOM. Finding, inserting, updating, removing DOM nodes using JavaScript and passing the right data to the right node can be cumbersome. In React it's the other way round. You declare your component with it's JSX and data (state or props). In React you only update state. React handles DOM manipulation when changing data, all under the hood.
• Component-based writing of elements: React's nature works with a component-based structure. This is makes it easier to think and break down the structure of your application. You declare (think and construct) your comp