Published Sep 3, 2019

Episode 86: Interview Dave Thomas

Explore the intersection of academia and industry with Dave Thomas as he delves into aligning research with real-world challenges, shares behind-the-scenes insights on the development of Eclipse, and discusses scaling Agile methodologies and the evolution of programming languages like Smalltalk and Ruby.
Episode Highlights
Software Engineering Radio - the podcast for professional software developers logo

Popular Clips

Episode Highlights

  • Eclipse Origins

    The origins of Eclipse are rooted in a strategic decision by IBM to create a Java-based IDE, driven by marketing needs and the desire to overcome limitations associated with Smalltalk. explains that the development of Eclipse was a collaborative effort involving a talented team, with significant contributions from both IBM and the Smalltalk community. The decision to open-source Eclipse played a crucial role in its success, fostering collaboration with universities and other developers 1.

    Eclipse was built by an incredibly talented team of people and I had the privilege to work with them.

    ---

    Today, Eclipse stands as a legacy IDE, reflecting its historical significance and widespread adoption.

       

    Development Challenges

    Developing Eclipse presented several challenges, particularly in managing technical complexities and team dynamics. highlights the importance of separating the development environment from the execution environment to prevent issues like memory leaks. This separation was a lesson learned from Smalltalk, where the IDE and objects existed in the same memory space, unlike in Ruby or JavaScript 2.

    It's a good thing to separate your development environment in some sense from your execution environment, because things can leak.

    ---

    The need for efficient refactoring and tooling also posed challenges, as IDEs had to constantly reparse code, leading to performance issues and complexity.

Related Episodes