he/him 
render() { return ( <> <h1>React v16.2 has been released!</h1> <h2>Introduces a new syntax for fragments!</h2> Thanks to all our collaborators! </> ); }https://reactjs.org/blog/2017/11/28/react-v16.2.0-fragment-support.html …
Referring to JSX as "React" and using a React release as an announcement of syntax availability seems very confusing.
-
-
¯\_(ツ)_/¯
-
Seems super confusing for a beginner that doesn't understand the relationship between all of their tools and libraries. Imagine someone being frustrated when they run `yarn upgrade react react-dom` but `<>` is still throwing a syntax error. I think it matters a lot.
- 2 more replies
New conversation -
-
-
The release is announcing availability of React.Fragment (new export) and semantics associated with it. But to most people, the syntax is just as important to learn about. Seems more confusing to announce separately?
- 3 more replies
New conversation -
-
-
In 10 years we're gonna look back and laugh at how lame it was to have XML (!) in our code.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I used to refer both of them as same thing until this tweet.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
React === (jsx++ vdom) ?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.