No, I'm not opposed to the Class-oriented interface though... I think it makes writing stateful components easier. I'm pretty pragmatic about it, I'd rather have clean code that makes sense than subscribe to dogma. That said, I do tend to favor the functional render component most of the time.
I mean direct render method components... you don't have to inherit from Component or use the legacy method at all if you don't want to.
export default MyComponent(props, context) {
return <div>Hello {props.name}!</div>
}
I happen to like React because it's functional representation all the way down, and I tend to like JSX in my JS vs. weird DSL in templating system in my HTML referenced with JS. But that's just me.
I can see the appeal of Vue.. and frankly, can see the appeal of Polymer as well. However, I find React feels better when I've used it.
The one point that rings true to me is "Focusing on poor metrics such as “issues closed” or “commits per day”"...
I was on the verge of being fired (I moved on to another position before that happened), because my issues list didn't have as many closed items as other developers.
Despite the fact that I'd literally removed over 20kb of code from the project (the prior month) with mild refactoring, using better techniques and all the code I did refactor/add was 100% tested. I also helped a lot of the other developers in the group, and had to participate in the meetings for two teams. But no, the issues closed ruled the roost so to speak.
Mistake towards the top, in the second code segment...
someModule(param, (result, error) => {
should be
someModule(param, (error, result) => {
Node-style CJS async methods should *always* have error first in the response... those few API interfaces that don't cause issues with other libraries.
I mean direct render method components... you don't have to inherit from Component or use the legacy method at all if you don't want to. export default MyComponent(props, context) { return <div>Hello {props.name}!</div> }Mistake towards the top, in the second code segment... someModule(param, (result, error) => { should be someModule(param, (error, result) => { Node-style CJS async methods should *always* have error first in the response... those few API interfaces that don't cause issues with other libraries.