[deleted]
React Fire: Modernizing React DOM
41–50 of 113 posts
Re: React Fire: Modernizing React DOM
#42Earlier quoted context omitted.
Yes, a double-edged sword. It's to the credit of the React developers that they've welcomed him. I was just curious as to how the internal politics work there.
People on the team who like to have presence on social media do that. People who don't like it that much, don't. I don't see much politics in this but maybe I'm missing something.
My apologies, I'm guess I'm just too used to seeing internal politics everywhere.
Re: React Fire: Modernizing React DOM
#43So, I've only used react indirectly via Clojurescript and https://github.com/tonsky/rum for a personal project... I don't spend much time in the front-end otherwise, but every time I read something about using React from JS as one would regularly it feels much, much more complicated. I.e. I just write functions that return hiccup-html lists, and @decorate a cursor into my immutable state structure for reactive update…
Certainly, clojurescript makes it possible to do productive React development without having to resort to JSX for syntactic sugar- This comes from the "create your own language" nature of lisp languages, which is leveraged by the many different frameworks to easily generate DOM elements in a natural way. (This also makes it easy to implement graph query languages BTW that are more elegant IMHO than graphQL.)
Another big payoff with clojurescript IMHO is the use of async channels and go blocks in lieu of promises to handle asynchronous operations- It's nice to have what is essentially a form of cooperative multithreading right inside your client javascript code, without the need for web workers.
Re: React Fire: Modernizing React DOM
#44I find it quite interesting how much of the public face of React that Dan Abramov has become. I really like the openness with which he speaks via his blog, but it feels like all the important React announcements come through him and I'm sure there must be some other very senior FB developers who created React before he arrived who might not be so happy.
We generally post on our blog when something is _ready_. Blog has to be very high signal/noise ratio so we don't announce something that might be experimental or has a risk of changing significantly there. Because it creates a lot of churn. Announcements about work in progress (which might be interesting to spectators but doesn't affect anyone's day-to-day usage of React) typically comes from people working on those…
This may be the wrong place, but in response about being a "developer advocate" what about other react projects? react-document-title has a few pull requests without any feedback, I've personally been sidelined since Februrary https://github.com/gaearon/react-document-title/pull/53 when I made a pull request to avoid having to wrap multiple children in a React.Fragment that's child to a DocumentTitle
Maybe my PR was too drastic, I could've just removed the call to React.Children.only
Re: React Fire: Modernizing React DOM
#45I find it quite interesting how much of the public face of React that Dan Abramov has become. I really like the openness with which he speaks via his blog, but it feels like all the important React announcements come through him and I'm sure there must be some other very senior FB developers who created React before he arrived who might not be so happy.
I manage the React team at Facebook. Only a couple of us have been on the team since before Dan, and I don’t think anyone resents his public persona. Quite to the contrary – Dan does a great job representing us. :)
Re: React Fire: Modernizing React DOM
#46I find it quite interesting how much of the public face of React that Dan Abramov has become. I really like the openness with which he speaks via his blog, but it feels like all the important React announcements come through him and I'm sure there must be some other very senior FB developers who created React before he arrived who might not be so happy.
I manage the React team at Facebook. Only a couple of us have been on the team since before Dan, and I don’t think anyone resents his public persona. Quite to the contrary – Dan does a great job representing us. :)
Thanks for the reply. Good to hear.
Re: React Fire: Modernizing React DOM
#47I recently went through a framework selection between React, Vue and Angular. I ended up with React for reasons typified by this post. There is a massive community and a great dev team (Facebook) interested in evolving and improving React over time.
I recently went through same thing at our company and decided on angular. I really appreciate the overall framework architecture angular provides. React doesnt really give that
Re: React Fire: Modernizing React DOM
#48When react already has to be "modernized" I become thankful that I don't work in JS land. I honestly don't think I could keep up and remain happy.
Re: React Fire: Modernizing React DOM
#49I want to say Great work, even if it's not done yet.
The react team obviously works well together, the vision is here and as an engineer who's been doing frontend work for 15 years (using flex, vanillaJS, various home-made frameworks, backbone, knockout, angular, etc) let me tell you I've never seen another framework/library come half way close to React.
By the way, why not use this big, breaking release to start offering another way to write stateful components from functions? (ES6 classes, prototypes and anything that forces me to use "this" are still part of the very bad parts of JS, imo)
Re: React Fire: Modernizing React DOM
#50When react already has to be "modernized" I become thankful that I don't work in JS land. I honestly don't think I could keep up and remain happy.
You should read the link, these changes are less "modernizing" the API, and more doing the internals, many of which haven't changed since 2013.
In that process there will probably be some breaking changes, but Facebook has some insane number of components they use internally, so they try to never make any breaking changes that can't be automatically migrated.