Re:Why is React is taking over front-end development?
by crimsonalucard on Wednesday May 10, 2017 @01:49PM
(#14310083)
Just want to mention. Does it make sense for a model in the backend to be immutable? Imagine that... Immuteable mysql... Why does this make sense on the front end? Why? Why? Why?
Re:Why is React is taking over front-end development?
by iLemming on Thursday May 11, 2017 @12:26PM
(#14317275)
You ever heard about Datomic?
Re:Why is React is taking over front-end development?
by crimsonalucard on Thursday May 11, 2017 @06:54PM
(#14320196)
Nope. What about it?
Take javascript for example. Let's face it... javascript is a shit language. Why did it take over front end web development? Because of Logic? No. Why did React take over front end web development? Because of Logic? Maybe.
The react + redux ecosystem has major issues that need to be addressed.
Problem #1: complex tool chain.
Problem #2: Forced OOP. Components need to be objects to use this.setState(). Why is this design necessary? See cycle.js.
Problem #3: redux... functional programming / immutable programming is not necessarily the best choice for a Model in any architecture that contains a model (MVC). Try building an app with a complex tree structure for the model then update a node in the middle of that tree and see what immutability does for you... Welcome to the world of Zippers and lenses..
In fact View components should be immutable and the model itself should be mutable... In react + redux it's the other way around!
We can do better. React + redux are not the holy grail.