Did you watch the React.js documentary released on YouTube a few weeks ago? Some of Facebook's tech engineers spoke about how React started in the company as Bolt.js and how some decisions were made around it. They also talked about how the community rejected the framework when they first introduced it, and how it has changed significantly in the months since.
Even though React.js was created inside one of the biggest tech companies, it's interesting (and inspiring) to see how an idea can grow to become one of the most used libraries in the world of front-end development. From an initial idea to solve a specific problem to an open source modern project with the collaboration of many developers around the globe. An idea that spawned others, such as Redux.
Watch the video and check out some key points below.
Based on the difficulties Facebook's front-end team was having in creating a complex UI at the time, two software engineers created Bolt.js, a client-side MVC framework that tied together some existing JS tools to handle with the complex interactivity of primitive Facebook timeline, chat, news feed and other advanced applications.
But as the use of Bolt.js and also the team grew, Jordan Walk, a product engineer working in ads at the time, had some interesting ideas for changing Bolt, making it much more functional, removing its MVC architecture and adding the concept of re-rendering when something in the UI has changed - that's when React came into being, but with its initial name as FBolt (Functional Bolt). Later they also introduced JSX syntax and, through Jin Chen ideas, another great software engineer, they also introduced ways for handling states in React based on Flux architecture, which was a new chapter in the framework development process.
But it was around 2012, when Facebook acquired Instagram, that the framework was renamed React and the web version of Instagram was the first full end-to-end application in production developed using this modern tool.
The documentary also showed the risky decision they took after several business discussions to continue using React instead of its initial version called Bolt, as React had not yet been fully developed and its use would impact the company's business for a while.
It was then that Sophie Alpert, a non-Facebook developer, saw React and decided to use it. She solved some technical details by rewriting about 2,000 lines of the library's code based on the project she was working on - and then made a pull request to the React repository. And as you can imagine, she became a member of Facebook's engineering team.
And then, in the same year, 2013, they decided to announce React again at the UE JSConf, which took place in Berlin. From that point on, the community slowly started talking about the library and trying it out, realizing the simplicity of how React creates rich UIs. And companies have also started using React. In 2014, Netflix decided to use React to rewrite its platform, which contributed a lot to the library's popularity.
2015 was the year of the first React.js Conf where they made React Native an open source project and started talking about GraphQL and Relay. It was a huge hit with the community and Facebook decided to convert all of their apps to React and remove all other JS frameworks. That's when a few other developers also showed up, including core team member Dan Abramov - famous for creating Redux.
Some of the software engineers responsible for React's success no longer work at Facebook, but they certainly left their legacy there (and in the dev world). :)
- Sophie Alpert
- Dan Abramov
- Vladimir Koesnikov
- Will Bailey
- Jin Chen
One off-topic thing I think is amazing to note is that the documentary highlighted some diversity in IT. I believe there is much more to be done, but having LGBTQAI+ people as managers is inspiring. To be even more complete, I would also like to see more black people in the film.
See you next time! 😁