React

Recent posts

React.js Conf 2016 Diversity Scholarship

December 4, 2015 by Paul O’Shannessy

I am thrilled to announced that we will be organizing another diversity scholarship program for the upcoming React.js Conf! The tech industry is suffering from a lack of diversity, but it's important to us that we have a thriving community that is made up of people with a variety of experiences and viewpoints.

When we ran this program last year, we had over 200 people apply for only 10 tickets. There were so many people that we wanted to bring in but we couldn't. The results were still awesome, and we had bright individuals from around the world attending who would have otherwise been unable to. These attendees took part in discussions at the conference and brought perspectives that we might not have otherwise seen there.

This year we're excited to bring back the scholarship, but we've set aside 40 tickets because we really believe that it's important to do our best to make sure we have an even more diverse audience.

This is something I'm personally really excited to be a part of. I know the rest of the team is as well. We're really proud to have everyone at Facebook providing support and funding for this.

The details of the scholarship are provided below (or you can go directly to the application). I encourage you to apply! If you don't feel like you are eligible yourself, you can still help – send this along to friends, family, coworkers, acquaintances, or anybody who might be interested. And even if you haven't spoken before, please consider submitting a proposal for a talk (either 30 minutes or just 5 minutes) - we're hoping to have a very diverse group of speakers in addition to attendees.

Facebook is excited to announce that we are now accepting applications for the React.js Conf Diversity Scholarship!

Beginning today, those studying or working in computer science or a related field can apply for a partial scholarship to attend the React.js Conf in San Francisco, CA on February 22 & 23, 2016.

React opens a world of new possibilities such as server-side rendering, real-time updates, different rendering targets like SVG and canvas. React Native makes is easy to use the same concepts and technologies to build native mobile experiences on iOS and Android. Join us at React.js Conf to shape the future of client-side applications! For more information about the React.js conference, please see the website.

At Facebook, we believe that anyone anywhere can make a positive impact by developing products to make the world more open and connected to the people and things they care about. Given the current realities of the tech industry and the lack of representation of communities we seek to serve, applicants currently under-represented in Computer Science and related fields are strongly encouraged to apply. Facebook will make determinations on scholarship recipients in its sole discretion. Facebook complies with all equal opportunity laws.

To apply for the scholarship, please visit the application page: http://goo.gl/forms/PEmKj8oUp4

Award Includes

  • Paid registration fee for the React.js Conf Feburary 22 & 23 in downtown San Francisco, CA
  • Paid lodging expenses for February 21, 22, 23

Important Dates

  • Sunday December 13th 2015 - 11:59 PST: Applications for the React.js Conf Scholarship must be submitted in full
  • Wednesday, December 16th, 2015: Award recipients will be notified by email of their acceptance
  • Monday & Tuesday, February 22 & 23, 2016: React.js Conf

Eligibility

  • Must currently be studying or working in Computer Science or a related field
  • International applicants are welcome, but you will be responsible for securing your own visa to attend the conference
  • You must be able to provide your own transportation to San Francisco
  • You must be available to attend the full duration of React.js Conf on February 22 & 23 in San Francisco, CA

React v0.14.3

November 18, 2015 by Paul O’Shannessy

It's time for another installment of React patch releases! We didn't break anything in v0.14.2 but we do have a couple of other bugs we're fixing. The biggest change in this release is actually an addition of a new built file. We heard from a number of people that they still need the ability to use React to render to a string on the client. While the use cases are not common and there are other ways to achieve this, we decided that it's still valuable to support. So we're now building react-dom-server.js, which will be shipped to Bower and in the dist/ directory of the react-dom package on npm. This file works the same way as react-dom.js and therefore requires that the primary React build has already been included on the page.

The release is now available for download:

We've also published version 0.14.3 of the react, react-dom, and addons packages on npm and the react package on bower.

Changelog

React DOM

  • Added support for nonce attribute for <script> and <style> elements
  • Added support for reversed attribute for <ol> elements

React TestUtils Add-on

  • Fixed bug with shallow rendering and function refs

React CSSTransitionGroup Add-on

  • Fixed bug resulting in timeouts firing incorrectly when mounting and unmounting rapidly

React on Bower

  • Added react-dom-server.js to expose renderToString and renderToStaticMarkup for usage in the browser

React v0.14.2

November 2, 2015 by Paul O’Shannessy

We have a quick update following the release of 0.14.1 last week. It turns out we broke a couple things in the development build of React when using Internet Explorer. Luckily it was only the development build, so your production applications were unaffected. This release is mostly to address those issues. There is one notable change if consuming React from npm. For the react-dom package, we moved react from a regular dependency to a peer dependency. This will impact very few people as these two are typically installed together at the top level, but it will fix some issues with dependencies of installed components also using react as a peer dependency.

The release is now available for download:

We've also published version 0.14.2 of the react, react-dom, and addons packages on npm and the react package on bower.

Changelog

React DOM

  • Fixed bug with development build preventing events from firing in some versions of Internet Explorer & Edge
  • Fixed bug with development build when using es5-sham in older versions of Internet Explorer
  • Added support for integrity attribute
  • Fixed bug resulting in children prop being coerced to a string for custom elements, which was not the desired behavior.
  • Moved react from dependencies to peerDependencies to match expectations and align with react-addons-* packages

React v0.14.1

