 So hi, I'm Nathan. I'm gonna talk to you. My by the way, I'm Nathan. I'm not Steph Steph was supposed to be here. Steph is not feeling well. So now I am subbing in. I am not giving his presentation This is a very different presentation. I'm gonna talk about the business value propositions of Ember have you ever sat in a room and said, you know That guy should be using Ember and here's why It's sometimes an interesting and complicated cell You're like, I could make all of these wonderful technical arguments But the technical arguments don't mean to damn except for that one guy over there in the corner And he's not gonna make the decision So let's talk about how to sell Ember about what we see as the value propositions of Ember and I think that one of the most important things of the Ember community is it gives us an Opportunity to move together and so what you see here is our tomsers from all sorts of walks of life We've got Boston. We've got I Don't know what all of these are anymore. I think one of them's Houston one of them's Austin. Yeah, so What we have that gives us that ability to move together as a crowd is Ember CLI Ember CLI is actually built on top of multiple mistakes And we finally learned how to build something that was so awesome that everybody else is forking and knocking it off So this is the thing which really ties everything in the community together and everybody's like, oh, yeah, Ember CLI. It's a build tool It's not a build tool Ember CLI is so much more than a build tool How many people in this room feel like they are qualified to actually design and architect a piece of software? I'm not raising my hand if that gives you any hints We've got a team of people however who work on Ember CLI whose job it is to think about this and Together we come up with solutions that we're happy with and if that's what happens We can work together and build blueprints build a strategy build a pattern that says hey This is how you should build an Ember application and all you do is you type Ember new my application name Done you no longer have to think about how to pull all of the pieces together whether you're going to use mocha or q-unit whether you're going to I have webpack or broccoli or Roll up or all of these decisions. Who cares? Really who cares about these decisions. That's not a Fundamental part of delivering delivering business value to our end users We're building an application that's supposed to do something. It's supposed to make it possible for you to bring food Into your company. It's supposed to make it possible for you to send a volunteer a Very small town in Africa to somebody who lives in rural Africa using hospital run our end goal is not the tools It's building an application and so Ember CLI is a Rocket ship if you will it's an opportunity to really speed that up and so it gives us an opportunity to Also provide our build trip reference this we do not want artisanal builds Artisanal builds are a problem every time you do something custom It makes it really hard for you to maintain because it's going to be you because you're the only one who built it and That's going to land on your shoulders and six months later Hey, why is this not working in that lands right on you? We have lib broccoli Ember app I have my own complaints about it, but it makes it possible for you to get ECMAScript 6 JavaScript modern modules everything out of the box. You don't have to think about it handles concatenation It handles all of the bundling for you You don't have to worry about these decisions. These are not part of delivering business value So instead you have a build and all you have to do is type Ember build But that's not all Ember CLI is also development server You know what sucks all of these tools that you need in order to make your developers productive Developer productivity is incredibly important for your company to make sure that they are able to get The actual product that they want But if they have to pull teeth to get there and instead they've got a development server that oh Sometimes it comes up. Sometimes it doesn't That kind of sucks you want it to be consistent. You want it to be fast. You want to know that it supports SSL You want to know that it has service workers set up right out of the box You don't want to have to solve all of these problems yourself because it's not important for delivering your business value but tests are Turns out you write tests your application actually will be stable and Ember CLI bundles an entire testing solution for you and you don't have to worry about it and the best part about this entire System is that when you run a generator you type ember g component ember generate component All of a sudden you have a component that's generated a test that's generated template that's generated You don't have to think about it. All you have to do is go in and fill in the test contents That allows you to quickly and easily make sure that the application is doing what you want and is actually able to deliver on the Value that you said you were going to provide Now beyond that How many of you have ever built an application that six months later. Oh Yeah, I'd like to upgrade the version of jQuery But I've got this dependency and I forked it here and I patched it there and I can't upgrade it anymore That was only after six months. Imagine what happens if you have to maintain that application for a year and a half or Three years or let's say you're linked in and you have to maintain it forever Forking your application from the other thing and now you have what we have Internally at linkedin called linkedin backbone Whoops Or worse we're like hey We're going to adopt the dust templating language and eventually the dust templating language becomes ours and we own it You don't want to own your framework You want it to be something that is owned by the community? Collectively because that's what gives you business value if you have to carry all of the weight all of the load on your own It's not fun So ember gives us an upgrade path we have every six weeks a new release We have betas that come out every single week You're able to quickly and easily move from the older version to the newer version In fact, all you have to do is walk into your project and type ember and it Done now you have the most recent versions of ember ember data and ember CLI That allows you to deliver your business value without a ton of work on the infrastructure side Infrastructure is always neglected At every company you have ever worked at and if it hasn't talked to me I want to know where that is because I want to work there so and that's actually a Totally vacuous threat because I know for sure every single one of your companies under invests in infrastructure So I've been burying the lead a little bit ember CLI is awesome But even more awesome than ember CLI is the add-on community which it enables add-ons are Fantastic, it means that you don't have to build your own calendar widget. How many of you have built a calendar widget? How many of you have built multiple calendar widgets? How many of those calendar widgets? We're so custom and so valuable to your company that it was worth paying you ten or so thousand dollars to build I don't think so, but somebody has actually gone through the effort gone through the trouble solved all of that we have ember power calendar and You don't have to think about it. All you had to do is type ember install and And then whatever you needed moment calendar Selects styling selects is literally the worst All of these things you don't have to worry about And so it's very gracefully summed up by Tom Dale in his lovely tweet here We have all of these complicated problems We explain all of these complicated problems and you get up here and it's like here's how ember engines work Thanks, Trent But you don't have to worry about it if you want lazy loading engines all you have to do is set lazy loading to true Because combined community solutions Allow us to move together And so that's what I'm looking at. We have ember engines. We've worked on it for a long time In fact, I'd say we've worked on it for about six months at this point and Now that we've reached the end of that road we've had all of this effort and The adoption for everybody else is Presentable in 25 minutes you don't have to go through all of that work all of your isolation Will just come out of the box with ember. This is how we work together as a community So it was an isolation primitive at first. It didn't actually do anything We started this effort in November of last year. We're like, yeah, eventually we'll get the lazy loading at some point So you're just sitting over there on an island doing nothing and then eventually we get there we get there with 0.4 point zero coming out like any moment now and This is the big tempo feature that you've all been waiting for and you get it without having to do a ton of work Let's say you want to handle server-side rendering You know, what's a lot of fun. I Absolutely love opening up a debugger in node. I just love pressing C enter repel enter Whatever the value I wanted to look at enter And it's just a terrible command line interface and if you've been using this terrible command line interface You should probably check out visual studio code because it makes your life so much better end of sales pitch, but fast boot All of this is a ton of work But you get it by typing ember install fast boot That's it. There's nothing else you have to do We allow the community to move together to accomplish things together and that is so much the value proposition And you're like wow this guy keeps saying the same damn thing. He's gonna show me something else and sure enough Let's say accessibility is something that you care about as a company Let's say you work in government spaces and you need a quick and easy way to make sure that your application is accessible All you have to do is type ember install ember a11 y and you're done so the Conventions the configurations that we have all worked together to define the architecture that we have used and come up with together allows us to Build something that we all get to use and that we all get to benefit from and so not only that we have a Lot of tooling that we've built in the community to make this palatable for everybody to get to use For everybody to get to build We've been around forever Sprout core which we come out of started in like 2008 We are the grandfather if you will of all of the front-end JavaScript frameworks and in September of 2013 we We're so confident and a little crazy. We're like, you know what we're gonna do We're gonna release a JavaScript framework every six weeks and we've done it consistently since September 2013 and so we've done that so well that we now actually have added in a long-term support story. We're the only JavaScript framework with a long-term support story. So, you know, it's really important for your business to be able to actually plan and understand when to Expect an upgrade so you can either do it every six weeks if you need to stay on the cutting edge of technology Or you know every four releases will be a Long-term stable and you can move from one to the next to the next And so we've added more and we have a schedule You can look it up on the Internet's and it tells you exactly when every single version is going to come and how long it's going to be supported for and That was in addition to our model just in April of this year We're a community-driven framework. We're not run by a single company We have a lot of people who happen to work at LinkedIn, but we also have people who work all over the community we've built something that allows us all to share and We have a governance model that allows us to actually achieve that and one of those Main Temp polls to it is our RFC process If you want to change something at Ember you can go write out what you want the change to be you can be the change You want to see Sorry had to go there Once you write your RFC you publish it you get feedback you get people involved you say hey This is what we are wanting. This is what we are trying to accomplish and once you've got all of these Together and we can review it and identify what the best possible solution is for the community and Then it shows up eventually inside of Ember itself That's not driven by an individual is not driven by a company. It's driven by a community That wants to build something great Ember happens to have an open-source initiative Approved license, which is really important. It is MIT and there's nothing clever about it It literally just says copyright Ember and contributors The MIT license allows everybody to use Ember everybody to benefit from Ember. This is a No risk license. It's been used everywhere. We've got a security story Turns out writing code is hard We make mistakes collectively In the background there. You can see our actual PGP. I Block this is what you can use to encrypt to send messages. You don't need to download it off of my slide I promise you can find it on the internet at emberjs.com slash security Having a security policy allows us as a community to make sure that we are able to solve our problems in a Responsible way make sure that we are able to communicate to your company You depend on ember and if you have a security vulnerability in your application It's important for us to be able to reach out to you and say hey here are the problems you're going to encounter and Here's how you can fix them. We have all of these releases So every time there's a security issue every supported version of ember gets a Patch release all you have to do is change a version number and redeploy the security story is Solid we've had only one issue. I believe in the last three years Ever since we moved off of HTML bars and or excuse me off of handlebars and into HTML bars so The trick of ember is we want to work smarter not harder We can build our own Artisanal framework with our own custom view layer our own custom build system our own custom data layer wired all together with our own specs of glue and hope that the duct tape and the string and the prayers all hold it together and work or Together we can build something that we all use That not one of us has to maintain and instead something that we can Rely on as our foundation that will continue to provide for us so Ember I love ember. I'm a little biased if you couldn't tell I Got an amen We want The experience of using ember to be fantastic We want to be able to deliver the products that you want to build using ember quickly and very I to a very high quality and That is what I believe embers value prop is Don't worry about the details worry about your product and Ember will be there underneath the hood and you don't have to think about it So ember work smarter not harder Thank you so much Anybody have questions you can find me afterward Mr. Showers. Yes. Thank you, Nathan Another round of applause for everybody that spoke tonight Transventing anything