Very Good Engineering

From Dart to Flutter: The Evolution of a Language and a Framework

BE

Brian Egan

Director of Engineering, Very Good Ventures

Brian Egan, Very Good Ventures — The Evolution of Dart and Flutter

Jorge Coca sits down with Brian Egan, Director of Engineering at Very Good Ventures, to trace Dart from its 2011 origins at Google to its role as the language behind Flutter. Brian shares his own early encounter with Dart while working at Zappos, installing an IDE plugin and starting to explore what the language could do at a time when it was pitched as a modern alternative to JavaScript for increasingly complex web apps.

The conversation covers why Dart felt approachable, its C-like syntax welcomed developers coming from Java and JavaScript, and how the arrival of type safety proved especially valuable on team projects. Brian and Jorge revisit the early skepticism, when many in the community doubted Dart could coexist with, let alone challenge, JavaScript’s dominance on the web.

Brian describes the turning point when Flutter emerged and put Dart’s strengths to work for mobile development. His own move to Flutter was driven by a search for faster iteration and better performance than native Android offered, with hot reload and hot restart winning him over. They close on how the language matured, from dropping the new keyword for cleaner code to gaining true sound type safety, alongside Flutter’s expansion well beyond mobile.

Frequently Asked Questions

When did Dart start?

Dart originated at Google in 2011, pitched as a modern alternative to JavaScript for increasingly complex web applications.

Why did Dart feel approachable to developers?

Its C-like syntax welcomed developers coming from Java and JavaScript, and the arrival of sound type safety proved especially valuable on team projects.

What won Brian Egan over to Flutter?

The search for faster iteration and better performance than native Android offered, with hot reload and hot restart being the decisive features.