October 28, 2015 by Paul O’Shannessy

After a couple weeks of having more people use v0.14, we're ready to ship a patch release addressing a few issues. Thanks to everybody who has reported issues and written patches!

The release is now available for download:

We've also published version 0.14.1 of the react, react-dom, and addons packages on npm and the react package on bower.

Changelog

React DOM

  • Fixed bug where events wouldn't fire in old browsers when using React in development mode
  • Fixed bug preventing use of dangerouslySetInnerHTML with Closure Compiler Advanced mode
  • Added support for srcLang, default, and kind attributes for <track> elements
  • Added support for color attribute
  • Ensured legacy .props access on DOM nodes is updated on re-renders

React TestUtils Add-on

  • Fixed scryRenderedDOMComponentsWithClass so it works with SVG

React CSSTransitionGroup Add-on

  • Fix bug preventing 0 to be used as a timeout value

React on Bower

  • Added react-dom.js to main to improve compatibility with tooling

Reactiflux is moving to Discord

October 19, 2015 by Paul Benigeri

TL;DR: Slack decided that Reactiflux had too many members and disabled new invites. Reactiflux is moving to Discord. Join us: http://join.reactiflux.com

What happened with Slack?

A few weeks ago, Reactiflux reached 7,500 members on Slack. Shortly after, Slack decided we were too big and disabled invites. There was no way for new users to join. Many of us were sad and upset. We loved Slack. Our community was built around it.

We reached out to Slack several times, but their decision was firm. Our large community caused performance issues. Slack wants to focus on building a great product for teams, not necessarily large open communities. Losing focus and building for too many use cases always leads to product bloat, and eventually a decrease in quality.

So… why Discord?

After a long and thorough debate, Discord quickly emerged as the most promising service. After just a few days, 400 members had joined the Discord server, and many already loved it.

Easiest to join

Discord is the easiest platform to join. New users can immediately join our conversations without having to create an account. All they need to do is provide a name. No permission granting, no password, no email confirmation.

This is critically useful for us, and will make Reactiflux even more open and accessible.

Great apps

Out of all of the services we’ve tried, Discord’s apps are by far the most polished. They are well designed, easy to use, and surprisingly fast. In addition to the web app, they have mobile apps on both iOS and Android as well as desktop apps for OS X and Windows, with Linux support coming soon.

Their desktop apps are built with React and Electron, and their iOS app is built with React Native.

Moderation tools

So far, we’ve been fortunate not to have to deal with spammers and trolls. As our community continues to grow, that might change. Unsurprisingly, Discord is the only app we’ve seen with legitimate moderation tools. It was built for gaming communities, after all.

Great multiple Server support

Your Discord account works with every Discord server, which is the equivalent of a Slack team. You don’t need to create a new account every time you join a new team. You can join new servers in one click, and it’s very easy to switch between them. Discord messages also work across servers, so your personal conversations are not scoped to a single server.

Instead of having one huge, crowded Reactiflux server, we can branch off closely related channels into sub-servers. Communities will start overlapping, and it will be easy to interact with non-Reactiflux channels.

It’s hosted

Self-hosted apps require maintenance. We’re all busy, and we can barely find the time to keep our landing page up to date and running smoothly. More than anything, we need a stable platform, and we don’t have the resources to guarantee that right now.

It’s a much safer bet to offload the hosting to Discord, who is already keeping the lights on for all their users.

We like the team

And they seem to like us back. They are excited for us to join them, and they’ve been very responsive to our feedback and suggestions.

They implemented code syntax highlighting just a few days after we told them we needed it.

Discord’s team has already built a solid suite of apps, and they have shown us how much they care about their users. We’re excited to see how they will continue to improve their product.

And what’s the catch?

Choosing the best chat service is subjective. There are a million reasons why Discord might be a terrible idea. Here are the ones that we’re most worried about:

Difficult channel management

Channel management seems to be the biggest issue. There is no way to opt out of channels; you can only mute them. And you can only mute channels one by one. There is no way to star channels, and channels can only be sorted on the server level. Each user will see the list of channels in the same order.

As the number of channels grow, it will be challenging to keep things in order. Branching off sub-servers will help, and we will keep an easily accessible directory of channels across our main server and all of the sub-servers.

We can build simple tools to make channel lookup easier, and the Discord team is working on improvements that should make this more manageable.

No Search

Lack of search is clearly a bummer, but Discord is working on it. Search is coming!

Firewall

A couple of users aren’t able to access Discord at work since other corporate filters classify it as a gaming application. This sucks, but it seems to be a rare case. So far, it seems only to affect 0.6% of our current community (3/500).

We hope that these users can get Discord's domains whitelisted, and we’ll try to find a solution if this is a widespread issue. The Discord team is aware of the issue as well.

Is Discord going to disappear tomorrow?

Probably not tomorrow. They have 14 people full time, and they’ve raised money from some of the best investors in Silicon Valley, including Benchmark and Accel.

By focusing on gaming communities, Discord has differentiated itself from the many other communication apps. Discord is well received and has a rapidly growing user base. They plan to keep their basic offerings free for unlimited users and hope to make money with premium offerings (themes, add-ons, content, and more).

Join us!

More than 500 of us have already migrated to the new Reactiflux. Join us, we're one click away: http://join.reactiflux.com

Note: Jordan Hawker’s thorough research made our decision a lot easier.