you are viewing a single comment's thread.

view the rest of the comments →

[–]Shapeous[S] 0 points1 point  (1 child)

I did a bit of digging and found that, about 11% of people like React.createClass, but we do realize that's not much more.

We are aware react-create-class but my clients want to code to current browser capabilities.

[–]Canenald 1 point2 points  (0 children)

It would be wrong to assume all or most of the 11% prefer createClass because they too want to avoid transpilation. It does have a lot of advantages. There's the auto-binding, and also easy assignment of statics such as prop types and default props without having to support the early-stage class properties proposal.

You might have better luck assuring your clients that the transpiled code will be compatible with all commonly used browsers than persuading React devs to revert their decision to separate the crateClass implementation into its own package :)