| // Problem Statement : | |
| // Write a function called deepClone which takes an object and creates a copy of it. | |
| // e.g. {name: "Paddy", address: {town: "Lerum", country: "Sweden"}} -> {name: "Paddy", address: {town: "Lerum", country: "Sweden"}} | |
| // Solution | |
| // This file shows ability of multiple approach with their advantages and disadvantages and 2 fully tested and working approach. | |
| // One has been written by me and another has been received from community to showcase that self written code is more concise and readable. | |
| // Just run this file in Node Js environment to get the result. | |
| // To run test cases, un comment method named test() in the bottom of file |
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
