3 ms·

I respectfully disagree. You don't need constructors and certainly not destructors (really not sure what you mean by this in the context of React, can you elab

by kierenj 10y ago

I respectfully disagree. You don't need constructors and certainly not destructors (really not sure what you mean by this in the context of React, can you elaborate) and these are not really the main OO concepts. Polymorphism, inheritance are, but you don't refer to these? There is no inline XML, and I'm not aware of any other popular (or otherwise) React alternatives where you use long files which create, destroy, append and prepend DOM elements? I'm also not sure what you mean by patch, or what the specific benefit you're highlighting here is - just modularity? You can do that with any framework, it doesn't seem unique to React - at all?

formula1 10y ago
Component will mount/component did mount is effectively construction. Component will unmount is effectively destruction. Apparently them changing the names makes you believe thats not what it is Polymorphism and inheritance can be implemented if you wanted. Mixins were used for a while. Xml is react native and all other alternative rendering that use jsx syntax and a form of react React alternatives where you create/destroy/append/prepend would be the DOM. Patching is interesting in that the inline html isnt actually html until the end of the render loop. I dont remember seeing that anywhere else to be honest. It seems more similar to transforms like in node streams.