Re:Ember.js 3.1 and 3.2 Beta Released
by nerdymanchild on Saturday April 14, 2018 @01:49PM
(#16838447)
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.
[ Parent
| on HN ]
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.
Re:Ember.js 3.1 and 3.2 Beta Released
by vasilakisfil on Saturday April 14, 2018 @01:52PM
(#16838469)
de-Reacting ? Are you going for plain js ? What's your use case?