What I Learned at QCon SF: Webpack, RxJS, and the Future of Frontend Frameworks

Conference Overview

In early November the author attended QCon in San Francisco, using the opportunity to visit several US tech companies and reflect on the experience.

Conference Content

The agenda covered frontend, design, containers, micro‑services, DevOps, Java, and more; the following sections focus on the frontend talks.

Webpack: The One Build Step To Rule Them All

Webpack has become a global standard for building web applications.

The core concepts presented were:

Entry – the source file(s) that start the bundle.

Main features include local development server, hot module replacement, lazy loading, and source maps.

Webpack 2 new features:

Native ES2015 support, laying the groundwork for tree‑shaking.

Tree‑shaking to remove unused code, dependent on coding standards and component quality.

Improvements in compilation speed, syntax design, and configuration validation.

Future direction:

Optimizations for HTTP/2 and tighter integration with browsers via DevTools.

Potential use of Chrome timeline data for intelligent configuration adjustments.

Building Robust Web Applications With RxJS

RxJS is an API for asynchronous programming with observable streams.

The talk highlighted RxJS as “Lodash for events” and explained that everything is treated as a stream, allowing developers to compose, filter, and combine streams to decouple business logic.

A demo WebSocket example was provided, and the code is available on GitHub.

The Strengths of Ember, Angular & React Explored

Representatives from Ember, Angular, and React discussed their libraries/frameworks.

React – component‑based UI library, not a full MVC framework; can be used partially or across the whole app; extensive ecosystem of libraries.

AngularJS – components consist of HTML, CSS, and class; uses TypeScript; provides routing; runs on any platform; Angular 2 improves performance via pre‑compilation.

Ember – designed for large, long‑lived applications; offers routing, components, data binding, server‑side rendering, and a mature ecosystem with thousands of addons.

The discussion emphasized that no single framework is best; each has trade‑offs and evolves by learning from the others.

Tech Companies Visited

Yelp

Yelp’s downtown office spans many floors, offers free snacks, standing desks, and a flexible eight‑hour workday; most traffic comes from PC, with only 20‑30% from mobile; they use AWS.

Airbnb

The office features artistic design and standing desks; the company’s front‑end style guide influences the author’s own standards, though enforcement varies; mobile traffic is also around 30‑40%; they use AWS.

Twitter

Twitter’s downtown campus houses over 2,000 employees, includes large open spaces and a rooftop terrace; they run their own infrastructure rather than AWS and built custom container‑like solutions.

Google

Google’s visitor center showcased an Android exhibit, a Google Earth demo, and ChromeBook displays; offices feature standing desks and even sleeping pods; the campus includes cafeterias, game rooms, and recreational areas.

Facebook

Facebook’s campus resembles a colorful small town with shops, restaurants, and themed offices; the culture emphasizes code visibility even in restrooms; numerous photos illustrate the vibrant environment.

Conclusion

While many QCon frontend talks were introductory and lacked deep practical demos, they provided insight into how technologies are adopted and evolved. Visits to US companies revealed a common reliance on AWS, relaxed work environments, and cultural differences in product usage and innovation. The experience underscores the importance of understanding both technical trends and the broader ecosystem.