DHH on the Evolution of Web Development, Ruby on Rails, and the Pursuit of Developer Ergonomics

This episode features David Heinmeier Hansson (DHH), creator of Ruby on Rails and co-owner of 37signals, discussing his journey into programming, the philosophy behind Ruby on Rails, and his critical perspective on modern web development. DHH recounts his early failures to learn programming on systems like the Commodore 64 and Amiga, highlighting the frustration of complex setups and the eventual breakthrough he experienced with HTML and PHP due to their immediate feedback and ease of deployment. He emphasizes that this early "developer ergonomics"—the simplicity of getting dynamic web pages online—became a guiding principle for his work, particularly with Ruby on Rails and its 'No Build' philosophy.

DHH critiques the current state of web development, arguing that many developers, whom he playfully calls "CRUD monkeys," overcomplicate systems to compensate for the perceived simplicity or "existential dread" of their core tasks. He laments the loss of the straightforward development experience of the late 90s, exemplified by Peter Levels' minimalist approach, and positions Rails 8's 'No Build' as an effort to reclaim that ease without sacrificing modern advancements. He specifically targets the "dark ages" of JavaScript development (2010-2020), characterized by excessive churn, complex build pipelines like Webpack, and a "mass hysteria" of constantly rewriting frameworks, which he believes created an unnecessarily unpleasant development environment.

The conversation also delves into the history and impact of web browsers. DHH attributes the stagnation of browser technology to Microsoft's dominance with IE5 and credits Google Chrome, despite its commercial entanglements and privacy concerns, with revitalizing the web as a development platform by fostering competition and innovation. He acknowledges that some complexity was a necessary "bridge" to reach today's highly capable browsers, which can parse even "smelly code" and maintain remarkable backward compatibility. However, he expresses concern about the potential for a browser monoculture and supports independent projects like Ladybird, which aim to create new browser engines.

Finally, DHH touches on broader implications, including the antitrust debate surrounding tech giants. While generally sympathetic to antitrust efforts, he argues that the browser market, with its existing competition (Firefox, Chrome), is not the primary area of concern. He underscores the importance of an open web, championed by entities like Google, for the continued flourishing of web technologies and the opportunities it provides for developers worldwide. The discussion ultimately advocates for a return to simplicity and developer happiness, leveraging modern browser capabilities to streamline the creation and deployment of web applications.

No one anywhere who's serious believes that Cookie banners does anything good for anyone. Yet, we've been unable to get rid of it.

A lot of people, I think, are very uncomfortable with the fact that they are essentially CRUD monkeys. They just make systems that create, read, update, or delete rows in a database. And they have to compensate for that existential dread by over complicating things.

That balance of danger and skill is what's so intoxicating.

I remember not understanding the purpose of a variable. If if there's a thing and you assign something, why would you assign another thing to it?

PHP to me didn't just give me a start in terms of making my own web applications it actually gave me a bar in many ways I think the pinnacle of developer web developer ergonomics is late '90s PHP.

It sometimes feels like we're barely better off. Like web pages aren't that different from what they were in the late 90s, early 2000s. They're still just forms. They still just write to databases.

The amount of churn that the JavaScript community, especially with its frameworks and its tooling, went through in the decade from 2010 to 2020 was absurd.

This is one of the hardest problems in computing today is to parse the entire internet because thankfully for us as web developers but perhaps not so much for the browser developers every web page that has ever been created minus the brief period with flash still runs today.

Chrome is a complete gift to web developers everywhere to the web as a development platform and they deserve an enormous amount of credit I think for that even if it's entangled with their business model and half of Chrome is code that spies on you or informs targeted ads and a bunch of things I'm not a big fan of.

I do think we have antitrust problems in technology. But the one place where we don't have them by and large is with browsers, is with the tools we use to access the open web.