New post on /r/flutterdev subreddit:
<b>Full stack Flutter devs?</b>
I <a href="
https://www.reddit.com/r/dartlang/comments/jzict9/functions_framework_for_dart_is_heading_your_way/">posted</a> under <a href="/r/dartlang">r/dartlang</a> yesterday that we just open-sourced the Functions Framework for Dart. I also <a href="
https://twitter.com/tonypujals/status/1330872613313282048">tweeted</a> about it. Here's what really struck me while I was checking out the profiles of people who liked or retweeted my tweet: <strong>a huge percentage of folks listed Flutter as their primary or only area of expertise!</strong>Because I'm coming at this from the serverless perspective, this took me a bit by surprise. But it makes sense that the vast majority of people programming Dart are developing Flutter apps, so I suppose I really shouldn't be quite so surprised.It also implies to me that there are quite a few people who consider themselves (or are interested in being) full-stack developers who have an appetite for leveraging Dart on the backend.This also makes sense. I spent a long time as a Node.js developer, primarily doing backend development, but I worked with many full stack devs who really liked using JavaScript both on the frontend and the backend -- it's nice to leverage the expertise you invested time and energy into mastering for a specific programming language on both sides of a web request.But it also resonates with me for another reason. Although I've been focused on the cloud side of things for quite some time, I spent years building "connected desktop clients" and "rich internet applications" for the browser using a variety of UI frameworks and platforms, going back to Java applets through Swing and JFC for Java, as well as WPF and Silverlight for .NET, for long list of enterprise line of business applications.I personally never fell in love with building web apps using HTML/CSS/JavaScript. As more and more frontend work shifted to the web, I focused more and more on server code.Flutter brings me back full circle to the excitement of building user interfaces that began with my first HyperCard stacks back in the late 80's. I'm more new to Flutter than probably 99.9% of all you subscribed to this subreddit.Let me be clear, my enthusiasm for Flutter isn't about drinking the Kool-Aid at work. Even when I was director of cloud engineering at Appcelerator, I didn't care about Titanium (and I mean absolutely no disrespect to the talented team we had there). It's just that at that point of my career I far more excited about building out our MBaaS (mobile backend as a service, basically a PaaS for hosting APIs on the backend that the mobile client apps used) than I was about building user interfaces.As a developer advocate at Google, I have a lot of choice for what areas I want to focus on. I saw an opportunity to bring serverless support to Dart -- a language that intrigued me for a number or reasons. I remember having a conversation and sharing my enthusiasm about Dart with Jeff Haynie, the CEO at Appcelerator, back around 2015 or 2016. We were a hard-core Node.js team and we loved JavaScript, but we were also quite experienced with its pain points.Having spent years as a Java and C# developer, Dart looked really appealing and promising to me even then. Ironically, I'd spend the next few years with Go just because it beginning to dominate in the cloud tooling space, so we adopted it for our next generation CaaS/FaaS, but that's another story...So back to Dart ... and Flutter. As I began drafting a plan on bringing serverless support to Dart, it occurred to me that considering how much I enjoyed using Java or C# to develop both desktop apps and web services, the same must be true -- or would be true -- for a lot of Flutter devs.Dart has been marketed as a client-optimized language for quite some time, but this does not mean that there's anything intrinsic to the language that implies it's not a good language for the backend. It simply…