 Hey, welcome back everybody. Jeff Frick here with theCUBE. We're at Node Summit 2017, downtown San Francisco Mission Bay Conference Center. 800 people, a lot of developers, pretty much all developers, talking about what's going on with Node, the Node community, and some tangential things that are involved in Node as well. We're excited to have our next guest on. He's Steven Fluen. He's a developer advocate for Google. Steven, welcome. Thank you so much for having me. Absolutely. So first off, just kind of impressions of the show. You said you were here last year. The community is obviously very active, growing. I don't know that they're going to be able to come back to this space for very much longer. What do you think? Probably not. I love how the community is continuing to grow and evolve, right? Because this technology is moving faster than almost any technology I've seen before, right? I call it a combinatorial explosion of complexity because there's always new tools coming out, new ways of thinking, and that's really rich and a great way to have a lot of innovation happening. Right, there was a great, one of the early ones this morning, the speaker said they had one Node app a year ago and now they have 15 in production, 22 almost ready, and 75 other internal projects in one year. Yeah, it's definitely crazy. So why? I mean, there's lots of things as to why Node's successful, but from your perspective, why is it growing so fast? Sure, I think it's fast because it's the first time that we have had a real extended ecosystem where a lot of developers are coming together, bringing their own perspectives, and it's a very collaborative environment. Everyone's trying to help each other. Okay, so you just got off the off stage, you had your own session? I did. You were on the server, you used for the folks that missed it, kind of what was the main theme of your talk? Sure, sure, so I'm on the Angular team, which is a client-side framework for building applications, and so we've really been focused a lot on really great web experiences for the client. So how do we run code as close as possible to the browser so you get these very rich, engaging applications? But one of the things that we've been focused on and has been one of our design goals since the beginning is how do we write JavaScript and TypeScript in a way that you can run it on the client or the server? And so just last week, we announced new support has landed in our CLI that makes this process easier so that you can run your applications on the server and then bootstrap a client-side application on top of that. But why is that important? Sure, it's important for a few different reasons. So you want to run applications sometimes on the server first because there's a lot of computers that are processing the web and browsing the web across the internet. So there's search engines, there's things like Facebook and Twitter, which are scraping websites, looking for metadata, looking for thumbnails and other sorts of content. But then also there's a human aspect where by rendering things on the server you can actually have an increased perception of your load time. So things look like they're loading faster. While you can still then on top of that deliver a very rich, engaging client-side experience with animations and transitions and all those sorts of things. So that's interesting. Before we got started, you talked about kind of thinking of the world in terms of the user experience at the end of the line versus thinking of it from the server. I thought you were going down kind of a server optimization, power, when you say think about the server, those types of things. But you're talking about a whole different set of reasons to think about the server and the way that that connects to the rest of the web. Yes, there's a lot of consumers of content that we don't necessarily think about when we're building applications. We normally think about the human side of things, but having an application whether it's a single page application or whatever that is also well optimized for servers can be very helpful. Yeah, that's pretty... Servers as the consumers. Servers as the consumers. I guess it makes sense, right? Because Google's indexes and all the other ones are crawling servers. They're not scraping web pages. Hopefully, I assume we're past that stage. All right, good. So what else is going on in terms of the Angular community that you're working on next? Sure, sure. So I think we're really just focused on continuing to make things easier, smaller and faster to use. So those are kind of the three focus points that we've got as we continue to invest and evolve in the platform. So how do we make it easier for new developers to come into the kind of Angular platform and take advantage of all we have to offer? How do we make smaller bundles so that the experience is faster for users? Right, right. And then how do we make all these things understandable and digestible for developers? It's like the Bionic Man never went away, right? It's still better, stronger, faster. Yeah, exactly. All right, well Steve, thanks for taking a few minutes out of your day and sharing your story with us. Thanks so much for having me. Absolutely. Stephen Fluent from Google. I'm Jeff Frick. You're watching theCUBE. Thanks for watching. We'll catch you next time. Take care.