Complexity: Divide and Conquer! - Michel Weststrate
Vložit
- čas přidán 6. 05. 2017
- Find the latest React.js talks & workshops at portal.gitnation.org
🗓 Talk from React Amsterdam Conference 2017
Check out the latest React Summit Amsterdam news - reactsummit.com
See other React conferences by GitNation
React Day Berlin - reactday.berlin
React Advanced London - reactadvanced.com
Michel Weststrate, Full-stack Lead Developer at Mendix
"Reactive programming" still sounds scary to many developers. As if it is an elevated way of thinking, only accessible to the chosen few. Nothing is less true! It is the most natural way to look at programming problems. You just might not realize it yet! In this talk, Michel will demonstrate that many complex UI problems, such as form validation and routing, can all be seen as '*actions* that change facts which leads to *reactions*'. And as soon as we start distinguishing those concepts in our applications; our code will become more declarative, more concise and less imperative.
Subscribe to our channel to see more React (Native) talks: / @reactconferences - Věda a technologie
This talk is the real eye-opener! :)
22:26 BookDetails component depends on the internal structure of the store. What if we decide to have several carts or just rename it? We'll have to find all components where it is used. What if in some component we separated 'shop' from 'cart'? We wouldn't have any common pattern to find such entries. It reminds me immutable that tends to poison all parts of code with its API and it is very hard to find such places. I think that view components should know nothing about the external state and just invoke passed addBook() property. Some outer component (container) may connect it to the store. Same for BookEntry. It depends on shop.view.openBookPage blocking any refactoring of internal structure of the store. I think it should just invoke onClick property.
Regarding renaming. With modern IDE you simply use refactoring option Rename and it renames specific symbol everywhere in your codebase. Also with use of TypeScript you will probably get warnings in every place you forgot to rename it.
Thanks for that.
ShopStore