React Went Public at JSConf US in May 2013

On May 29, 2013, a small audience at JSConf US in Portland, Oregon watched Tom Occhino and Jordan Walke introduce a JavaScript library that most of the room had never heard of. That talk, titled "React: Rethinking best practices," marked the moment React left the walls of Facebook and entered the wider world. For anyone who grew up building interfaces in the era that followed, it is strange to think that the framework now running a large share of the modern web was once a guarded internal project making its public debut at a conference.

React did not appear out of nowhere. It had been growing inside Facebook since 2011, when Jordan Walke, an engineer at the company, began experimenting with a declarative approach to building UIs. The idea was shaped by his earlier work on XHP, a PHP extension that let you write HTML as composable tags, and it matured into an internal JavaScript library. Initially called FaxJS, the prototype was first exercised in Facebook's ads product and later in the News Feed, where the team was fighting the performance and complexity of managing pages that update constantly. The problem React set out to solve was straightforward in outline and thorny in practice: how do you build a large, stateful, ever-changing interface without your DOM logic becoming an unmaintainable tangle?

React's answer was radical for its time. Instead of telling the browser exactly how to change, you describe what the UI should look like for a given state, and React figures out how to make the DOM match. The rendering is declarative: you build a virtual model of the interface, and a reconciliation algorithm computes the minimal set of real DOM mutations needed to bring the page in line with the model. The kicker was that a full re-render of the virtual tree is cheap compared to touching the real DOM, so developers could reason about simple render functions and let the library handle the dirty work of updating the page.

The JSConf announcement was not instantly triumphant. The audience, made up largely of developers steeped in MV* patterns from Backbone and Angular's early days, met the "HTML in your JavaScript" idea with real skepticism. Writing markup directly inside JavaScript, via what would become JSX, felt like a step backward to people trained to keep templates separate from logic. Some dismissed it as a rehash of older ideas or a backwards-looking trick. But the proof was in the production systems behind it. Facebook was already running React at scale on its News Feed, and the performance and maintainability gains were real, not hypothetical. Persistence and evidence won out over first impressions.

That 2013 open sourcing matters to working developers because it flipped the technology from a company secret into an ecosystem. Within a couple of years React had accumulated a wave of contributors, tooling, and adjacent libraries, and its ideas began to reshape the whole front-end field. Declarative rendering, component composition, and the component lifecycle influenced everything from Vue to the evolution of other libraries. The Facebook-GitHub open source model, with RFCs, large community momentum, and eventually a move to the MIT license in 2017, set a template for how a widely used framework is governed in the open.

Looking back, the JSConf talk is a useful object lesson in judging technology by engineering results rather than fashion. The same tactical critiques that once got React dismissed, mixing markup with logic, full re-renders, unfamiliar abstractions, are now the default mental model for an entire generation of interface developers. When you build with something like React today, you are standing on a decision made at a Portland conference over a decade ago, a decision that validated the value of an unconventional idea because someone had actually shipped it to millions of users.

The takeaway for a senior developer is simple: good technology earns its place through results, but it still needs a moment of public exposure to reach the developers who will build on it. That single May 2013 talk turned React from an internal experiment documented only inside Facebook into the foundation of the modern JavaScript front-end, and it remains one of the most consequential open source announcements in web history.