w/simple transform, React .14 reuses the same elements for static parts of the page, handlebar templates not required http://babeljs.io/blog/2015/03/31/5.0.0/#react-optimisations …
-
-
-
Replying to @SlexAxton
@SlexAxton Yeah, still basically JS though. Might be a way to do it without, but would be hard to disambiguate components... good point2 replies 0 retweets 0 likes -
Replying to @jlongster
@jlongster@SlexAxton Ultimately this optimization requires a static compilation step of markup, right? Pure JS loses the optimization.3 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@SlexAxton Yes, that's true, but it's something that could only be done for production if you only have a build step there1 reply 0 retweets 0 likes -
Replying to @jlongster
@jlongster@wycats@SlexAxton The original React task includes both React.createFactory/createElement and JSX. Not sure what Babel does.2 replies 0 retweets 0 likes -
Replying to @sebmarkbage
@sebmarkbage@wycats@SlexAxton I don't think anyone who writes raw JS DOM uses those manually inside `render`, fwiw1 reply 0 retweets 0 likes -
Replying to @jlongster
@jlongster createFactory at the top of the file is still used/recommended. That's trackable in the module scope.@wycats@SlexAxton2 replies 0 retweets 0 likes
@sebmarkbage React.createFactory isn't taken into consideration right now, no. @jlongster @wycats @slexaxton
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 