My team is actually in the process of de-Reacting our code base. These frameworks are full of hacks underneath the covers, and their abstractions are mostly ill-specified.
Apart from the very annoying Event compatibility layer with its event pooling and central handling that breaks the usual DOM event bubbling, I never saw something bad enough that would make someone consider de-Reacting.
As much as I dislike magic, JS libs working with the DOM will always have code that isn't as clean as your application code.
Comments
My team is actually in the process of de-Reacting our code base. These frameworks are full of hacks underneath the covers, and their abstractions are mostly ill-specified.
Explain that bold claim?
Apart from the very annoying Event compatibility layer with its event pooling and central handling that breaks the usual DOM event bubbling, I never saw something bad enough that would make someone consider de-Reacting.
As much as I dislike magic, JS libs working with the DOM will always have code that isn't as clean as your application code.
de-Reacting ? Are you going for plain js ? What's your use case?