Okay, story time. When I first heard of GitLab, we had just finished integration with GitHub, and a customer said they wanted to just integrate with GitLab too, and I was like, GitLab, what's that? I took a look at the website and was like, eww, that's an ugly knockoff of GitHub. No thanks. And then I promptly forgot about GitLab. A couple of years later, a product manager that worked for me was excited about this competitor called GitLab. GitLab's got CI now, and their roadmap is public. I didn't really understand what he was excited about, but he was kind of irrationally excited about GitLab. I still ignored it. Within a few months, this PM had raved about GitLab so many times, I figured it deserved a look. So I started digging around, and I was like, damn, GitLab, you grew up.  First off, it actually looked nice. It had more features than GitHub. Wait, what happened here? Oh, I see. You joined Y Combinator. There's a real company behind it now, and they're crushing it, growing incredibly fast. What the heck? And then, of course, I found the company Hembook.  It was only a fraction of the size it is now, but even then, the mission, the values, the roadmap, it was all out there in the open. Oh, and it was a remote-first company. It became a remote later, a bit later on, but it was still at that point. The headquarters actually had maybe three people working in it. But even though I lived in the Bay Area, I hated commuting into San Francisco. So I reached out to Yob and had a chat with Sid and realized that not only was the company already doing well, there's even more ambition behind it. So I started opening up about all the things I wanted to do in the developer space. And Sid and I were so shockingly on the same page. Everything I had wanted to do in previous companies but ran into a wall. While at GitLab, there was no wall. It wasn't confined to source code management. It already had strong CI and was poised to head straight into CD. So spoiler alert, I joined the company. Sid, to his credit, told me to take it easy for the first few weeks and get to know the team. Just absorb, soak it all in. But after about two weeks, I had written up a complete vision for CI-CD at GitLab, telling every one of the things that I'd ever dreamed of doing before. But for the first time, seeing that maybe, just maybe, this company would pull it off. So we implemented environments, and deployments, and pipelines, and slowly worked through the vision picking off major chunks of the developer workflow. Well, I say slowly, but that's a lie. We were knocking out major features at a furious pace, iterating faster than I knew possible, and I was proud of my previous teams and their abilities to iterate, but this was different. Things that another company might take a year to even start, we were kicking out in months. It was awesome. I'm so proud of what the team accomplished. Then about a year ago, we had covered so much of this vision for CI-CD. We were starting to run into another wall. See, I had always thought that as a developer, you really needed to cover this entire workflow from idea to production, and once it's in production, you'd keep watch on it in case any code changes caused a production problem. But true operations, well, that was on the other side of the wall. We were only making things for developers. It was a developer tool. Operations is clearly a separate thing. Or is it? Maybe this wall isn't a wall at all. Maybe it's imaginary, and just like Neo swallowing the red pill, my eyes opened and I saw that there was no wall, and with that, GitLab was moving into DevOps. Then a month or two, Sid and I and others had crafted a vision for 2018 where GitLab goes beyond dev into DevOps, but not just any DevOps, complete DevOps, where we cover every important part of the software development lifecycle with a single application. Because did I mention GitLab is ambitious? To cover something this big, we knew we'd have to go seriously into breadth over depth territory. For a user experience-minded PM, this is uncomfortable, shipping a lot of MVCs or minimum viable changes that amount to a foundation or base, or scaffolding, if you will. They're pretty bare boned. But by getting the entire vision out there, people would understand internally and externally. Everyone would know where we're going, and the community can help flesh out the rest. And the thing is, it's working. It's really resonating with prospects. When they hear our vision, customers' eyes light up. They love our vision. Sometimes they're skeptical, but they want it to come true. This product, this entire scope of complete DevOps, this is what I've always wanted as a developer. I didn't want to have to make it, but I wanted it to exist. But no other company could do this.  They all put up imaginary walls. At GitLab, there is no wall. Of course we can do this, so we have an obligation to do this. This product needs to exist. Many people could have done it, but we're the only ones willing to accept the low level of shame inherent in iterating so quickly.  There is no wall. We tore down the wall between version control and CI. We're tearing down the walls between Dev and Ops. As a side note, at one point, Sid said, not to worry, we'll get complete DevOps out there, and then we can take time to build in the depth. I replied, yeah, right. We'll do DevSecOps and add even more scope. Well, that turned out not to be true. He didn't wait until next year. Within two months, Sid realized security was important, and pretty soon we were really going after Dev and Ops and Biz and Sec. So if you think there is a magic wall around DevOps, think again. There is no wall. Who's next? Designers, product managers, executives? Yeah, they're all fair game. Remember, our mission is everyone can contribute. We're building on strengths and going through an ever-expanding software development lifecycle, but there are no limits. There is no wall. And the funny thing is about imaginary walls is that once you're on the other side, you wonder what you were afraid of. There is no wall.


Welcome folks, this is Tom O'Brien of TFNN. We got five days a week, we got seven hours a day, we go 24 hours a day on the internet at TFNN.com. Always remember folks, whatever you think about, you bring about whatever. You focus on growth so everyone's having a great day, safe day, let's make it a great night folks. Kicking into May, pretty wild. Serve the one you love.  And every kiss and every touch, you feel you're there to please the one you love without expecting anything back. Mugger to eyes, let's take a look at it out here. We have the Dow Industrial's up 718, Nasdaq's up 433, S&P's up 117. Gold contract up $6.10, trading at $18.94 an ounce. You got Silver down to $0.28, $23.17 an ounce. Lightsweak crude up 343, 105, 44, a barrel, notes and bonds. The 10-year note, down 11 ticks, trading at 119.14, the 30-year off six at 140, 111, and King dollar. King dollar's up 638 ticks, trading out at 103.589. The euro is at 105, the yen is at 130.88, and the British pound is at 124 to one US dollar. iPhone number's 877, 9276648, give us a call folks. Want to know what's going on in your world? In the world of the S&P's, let's take a look at them. What do you have? Okay, so you got a big bounce here. There's no two ways about that, man. Percentage-wise, this is a decent bounce. You got percentage-wise, what we have here is that you got the Dow, Nasdaq rather up 3.4%, 2.7 on the Nasdaq, 2.1 in the Dow Industrial's. That being said, you take a look at the spy. You get 71 million shares, bottom line. You come into 132. Now the way this is set up, there's no reason to kind of go back to ICE, okay? So you came down with, here's the bearish pot. The bearish pot is it didn't get to the bottom of the test. The test is 410. You can see that bar sticking out there. It's a monster bar. We got to 416. So my take is what you'll see out here tomorrow. You get over the highs. We'll see if they can hold. You're gonna have lighter volume. Once again, you have lighter volume now, but you get lighter volume tomorrow, and we'll see if it holds price. If it does hold price, then you can get to ICE. ICE would be 436. Right now you're 429, and as you get up to that point, you'd probably come up and you'd have a contraction of volume simultaneously when that's happening. What is intriguing, no doubt, is that we are coming into window dressing, so there's gonna be plenty of funds that, you know, bottom line, we'll put money into the marketplace. End of the month, beginning of the month. NDX 100, same type of setup. The difference in the NDX has been the weakest. Still the weakest out here in a big way. So what we have here is that you got, you're up 12 bucks right now. What the NDX did do, that is the one that broke the swing high, the swing lows. Let me put this on a weekly for a second, because I want to see this on a weekly. Okay, so on a weekly, first low, going back to the week of the 25th of February is 381. The second low is 414. This low, yeah, okay, cool. So what you're gonna have here is this. If you're watching Tiger TV and you're watching my screen, this low here is gonna have heavier volume than the last low we had. That says we can back down. That's how it, because what you're going against here is the low that was established at 297, and that had 444 million. So bottom line, first one, as I said, had 381. Second one had 414. Right now, with one more day left, we are at 394, so that's gonna commit her to about four, might commit a five. Yeah, might commit 500. So, well, you get the gist of it. Well, let's do this in the spy, too. Okay, so I take the spy, put this. This didn't hit the bottom, but I just want to see how these volume calculations are coming in. Okay, so in the spy, the volume we're going after is 593. We're at 417. That's gonna be lighter volume. That's gonna be lighter volume. There's no doubt about that. Just didn't get to it. We'll see how that baby shakes out, and after the close out here today, and we'll go over, we're gonna have Amazon, we're gonna have Apple. Let's go into the gold contract first. So gold contract, bottom line, went all the way back to where it broke out from. You didn't get a rejection of lower price. If you're just getting your head wrapped around technical analysis, folks, these are pretty cool charts to look at, because they don't set up this clean a lot of the time, and you get to see, this was so clean, it's insane, actually. You broke topside, you were trying to break the 1883. We got up there a couple times, then when you did break it, we went from 1873 to 1906, and that's what it just did. It came all the way back to that level, and bottom line, we'll see if we can get some juice. The rate, oh, this is good, it just got back inside 1893, because that's where it broke down from, okay? So now you're back in a higher range inside of the gold contract. Now the hard thing to comprehend, and I've been in this gold market since heavily, since 2000, is gold being this high, and the dollar bottom line being this high. This looks to me, so check this out. I mean, this is pretty intense, even what I'm saying, because I'm still a gold bull, but it looks to me, man, that this dollar is actually gonna break higher. That's what it looks like. I mean, when I take a look at this, it's not gonna take much. Actually, I gotta put it back further. So watch this, I gotta put this back 30 years to get some clarity about where we are. Now, the intriguing part is that, you can see that you're set up. It hasn't got a decisive break yet. I talk about this a lot. When you break topside or downtown, you gotta get away from the break. But I guess, well, if you break topside, man, bottom line, game is 2,000 highs in the dollar, which is 121. That's a long way up. We'll see how it shakes out. With gold hold, well, yeah, let's go over to the end, because we go over to the end also. Now, you can see that the Central Bank of Japan couldn't handle the yen. They claimed when they came out, what it was all the way down here, down with the 30th of March, they came out and said they wouldn't let it go by 130. Well, go look what happened, folks, it's 130.91. It went to 131 today. Now, let's bring this back and put that on 30 year. Oh, this is a big break, too. We broke that. Yeah, so the yen needs more to go higher, meaning it gets weaker against the US dollar. Stay right there, folks, come right back.


Hello. Welcome to WorkerEye's JavaScript Made Easy. So my name is Ben Morse. I'm a developer advocate at Google. My job there is to help the web be more beautiful and faster and easier for both developers and for users. Really easier for developers to make good experiences for users. I used to be a musician, which makes me especially sad that I can't be here in Austin today. I was looking forward very much to being in Austin, it's a great city. I used to go a lot for South by Southwest and has great music, barbecue and so on and so forth. Here I am instead in New Jersey. But hey, let's travel. My dog is over here. It's comfortable. So there's always that. Anyway, if you're here at this conference, you're probably a big fan of JavaScript. Why shouldn't you be? I mean, JavaScript is awesome. It does all kinds of incredible things. It's blossomed in the last years from this little thing to make small button changes and little things on web pages, to the full featured programming language ecosystem environment with lots of wonderful libraries and frameworks and features that are great. The thing is though, it's possible to have too much of a good thing. This actually is a screenshot from a Chrome Dev tools of a site owned by Google. If you have a lot of JavaScript, your wonderful site may load slowly for many people and also may execute slowly. So things on your page may not work sometimes because you've got lots of JavaScript running and things can happen in the browser. If you've got a nice device and you're on a nice connection, then it may not be quite as important. But for a lot of people in the world, this matters a lot. I mean, for me, for example, if I wanna train somewhere, trying to go somewhere, some sites that you try to load up don't work at all. Some sites do work, some sites don't. And people across the world may not have like a nice new iPhone, a nice new Galaxy phone or a Pixel or something. They could have a lower powered phone, which is quite likely. They may be also on worse connections. And in fact, last time I saw actually 40% of connections worldwide, mobile connections, were 2G connections. 2G is not how you can load a complicated JavaScript filled website. I mean, a lot of the problems are large images, other kinds of things can be problems, but we're gonna discuss JavaScript today. That's why certain people around the world are trying to look at your site and instead they're getting frustrated. So this is not good. Let's focus on the JavaScript side of things. What can we do as JavaScript developers to make these sites load faster and be functional more quickly? One thing, of course, is shiplash JavaScript. Okay, great, how do we do that? Well, you can minify and gzip our code, of course. You're probably already doing both these things, but people don't always minify, don't always gzip, send less code over the wire, at least it will load up more quickly. Also, of course, code that isn't being used shouldn't be on your page. It happens a lot because you have code for all of your site, which you put on all your pages on your site, but in fact, that makes things just slower for the user. You can also go through the code coverage tool of Chrome and realizing that I'm missing an S and unnecessary. Yeah, so that was necessary, but it's not there. Anyway, that S was necessary, it should have been included, but don't have to assure you, if you have extra code, don't include it on your pages. Also, if you're using frameworks or using various kinds of ways to move code and merge it together, reduce your bundle sizes, make those more efficient. If there are dependencies that shouldn't be there, get rid of those things, that all helps.  Or of course, you can use AMP, which you know I talk about AMP quite a bit. AMP is a way to use less JavaScript and make pages load faster in general. So there's all those things. None of those really deal with the problem though of making things, making interactions happen more efficiently. Like JavaScript can be running and it can be blocking the browser from doing things. Long tasks can make things not able to happen. There's a way to get around this, which is web workers, because the web is single threaded, but web workers run in another thread. So you can offload code that is gonna take a while to run into a different thread via a web worker. Kinda neat, right? That way your code is running over here in a different thread, and your other code can keep on handling events, the browser can keep on doing things. But what is this about the thread thing? Why is the web single threaded? I mean, every modern OS is multi-threaded and multi-tasks. Why can't the web do this? Well, part of it is that it's just how browsers in JavaScript were created, how they've always been. Now, of course, modern browsers multi-task. You can run various tabs. They can be loading files while doing various other kinds of things and painting the screen, but the thing is that each browser tab has a single thread for the UI, which means only one process can make changes to the screen at a time. So JavaScript can block the browser from doing things and vice versa. Imagine it wasn't that way. Imagine if you just allow JavaScript tasks to run simultaneously. They can all modify the DOM at the same time, and while the browser's laying out and painting the screen, this task is modifying the DOM, this task is modifying the DOM, you'd have race conditions and general chaos. It would not work. It's confusing though, because as we know, JavaScript is asynchronous. JavaScript depends on events getting fired as async. So doesn't it, isn't it the kind of thing where as soon as an event fires, code executes immediately? Well, it's not actually how it really works. Remember that all the code on a single webpage runs in a single thread. There's a thing called the event loop. Let's look at this diagram here, rather not diagram animation. Anybody take Archibald, which I borrowed for this case over here. This is a simplified version of JavaScript's event loop. So the browser fires an event, right? If there's an event handler for that thing, that could run until it's done. As other events fire, they get added to a queue. So we're gonna see over here these tasks move into the loop there they are, it gets handled, another task is being queued up, and event loop handles that one next, all well and good. So really, if this works out nicely, the browser's able to get the tasks pretty quickly and there aren't delays. However, if a long task happens, it has to wait for that task to finish. Nothing else can happen until that task completes. So the next bit of code will be delayed. This also means the browser may be blocked from doing things in the UI. You may be blocking the browser from entering things into a form, you may be blocking scrolling from happening, animations might get janky, and of course if the person taps on something else, while your code is still running, that event can't get handled until your code finishes running because it's all one event loop, it's all one thread. So that can be a problem, you can get this case where there's traffic holding up the entire thing happening in the DOM. We wanna avoid this happening. Not only do you have JavaScript causing pages to load slowly sometimes, but it makes this unresponsive screen where you can't swipe, you can't do things, users don't like that sort of thing. So one solution for this is to use web workers. Web workers are special because JavaScript in a web worker runs in its own thread, which is nice. Web workers have been around for quite a long time, actually about 10 years. So why don't they use more? I think because their limits make them harder to use. The thing is, workers can't cause those race conditions in the DOM and can't get in the way of other kinds of things because they lack access to the DOM, they also lack access to the global scope. They can't modify variables that are in the global scope. So they're limited. You can kind of pass them things and they can then send messages back. That's how they work. They work by passing messages back and forth. So web workers can pass messages to the main thread, which can pass messages back to the web workers. That's about it. Now that's kind of complicated. There are libraries that make this easier like a com link by Surma and workerized by Jason Miller, but even with those libraries, workers can't access the DOM. They're stuck in this little DOM area over here where they can't get near the DOM. That's a big obstacle. Fortunately, there's a new library called Worker DOM. This was released by the AMP project a couple of years ago. Worker DOM works in the following way. It makes a copy of the DOM the worker can use. And Worker DOM also recreates in its own JavaScript a subset of the standard DOM API so the worker can manipulate the DOM and make changes on the page using standard DOM methods and properties. It looks sort of like this. There is a copy of the DOM, if you will, a virtual DOM which Worker DOM creates and there's a real DOM. And the Worker DOM creates the two DOMs, a lot of DOMs here, sorry. Worker DOM keeps the real DOM and the virtual DOM in sync. So when a change is made in the real DOM, Worker DOM detects that. It diffs it and detects it and sends a message over to the worker telling it to go ahead and make the same change in the copy. If your worker's code changes its copy, Worker DOM recognizes that mutation and sends a message over to the real DOM making the same change over there. It's a little bit of overhead, but it's actually pretty fast. Here's how it kind of looks. Worker DOM handles mutations in this way. It does a diffing of the virtual DOM and the actual DOM which sounds kind of like other frameworks we've used before. An efficient diffing mechanism figures out what changes and then it encodes those changes into an array buffer, a very compact way of sending a message over to the other thread that has to make the change and then passes it over. Here's an example of that. So for example, this kind of standard looking thing here, document create element div gets represented in the following way as this very compact looking series of numbers. The first number there represents the reference to the node which this div here will be always index number three. The second number tells the main thread what kind of DOM mode is being created. Element mode happens to be number one. Then the node name of div corresponds to six and so on and so forth. So any kind of mutation gets encoded into a small bit of numbers. That's why this message passing actually isn't that slow. I think SIRMA actually has a whole blog post about this where he discusses how it can be pretty fast. He does some measurements about this.  You might be telling yourself, okay, so I can try this thing out, this worker thing, but how do I use it? Do I have to build this myself? How do I use this whole worker DOM thing? Well, the good thing is there's an easy way from the framework that wants to make things easy for developers and advanced web features accessible to all, which of course is our friend AMP. As you probably already know, was created by Google as an open source project. The goal being to make the web faster and easier to use and just better in general. AMP is now part of the OpenJS family. It's why I'm here today. AMP is now an OpenJS growth project. To you, AMP may just be a way to get into Google's top stories carousel, which has a special place in. If you do that, you may also know that Google has just announced recently that in the near future, any page that meets new standards for speed and for a stable layout, which are called web vitals, any page that meets these standards will now be eligible to be in the top stories carousel, not just AMP pages. In fact, AMP pages that are slow or unstable won't get in there anymore. This is not true now, but this will be happening in the very near future. So you may have thought of AMP in various kinds of ways, but probably not as a way to make developers' lives easier. That, in fact, is why I'm interested in AMP because it makes things easier for developers for common and basic tasks. What is AMP? It's basically a web components library. So HTML was created about 30 years ago and it was a document description language. So there's things like, hey, this is boldface. Hey, this is a paragraph. There weren't things like, hey, this is an interactive menu. Hey, this is an image carousel because those things didn't exist yet. As those things became part of the web, JavaScript grew to the task to make these things happen, to make interactions happen. HTML couldn't do those things, which means that people ended up adding a lot of code to their site, which isn't always necessary. So AMP aims to make this better by using web components to add new tags to HTML that do those kinds of things that HTML didn't do before. You see some examples over here in this large list of colorful looking names, things like a flying carpet effect, a Facebook comments component, the AMP carousel component, all kinds of things. I think I see a Hulu player over there. All of these tags here work because they're web components that are run by small bits of JavaScript that AMP uses. I'm in contrast, AMP discourages you from writing your own JavaScript because that can make things slow. That was the idea of AMP. It's now allowing more JavaScript to be written as we'll soon see. Before we see that though, here's how AMP looks in practice. This is simply how you do YouTube embed in AMP instead of embedding YouTube's own JavaScript, use a component called AMP YouTube, specify a layout type. AMP has various layouts, including responsive, which is its way of automatically making the YouTube video or any component shrink if it's container shrinks or expand if the container expands. And the width and height are specified in advance. That's because AMP wants to prevent things from shifting around on the screen and wants to prevent content layout shift. So it creates a space for everything in advance. And then as things load up, they pop into their space, things that move around, the browser isn't repainting the screen, recalculating the layout, things are just faster and more stable. And finally here, we have data video ID, simply the ID of the video, the YouTube video. And then you just do this and there's your YouTube video all done. So I was saying before, worker DOM, amp makes this possible to use through a component called AMP Script. AMP Script is kind of a wrapper around worker DOM which brings it into AMP, makes it pretty easy to use. How does this look? Let's try a simple hello world example over here. So hello world, let's see. In the body, we're gonna insert this AMP Script component over here. This is just another component in AMP. It's got layout type equals fixed because we'll see why later. We give it the name of a script, we give it the size of the components because as we know in AMP, all things have their size declared in advance and it consists of the word hello instead of h1 tag. Now what AMP Scripts will do is pass the stuff inside the AMP Script component, the children to the worker as the entire DOM. So the whole DOM the worker sees is just the h1 tag. Then we have the script over here which simply grabs h1 tag and it pens a comma a space in the word world and there you are. Notice that we have type equals text plain instead of text JavaScript. This is so the browser doesn't see this as a script and execute it. Instead it's just plain text, AMP Script can grab it and give it to worker DOM to use. There's that. And let's see if we can get this thing to actually work. I think that's the next thing over here. All right, I'm gonna make a new tab over here and I'm going to enter over here the URL of my little demo. That's actually not what it is. It's actually supposed to be this AMP Scripts. Getting closer now. Thank you auto completion for almost being there. This is it. Hello world, okay. Hey, I'm clapping for myself because no one else is here but me and my dog. Hello world. So what did that actually do? Can you see that actually worked? You can't tell what it actually did. Let's look over here at the console either at the sources. We can see here at the bottom of the sources and DevTools, this little extra thing, this thing over here. And there is this little bit of JavaScript. And the top over here, let's make this a little bigger. I said get a little bigger. Thank you very much. The top over here is worker DOM stuff and the bottom is our JavaScript. So there it is. We actually managed to inside a worker add this little world thing over here. There you go. That worked. It wasn't gonna be that exciting. So by the way, this is a little more of the page it can go in. So this is more of the AMP page this would be part of. Notice that the first thing we do over here is we load up AMP so in runtime, which makes AMP possible. I also load up the bit of JavaScript that encapsulates worker DOM that makes AMP script work. So you can also put this JavaScript into a different file instead of putting it in line. In this case, we've just stuck the JavaScript into a different file called helloworld.js and pointed the source attribute of AMP script to that file. There we are. A more glamorous example here is an event handler. So we've added a button to our HTML over here, this button that says hello who and added some more JavaScript that adds an event listener to the button where if it's clicked, it adds the famous comma in world. Let's try this out over here. I think this is called hello button which I named very, very cleverly and let's make this a little, whoops, that's not what I wanted to do. There we go, okay, make that a little smaller and hello who, look at this, hello world and more worlds and more worlds. Now the document we use over there, a document object is not the same as the one you usually see. Let's add a break point over here and run this thing again. Run it again, okay, let's go to the button. Notice a document over here is not the usual document. It contains the things that you wouldn't usually see. Look at this, a seven, an eight, a nine, some arrays, a T, some more things over here. This is because this document object is not the one the DOM provides, the browser provides, it's created by worker DOM and worker DOM gives you all these things to simulate a DOM. Kind of interesting, kind of neat, that's how it works. So there's that, there is that JavaScript over there. Okay, and you can do more in a worker. Workers actually natively support fetch, XMLHTTP requests, web sockets, canvas, all kinds of features like that. Here's a fetch version, let's try that one. So again, we just have a fetch instead of having the thing just stuck in there. You click on the button and then you fetch it. Let's go over here and see how that works. So here's hello fetch. Actually let's go over here to the network tab and see if we can watch this being added. So there's what's added over there. We're gonna click hello who and notice hello text was grabbed over there and it contains the incredible payload of comma world. There it is. All these things are not so complicated and a way to get JavaScript into a worker, which is kind of neat. Remember though, this is actually not again the real document API. Remember that worker DOM has gone and recreated these things with its own JavaScript. Here's an example over here. I've got elements by name. This is the code that worker DOM itself uses to get elements by name. So all that is true. The thing is that you can't really have worker DOM reproduce the entire DOM API because it is absolutely enormous. Sorry about this cut here in the video. My dog got bored and went downstairs and was stuck inside the downstairs area. I couldn't get out and there was some general chaos for a little while, but now we're back. So I think I was talking about where we were over here. I think we're somewhere over here in the previous slide. There we are that worker DOM recreates these APIs with its own JavaScript. It doesn't recreate the whole DOM API because it just couldn't do that. So there is this handy web compatibility table over here, which you can find at go.amp.dev slash amp script APIs. This provides a list of APIs that are and are not supported. So you can go through your JavaScript and if things aren't supported, replace them with equivalent APIs that are supported. There are also a couple of limits that amp script places in there so you don't violate web vitals principles, don't have things loading slowly, and then have layout shifting around on the screen. One of those things is amp script doesn't allow more than 150K total JavaScript per page. If there were use cases that required more than that, the team would consider raising the limit, but so far no one's really complained about it because it's usually used for the tasks amp doesn't really do out of the box. You just want to change something here and there to add some kind of functionality. The other thing is that it wants to restrict intrusive mutations. So if your amp script tries to make changes before user action that will make the screen move around too much, it will try to block you from doing those things. So you can get around or rather you can make your amp script more capable by taking some simple precautions. Amp script knows that if your layout is a fixed type, then that can't move around too much. Like if the children of your amp script area change size, the whole container won't change size. If the height and width are fixed in HTML, it knows the whole amp script area can't change size. So if those things are true, if the amp script area really is fixed to a certain part of the screen, it says go ahead, make changes over here. If it isn't fixed to a certain part of the screen, it says, you know what, you can't change things all over the place until users take an action to request a change because it would involve a lot of things that would surprise the user in terms of layout shift. It's kind of a more elaborate topic. So to hear more about it, go to amp.dev and read about the actual ways that keeps this safe for you. So again, I was saying before that WorkerDOM has certain APIs. If you wanna not worry about this too much and just go ahead and write your code, have it work out of the box, you might wanna try one of your favorite frameworks. The team that works on WorkerDOM also works on various frameworks and uses them frequently. And they have tried using amp script with things like Vue, React, Angular, Lit HTML, Aurelia. The thing is that these frameworks use a certain specific subset of the DOM API to do their own changes. They do a diff between the virtual DOM and the actual DOM, and then they use certain APIs consistently to make changes. So WorkerDOM supports all of those things well. However, you may find yourself with larger bundle sizes with certain frameworks. So to make your bundle sizes small and to really follow the principles of amp that you should have less JavaScript, no more than you need, and keep things fast for the user, recommend that you use Preact. And Preact, actually one of the people that works on the WorkerDOM team as part of the Preact Core team, he was very careful to make sure that the APIs that Preact uses are well supported within WorkerDOM. So Preact actually is like React, very similar. It's compatible in most ways. You can always transform React into Preact, but it's only 3K minified in GZipped. So out of the box, not much extra JavaScript being added to your project. And actually amp itself is being rewritten with Preact. Amp is being recreated so that all the components will work reliably by themselves, not using the up-run time at all. This is possible usually now, but not guaranteed, but to make it more part of the web, this effort's being undertaken. And it's being undertaken using Preact. So the app team's very invested in Preact. So in the spirit of that, I took my Hello World example and we did it with Preact. It's not that much more complicated. It's just a component and the usual kind of JSX things. Let's now drag this terminal here into our visible window. There it is. Let's build this suspense, suspense, suspense. Suspense, suspense. Let's serve this. Now let's drag this out of the visible area and let's try this over here. It's an embarrassing moment. I can't type anymore. And that's a bit of a problem. Actually, I think it's, I wonder why it's there. Interesting. There we go. And Hello Who. Hello World. There it is. Magical. So Preact works. So that's my discussion here about workerized JavaScript made easier by AMP. If you wanna learn more and try this yourself, we just updated this tutorial here. It's quite nice now. Go to go.amp.dev slash learn script and you can make your own custom UI widget that does some form validation. It guides you along and teaches you about the various things that AMP Script and WorkerDOM do on the way. So look at WorkerDOM's code to get involved in the project. Just go to github.com slash amp project slash workerDOM. And yeah, try it out. We think that workers are a way to make JavaScript more friendly for the user and getting the users way less often. There's various ways to use workers and the way that AMP provides makes it simple to get started. Try it out. If you like it then go from there. Thanks a lot and have a great day.


Hi everyone, Sean with jaspyscasebreaks.com here running a random number block randomizer for 2020-2021 National Treasures basketball pick your team number 14. This random number block includes the Lakers, Kings, Celtics, Pistons and the Magics. 10 spots in the format will randomize random number block works only for the teams in the list here for this pick your team. So every spot will get a random number from the break between zero and nine. If you get number three you'll get all cards for the teams listed these five teams here with three being the first number next to the slash on the left side of the slash. So if the card is 243 out of 299, 1399, 3 out of 25, 43 out of 49, 93 out of 99 and so on the number three with the card all redemption cards will go to the zero spot even if it is a known one-of-one it will still go to the zero spot and any non numbered cards are randomized to the group. So there you go. Here is our list of customers Brian Frank down to Ryan Carrithers with last spot mojo and our numbers from zero through nine dice will randomize both lists and pair them up a five and a six eleven times good luck. Eleventh and final time for Matthew Shearer down to Ryan Carrithers and eleven times on the numbers which are right there. Eleven the final time from seven down from seven down to eight. So eleven times on the numbers, eleven times on the customers and eleven times on the dice. So there is the randomizer. Matthew Shearer with seven Brian Frank three Matthew Shearer six Ivan Lee with nine Matthew Shearer with five Brian S four Brian Smith with two and one Matthew Shearer with zero and Ryan Carrithers with eight. So Matthew Shearer with the zero spot will get any and all redemptions for these five teams including the Lakers Kings Celtics Pistons and the Magic even known one-of-one redemptions while Brian Smith with the one spot will get any and all in person and live one-of-ones for those same five teams and there you guys that was the random number block randomizer for the Lakers Kings Celtics Pistons and the Magics for 2020-2021 National Treasurer's Basketball pick a team number 14 one more random number block to close it out and get it done tonight I'm Sean jaskiescasewrakes.com thanks for hanging out we'll see you next time


Welcome to One Minute Tennis Lessons with The Tennis Mentor. In this video, I'm going to tell you why you shouldn't be recovering to the centre of the court. There will be occasions where you can recover to the centre, but generally you don't want to, and here's why. When playing singles, your aim is to make things as tough as you can for your opponent, and pushing them into the corners of the court can be a good way to do that. If you push your opponent into this corner of the court, their two options are to hit a shot straight down the line, or they could hit the other half of the court hitting an ankle cross-court. Now, your job is to recover to the centre of those two furthest points, which would be slightly off-centre here. The only time you should recover to the middle is if you actually hit the shot straight down the centre of the court. Because if this is the case, your opponent's options to hit the corners are now limited to a more central channel, and the centre point is straight down the middle. So, the only time you should recover to the centre of the court is when you've hit down the centre of the court. Be sure to subscribe to see more.


Alright, it looks like our numbers are slowing down so we're going to go ahead and get started. As you can see on our screen we have a lot of great speakers today. This is the webinar on buildings. This chapter specifically in America's zero carbon action plan. We have Benjamin Prosky from the American Institute of Architects in New York and the Center for architecture who's going to kick us off. Following that we have Professor Jeffrey sex from the president of SDSN and Columbia University, and then Lori care from the LQ policy lab and Roger plat from the US green buildings Council will dive into the specifics of this chapter of following Professor sex, and then we will have a Q&A at the end. Be sure to insert your questions into the Q&A box throughout the entirety of the webinar we will be looking at those and we will ask those at the end. And for those of you who are looking to get a continuing education credits. You can do so using the form that has just been put into the chat, you must attend 75% of the webinar and complete that form to get your continuing education credits. So without further ado now that all the housekeeping is out of the way I'm happy to pass it off to to Ben to get us started. Thank you so much and I'm so pleased that we're collaborating on this and Ben Prosky executive director of AI in New York and the Center for architecture. So if you're not familiar with us as professional association representing and supporting designers and architects through advocacy continuing education and advancing the work in critical areas such as climate action and resilient design. This chapter has close to 6000 members who through over 25 program committees organize educational events workshops and discussions. AI and noise partner organization the Center for architecture focuses on public outreach, reaching beyond the architectural community to all who experienced architecture to educate and activate people to understand how design is a powerful tool, which is the foundation for living, learning, and even more. I want to briefly tell you about a new project that we are about to launch. Now that we are inching past the federal elections, few on November 16 AI and why and the Center for architecture in collaboration with MIT civic data design lab are launching a new project that looks forward to New York City's next mayoral election in 2021 visualize NYC 2021 the project will present a series of questions, studies, and data sets that will help us understand what issues are germane to design and the city and what needs to be addressed by a new administration and city council. We are starting this project a year ahead of these unprecedented city elections, as not only will the mayor and all the borough presidents change, but more than 40 city council seats will turn up. So I invite you to join us via visual eyes NYC net and help us establish design agenda for our next local administration. I also want to make sure that you are aware that in 2018 AI national our parent organization comprising of around 100,000 members across the world actually make climate action one of its top priorities. I was thrilled to serve on the national working group that developed a climate action plan released earlier this year, and the plan asserts that we must declare an urgent climate imperative for climate reduction. We must transform the day to day practice of architects to achieve a zero carbon and equitable resilient and healthy built environment, and we must leverage support for all potential partners, including peers, clients, policymakers and the public. I want to download that full plan at a.org. And I think it's so important, right that architects do declare that they have a role and do declare that they don't have a role only themselves but as part of a larger group. But now I want to introduce our wonderful speakers today. Her FAIA lead AP has extensive experience in urban sustainability policy. She is president of Lori Kerr policy lab and a senior fellow at USGBC and a strategic development fellow at CUNY building performance lab. Formerly as deputy director for green building policy at the New York City mayor's office of long term planning and sustainability under Michael Bloomberg Kerr help develop plan YC New York's influential sustainability plan. And until recently, she served on the AI New York board and is still an active member and our organization advising us on policy and working with our committee in the environment and others. Roger Platt is senior vice president for strategic partnerships and growth at US Green Building Council. He is the immediate past president of USGBC also. In addition to his role advising the CEO on mid to long term strategy matters. He also leads USGBC's lead for cities efforts and business development in New York City region. And in addition to the many impressive positions Roger has held and holds, I am particularly proud that he is a board member at the Center for architecture. But before we hear from these speakers, I am pleased that we will first hear remarks from Professor Jeffrey sacks. I know Jeff needs no introduction for this crowd. But before I pass to him, I first want to personally acknowledge the incredible work he has done as an economist turned climate action leader via his work at Columbia University and the UN and beyond. Jeff devotion to affecting change in a sustainable equitable way globally has elevated his message. In 2017, the Center for architecture was thrilled to honor Jeff at our annual gala. We were so encouraged by Jeff's message at the event, which I just revisited via video, and I quote from Jeff. Jeff, I cannot tell you how many politicians I speak to, who have no idea just how key the work of designers is in helping us live better, all while reducing our impact on the planet. Thank you for being such a wonderful advocate for design and a friend to our community. Jeff. Thank you so much what a wonderful introduction and how great to remember that such kind and exciting occasion together. And all the great work that you do. And indeed, we do live and prosper based on what architects and planners do. And I'm in the Upper West Side right now at home. And we live off of a wonderfully designed grid that was designed more than 200 years ago and laid the foundations for Manhattan. And I'm lucky to be near a central park that enriches lives immeasurably. And so what good urban designers and visionaries do affects our world and our ability to thrive in it. And with 55% of the world and cities today, and that will rise to at least 70 I think even higher than that by mid century. Your work is absolutely essential. And as you're going to hear from Roger and Laurie in just a moment. It's also essential for our most basic challenge of having a safe climate, not only nice places and productive places to live, but because the role of cities in the climate challenge is absolutely huge. The role of the building sector, and the energy used, whether in electrification or direct heating and burning of heating oil or natural gas. The role of transportation. These are fundamental challenges for the safe climate agenda ahead. We started the project to map out a pathway to net zero emissions by mid century. And more than a year ago, bringing together Laurie and Roger and experts from across the country, knowing that we would have an election and and a government and I hope to utterly for a new government and we have a new government now and do president and we are becoming Congress and president elect Biden is very clear that we need to reach net zero emissions by mid century. I think everybody knows where that guideline comes from the Paris climate agreement calls on the world to make all efforts to keep warming below 1.5 degrees Celsius relative to the pre industrial level. We see documented that in order to have a likely chance of success that just means two thirds by the way, we have to decarbonize by mid century latest. And of course, under Trump we were going deliberately from the top in the wrong direction at profound danger to the US and the world. There has been good news in this awful year of COVID there has also been good news politically in that Europe adopted a European Green Deal to reach net zero by 2050. Just in recent weeks, China, at the UN General Assembly, President Xi announced reaching net zero by 2060. It's a big commitment. They're going to even accelerated I believe to 2050. Again, under new Prime Minister Suga and Korea have also announced reaching net zero by 2050. This is all a prelude to cop 26, which will be in Glasgow in November, where all nations of the world including the US as a member of the Paris agreement once again must commit to this trajectory of reaching net zero. Our zero carbon action plan Z cap which you can find online and in the chat you'll find the links to that is the result of collaboration as I said across more than 100 experts across the United States, looking at how the US can do this. Basically, and just within two more minutes, we need to decarbonize the power sector. So to move from coal oil and gas is powered generation primary sources to wind solar hydro as the core of the power generation sector. We need to electrify everything that can be properly electrified including of course like duty vehicles and we need to use the clean power to produce synthetic fuels, green chemistry, for example, hydrogen loop or synthetic methane or synthetic ammonia or other fuel carriers for certain heavy industrial uses, but the name of the game is clean electricity and electrification to a maximum extent, plus some clean fuel carriers gas and liquid made with clean electricity. That's the basic story. We have the time to do it between now and 2050 but we have to hurry every new investment has to be pointed in the right direction so that when the old infrastructure rolls off. The new infrastructure that rolls on is clean green and oriented to net zero by 2050. We show, and especially our modeling team shows that the costs of this are extremely modest. We have the action of 1% of GDP per year to achieve a safe planet and cleaner air and multiple co benefits of a better life. So it's not a cost at all, taken in the big picture. And this is the story. We are presenting this to AI a today, we will be presenting it to members of Congress and of course to Vice President Biden's transition team. I believe that it can be an important basis for what will be intensive deliberations and policies in the coming year to show the practical pathway to climate safety as part of a world that is taking such efforts together. So without further ado, let's turn it over to the real experts here to Lori and to Roger and thank you again Ben for hosting today's workshop. Okay. Thank you so much Jeff for getting us started. And I was also going to mention the fact that four major countries that had all announced recently this remarkable commitment to 2050 or 2060 in the case of China. Very bad look for any country to be just, you know, 10 years later on these so I don't think I don't think it'll stick there for very long. But in all events, I want to start by, if we can just go to the next slide. I just want to start by emphasizing that a lot of the, the, the way that this overall plan has been developed, and a way that the impacts have been estimated to these four key pillars that are identified here, electric decarbonization electrifying everything that's electrification energy efficiency. And I just want to emphasize here, the degree to which the building sector work is very dependent on the work of other sectors is very dependent on the greening of the grid. In order to accomplish much of what we need to accomplish. And we're also very dependent on energy efficiency, both in our sector and in the transportation sector and if we just go to the next slide I'll just, I think that's so important. Here we have a situation where the overall impact of carbon emissions in buildings. And if we're just talking about the actual emissions directly from buildings, when they are burning fossil fuels on site. Thus, that alone gets you to 12% of our entire footprint being from buildings. However, when as in the second graph you allocate the amount of electricity being used already in buildings, it jumps to 32% of our entire carbon footprint as a country. Now, I want to emphasize how much that is by just mentioning that the residential sector alone if you just look at the amount of carbon emissions occurring both on site and indirectly through through the burning of fossil fuels at utilities that serve residential neighborhoods. You have a higher level of carbon emissions than the entire economy of Germany, and almost twice the carbon emissions associated with the economy of Brazil. So we're talking about a tremendous amount of carbon emissions, and we're also talking about an amount for which energy efficiency is going to get us part of the way. And I just want to highlight in the next slide and we can go to it. Just how significant this is this is three graphs would show by 2050, the way that either under a baseline or business as usual approach under an electrification only approach, or under an approach that includes substantial amounts of energy efficiency and electrification. And what it what it looks like in terms of electricity use, and you can see that the extraordinary amount of electricity use that will be necessary if everything's being electrified and cars are being electrified but also their stationary equivalents buildings are being electrified. And the surge in electricity is huge, and that in the short term can cause a lot of carbon emissions, and also can cause greater expense in building out the green grid huge additional expenses these graphs from an exercise in the Boston metropolitan area. And by the Boston folks to determine that if we just went with full electrification without concurrent energy efficiency, especially in the early years, the costs associated with building out the grid the additional transmission costs, etc. That could be as much as 300% greater than without the energy efficiency. So, just as we are very dependent on the greening of the grid, which will be done by the energy sector, I believe that the overall project is very, very dependent on our publishing a great degree of energy efficiency under the models in Jeff sacks approach we're assuming to get the numbers we want that it'll be a 40% per capita energy efficiency goal. So electrification, yes, possibly even the most important thing, but energy efficiency a huge piece as well. Next slide. Now, I want to introduce Lori's portion of this in which she will take you in fast and furious style through the five key points that we believe are necessary to get to net zero that what she's talking about our policies that will need to be implemented by an significantly complex alphabet soup of agencies at the federal level, the state level, and at the local level. So here in Washington where I am, the federal government advances the energy efficiency and electrification of its buildings through more than 12 different There are different agencies that have huge, huge footprints in terms of their buildings. There are different agencies that deal with private sector buildings that deal with public sector buildings like the private sector buildings like the energy star program. Public sector buildings like the Department of Energy State energy program. There are also land use laws that affect transportation and other things related to the built environment. There is also and this very important tax policy that that does in some cases engender either more emissions because it engenders more of the sprawl type of development that we're that we're experiencing historically or Fannie Mae has become a positive force it subsidizes mortgages but it also encourages greener buildings and you can get special treatment if you are an energy star or a lead building. So, finally, state local tribal territories all have their own building code by the way this is completely untrue in other countries where there's national standards for all of this. And so, as you're listening to what Laurie has to say, think about the importance of the national goal setting, whatever the challenges that the next president will have with Senator McConnell's Senate. There's great power in the role of goal setting and standard setting at the national level. And that's what you'll see from Laurie's description is what we're trying to put on steroids. So that leadership at the top, supported and implemented and creatively advanced also at local levels can be successful so with that I will turn it over to Laurie. Roger. I'm going to end thank you Ben and Jeff, and now I'm going to be fast and furious. I want to backtrack just a little to the four pillars that Roger mentioned and just talk a little bit more. Maybe quantitatively about how this works. So, this is a, this is a diagram showing how much easier it's going to be to achieve carbon neutrality in the building sector. Then we all thought it was going to be when we thought we were going to have to do most of it through efficiency. In recent years, the grid has started to become much, much greener. And now there's electrification on the horizon. For those of you who don't really understand that that well electrification means that we're going to stop burning fossil fuels in buildings for heating hot water and for cooking. And we're going to start to use heat pumps, which are very efficient, rapidly improving cost effective technology so these two emerging trends, the greener grid and cost effective efficient options for electrification. Now make a much easier decarbonization path possible. So let me walk you through this, how it works. The bar on the far left shows the relative emissions in the United States from electricity and fuel. The blue part is from electricity, a little over 60%. Let's assume we can electrify about two thirds of that so that electric part increases, and the fossil fuel part decreases that's the second bar. Why do we say two thirds. Well, it's hard to say but there are a lot of old buildings, it's expensive to transform them all steam heat might be particularly hard and expensive so just a guess, maybe we can achieve two thirds very cost effectively. Then let's say we cut energy use by 25%. We might be able to go to the 40%. But that takes you to the third bar, which shows we're down by 75%. But then here's the magic trick where the carbon neutral grid kicks in let's say we get 90% carbon neutrality. Then suddenly all that all those carbon emissions coming from the grid vanish and we're down to much less than 20% of our original carbon. So it's that 123 steps that gets us to very low carbon. And then the final last mile, which we don't know exactly what we'll need to do maybe carbon neutral gas, maybe carbon sequestration capture and sequestration, probably some sort of combination of those things but we can by the way already know how to do, we can get to very very low carbon, putting us in a very very good position by 2035 2040 to make it to get to that last mile. Next. So that's technically how we do it. Modernizationally, how do we do this in an enormous country. How do we make this happen with our 150 million buildings, 50 states and so forth. So we think we need an overarching structure, and particularly a carbon, a carbon neutral goal for America by 2050. This does not take Congress to set this it's like Kennedy said we're going to the moon. Congress did not have to vote that goal into place so even without Congress. We can set a carbon new neutral goal by 25 or the new administration can set a carbon neutral goal by 2050. Then I think we need the structures in place to make that happen. As Roger pointed out, there are just multiple overlapping jurisdictions and departments and agencies that will have to all be pulling together in the same direction to make this happen. So we think there needs to be either a White House office or I think Roger and I are in favor of a new cabinet department of climate and resilience that organizes this vast effort, including buildings. And then we think the administration has to create a detailed plan that harnesses the federal agencies, the states, and that it should report annually on progress. And the plan that we think will probably have to happen will probably include these five basic strategies that we're going to outline. One is retrofits in a stimulus package. Another is utilizing codes and standards, leading by example and promoting subnational action, R&D and American manufacturing and using the federal fiscal tools. Next. The first out of the gate, of course, is going to be a stimulus package. And we need, we know we need to jumpstart the economy. And we think that allocating a good portion of that federal stimulus package to renovation and electrification of buildings will make a ton of sense. First of all, it's very job intensive to retrofit buildings. Secondly, the jobs that are generally going to be created are good jobs, they're construction related jobs, and any legislation can make sure that they are equitably a portion to cross the population. Finally, they happen everywhere because buildings are everywhere, so those retrofits have to happen where the buildings are, they can't be outsourced. So it's going to be a very even stimulus for every part of the country. We think it should concentrate on two areas, low income housing to help people who are energy experiencing energy poverty. And we think that the buildings that serve the general public should also be preference because these are the buildings owned by the people and so if we're going to pay for them, the public hospitals, community colleges and so forth should be preference. Next. The biggest single thing though that we probably have to do is to establish a national energy code for zero carbon buildings and push for stronger appliance standards. The reason for this is that codes and standards are really the least cost path to an efficient decarbonized building stock. The reason for this is that it's much less expensive to build it right the first time then and add a small incremental cost to put in better low carbon equipment. Then it is to actually have to rip something out and buy a new product and put it back in. So if we can get the codes and standards right. We're on a very, very low cost path to decarbonizing the building sector. How does that work for new buildings. It's the they're the easiest part. So we think by no later than 2025 all buildings should be designed to be fossil free and carbon neutral, once the grid is green. And in addition an awful lot of carbon we haven't talked about this yet an awful lot of carbon is produced by the construction of buildings through the the mining and manufacturing of products used in buildings so the codes are going to have to start to regulate that and start to decrease that existing buildings are a little trickier, but they're changing all the time to their equipment wears out. Windows need to be replaced and when those things happen again is the cheapest time to make it much, much better so we think the codes are a great tool to make that happen and kind of quietly and inexorably move through that existing stock, making it closer and closer to carbon neutral as each incremental change happens. Finally, appliance standards. We've had appliance standards that have been adopted at the federal level in the last four years they've really fallen behind. So the first thing is to catch up. The second thing is to broaden and capture some pieces of equipment like computers and monitors that were never captured at the federal level, and then also to start to include carbon. Next, third piece is leading by example. So this has been something that most the federal government and most progressive state and city governments have done for a long time. They have led by example doing a better job with efficiency with their building stock, and this has gone on for many years. Why did they do it. One is that maybe six to 10% of the building stock in the United States and energy produced comes from their buildings. So you can achieve some reductions that way. And the bigger reason is that it transforms the industry. So if you have that big six to 10% chunk of buildings, going forward with progressive strategies, then you've got a lot of people trained, you've got a lot of call for better equipment, which then says a signal to the manufacturers to make more of that making that much much cheaper so it's really the industry transformation aspect of this that it's probably the more important thing. In the federal portfolio, we think it should commit to decarbonization by 2040 and that would include, you know, enormous things like the military. All those fleets of, of post office trucks and other trucks, all the buildings procurement could be a huge piece. The federal government should assist the state and local portfolios to achieve the same kind of reductions in an accelerated way. And also, I think the federal, we think the federal government has a role in supporting aggressive action in cities at states that want to go further faster in more, more aggressive legislation like local non 97. Next, we also think that we need to do much more with research and development education and supporting manufacturing of clean tech. Right now, about much less than 1% of American research dollars goes into the building sector. This doesn't cut it. We think that we need to bump that up to something like 5% of the federal budget and start really researching things like carbon neutral gases for buildings because we think there's going to be a need for that high temperature heat pumps that might be able to work in buildings that had steam, low carbon production products and other, other products that are going to be that will, will help us achieve all of this at much, much lower trouble and cost. Education we have to invest in the next generation of building efficiency and carbon professionals. There's really going to be a lot of jobs in this and we need a really knowledgeable workforce. We need to really start supporting entrepreneurship and manufacturing in this, even perhaps considering subsidies to American manufacturing to make this happen and resuscitate the rust belt and bring back jobs into places that are going to lose jobs in this transition. Finally, as Roger was suggesting, there are a lot of fiscal tools that the federal government can employ. There are always tax incentives. There could be loans or green banks and maybe one of the biggest of all is are the mortgage underwriting rules by Fannie Mae and Freddie Mac, and then there are probably many, many other such tools that that could be utilized. I think that one last thought before I send it back to Roger, we analyzed what would happen, you know, they're most a lot of what we put forward, nobody would argue with who doesn't like a good stimulus package. But, but I think that there might be some people who are concerned about a stronger energy code that includes carbon. You looked at what if you didn't do that what if you were weak on that relied on the few progressive states to get you there and kind of lumbered along as we have historically, we found that by the time you get to the end of the road with those policies you're 35% away from the goal. And that's putting an awful lot of burden on possible strategies like carbon neutral gases or carbon sequestration and capture strategies that might turn out to be quite expensive. So it seems to us to be quite reckless to leave so much to the last mile and much better to start addressing this soon through better codes and standards where it's going to be a lot cheaper and a lot more predictable. Hi Roger. Okay, can you hear me alright. Thank you Laurie, and especially important where your comments at the end relative to the degree to which it's possible to take other paths and it's possible to be less aggressive in certain areas, but it's not possible to do that and there's no carbon zero by 2050. And again because all these different sectors are in a sense relying on each other there is no room for one sector to fail in any significant way. One of the things I didn't mention when I was describing the pie of carbon emissions from the real estate and construction sector was the huge amount maybe as much as 11 or 12% additional of the carbon emissions associated with the embedded energy based on the life cycle of the construction materials that are used. Now the reason I didn't mention that is that is implicit in and is theoretically at least included in the industrial portion of the pie chart that you saw. But it's again something that the real estate industry will need to be taking the lead on and it's something where again very progressive codes and specification principles will be really critical to reducing that piece of the puzzle. The other thing I wanted to just hammer on a little bit is the last piece of what Laurie was talking about in terms of tax and fiscal incentives. Now this is an area where historically the federal government has produced tremendous subsidies to the real estate industry, which have done a lot of good in terms of allowing more people to afford homes and 30 year amortized mortgages, the tax deduction for interest, etc. There's never been any meaningful condition to doing that, but it seems to me that if we are setting clear standards and goals. There should be a point at which banks begin to be nervous about financing those buildings which are not going to achieve those goals or could be out of compliance with those goals. And it's our view that if we could get to the point where, you know, for example, there are now laws in New York City that require that there be grades for buildings similar laws have passed in other countries. But what's interesting is that in other countries, including for example the Netherlands, major banks are now not willing to refinance buildings that achieve lower than a certain score. And so our vision also includes this idea that the remarkably lush amount of money and very attractive tax benefits that real estate has gotten in the past, need not be completely disconnected to to one of the greatest and most important goals of the country which is to get to carbon by 2050. And if we move in that direction banks will actually get out ahead of the regs they will be so cautious about lending on buildings that might go out of compliance that in our view they will start insisting that buildings owners prove that they're doing the right thing. The last thing I wanted to do which is again reinforcing a couple of points that Laurie's made. Really the first I want to go to is that in general with this exercise just so people understand, we're only talking about social equity issues largely as it relates to the displacement of jobs caused by this particular project we haven't taken on more fully the critical issues of poverty alleviation and social equity issues. However, we believe that the real estate piece of this has the greatest opportunity to have that impact as a dividend to the good work we're doing. So in other words the energy poverty reduction that Laurie talked about if you just look at the way it was done under the Obama stimulus package, the analysis done afterwards was very very encouraging as to the amount of long term savings and reductions in energy bills for those who can at least afford to pay them. And secondly we've done a tremendous amount of analysis relative to the overall job creation. If you look at the big picture plan it talks about 800,000 jobs being created by energy efficiency related issues, 500 almost of those are in the building sector, so 500,000 new direct and indirect jobs every year. So as a result of the amount of economic activity that will be necessary to achieve these goals. So I just want to basically end by pointing out that there's right before the COVID hit the fastest growing area for new jobs one of the fastest in the country was energy efficiency related jobs. And more than 2.3 million Americans twice the number of jobs held by people in the entire fossil fuels industry, and those energy efficiency jobs were among the most brutally ended by the COVID activity so we have a lot of people that are trained to do energy infrastructure who could be brought back into the economy in a very powerful and positive way. So, with those two points, I will just close by emphasizing if it's possible to do at this point that we had a very simple plan. We had five elements retrofits in a stimulus package and you heard Lori talk about that the codes and standards element of it, the leading by example and promoting subnational action the states and localities utility programs in advance in R&D at least five times the amount of investment that we've had in the past I think we can do with much more. And then finally the use of federal and fiscal tools. It's that easy. We think it can be done. And Lori, it's been a great pleasure working with you on this. Likewise. Wow, that was, that was efficient. It was a lot I sort of have to stop taking notes with my hand. But this is great. There are a lot of questions and we have about a quarter of an hour so we'll see how how rapid fire we can do with the questions I think it's so interesting the range of questions of course are now like relating to our political changes that are happening and how we're going to support this and then some of the things that I have to do with the plan itself. I'm just starting with one that has to do a little bit more about you know sort of political structures. What are the advantages of creating a climate and resilience department and cabinet position versus appointing a climate czar to work across existing programs at EPA, DOE, etc. Any thoughts on that. I'll take back at it. Otherwise, I'm happy to answer. You have to unmute yourself if you are. Why don't you take it. Lori and I felt strongly and of course the Senate to the decision of the apparent failure to get a Democratic Senate. You know, we'll put this on hold for a few years, but we felt it was extremely important that this not all be treated as one of these sort of short term stimulus things with a czar as though it's sort of some kind of working group or some issue we're talking about creating an institutional 30 year process with mammoth amounts of new programs at universities new new types of jobs we can't even imagine. And we're also talking about having a government that for the first time would really treat this as a statutory the absence of being able to do legislation on this, it's going to be very important to have an office in the White House that can over time transmute into, or ultimately become a cabinet level position, but we think anything short of that a czar really has, it makes it feel more like it's a short term challenge. And the amount of coordination that is going to be required here is is is almost staggering because you're looking at, you know, when you think of the federal departments that are going to have huge impacts on on America's carbon footprint department of transportation, department of energy, EPA, education, the, the military of course with its huge footprint, you know and on and on and on it goes. You've got to have, you've got to have kind of the administration muscle, all that goes along with having a department. And all those people who are paid to do all those complicated pieces of analysis and and making sure things actually did happen and measuring the impacts and adjusting the plans you know it's just the amount of you know bureaucratic muscle this is going to take is really going to be huge. I just would note that it is a very fair question because of course there are consequences to the lack of the Senate and we're happy to talk about that more, although we're here mainly to talk about substance of the proposal. So if you could going on this in the absence of that with through a federal through a White House office, and you could, you could create a plan, somebody asked me was 21 for 2020 January 1 2021 for the plan. And I was at Stefan you were absolutely right I meant January 1 2022. The plan would have to be delivered to the American people of, of how this administration proposes we achieve carbon neutrality. Laurie has an interesting parts of footnote that Jared, the presidents of Sun Law will actually be doing the plan by 2021. More challenging. So, how about one about something you know it within the plan. Does the Z cap have any component component to include embodied carbon already recognized to be nearly half of overall emissions tied to a building depending on the materials use. And this person's own research is revealing that LCA's are only considering fossil fuel use and material construction yet emissions due to extraction can far outweigh that. So and also that would is rarely a carbon neutral. Yes, we do have several proposals. The first is that the new energy and carbon code start to capture that. So exactly how that happens I don't know maybe it's a cap per square foot for different types of construction that gradually ratchets down, or maybe it's, you know, maximum amounts of emissions from concrete. There are many ways to do it we we propose for the first time that we shift from a pure energy code. So this is a big change to be an energy slash carbon code. And we'll deal with operational carbon, and with embodied carbon. So, I should conceptual change there. Go ahead. I was just going to say that recognizing this is a very, very sharp group of folks on this webinar I suspect for a variety of people, including for example, the chair of the AIA New York's coat that could probably write that provision better than us so there are people that are deeply committed to this with a lot of sophistication about this and I suspect some of them are on the call. And many of you are going to be necessary to hammer this out in reality we're just laying down the gauntlet in a way here, very broad brush. And then the second way that we're addressing it is through the research and development proposals that we're making and manufacturing and so forth that that we really push for research and development in this, not just in better materials and construction techniques and all of that, but also better knowledge in terms of these embodied carbon and better data and information on that that could help the industry move forward. We think of it as the embodied carbon discussion is being somewhat in its early phases, whereas energy efficiency is, you know, a very, very mature field. So we think that a lot of work has to go into making that grow up. But I don't think it's anywhere near too early for for proposals to go into the codes. There's a question here about demand flexibility. So what role could and should demand flexibility in buildings have to decarbonize it helps reduce over building renewable energy on the grid, but that is captured in the electricity sector. Does the roadmap factor in that. Well, I answered by saying, absolutely, that is factored in. And again, you know, pardon us if sometimes we have given more range to another sector than the building sector on this because that kind of demand response type of strategy is both a real estate strategy and an industrial strategy as well. So it's something that it's very much on our minds. And, but like a lot of this it's very challenging to because it's going to be so critical that kind of demand response type of work in the first 10 years, but then as we move to getting a greener and greener grid, we'll have other priorities but in this period where energy efficiency and and peak load reduction is at its height in terms of prioritization demand response one of the most critical ways of addressing there's one other proposal that we make. That is that new buildings should be capped in terms of their annual heating and their annual cooling loads very similarly to the passive house. That's what we do. It just keeps those additional heating and cooling peaks low, which, again, reduces the requirement to create an increasingly bigger grid. Well, to my to my friends in the commercial real estate industry Lori is not saying that if you have multiple floors of trading floors and everything else that suddenly that's going to have to meet a residential passive house standard that doesn't contemplate that so we're not we're talking about residential No, no, no, and only for heating and cooling loads, not for other building works recognize very widely in court in terms of, you know, the needs, because of the functions that are housed there in heating and cooling are mostly independent of function and can be addressed upfront and it's, we now know how to do it quite well. There's a question. Simple question that I always have and I think considering we're going into a new administration. This becomes relevant again. Do you have examples in other countries remember that we so used to look at other countries. That have that have been put into place that are maybe similar structure to what you're proposing. I think, particularly just adding to that, dealing with affordable dealing with public buildings. I'm just wondering about Nordic countries other places are there any examples you're aware of that might be interesting to look at. I would just quickly say that that that absolutely in every way we have learned a huge amount I personally was on the board of the world green building council which might sound a little less a territory to make it was just a lot of green building councils from around the world and we learned a tremendous amount from different parts of the world about what they're doing in all of these different areas, having said that the United States as we've all witnessed over the last four, last four days is an unusual beast in that every single city sometimes counties have their own building codes have their own laws relative to this just as they had their own laws related to how to count the ballots. That is not the case in other countries there are national building codes for most of the countries that we're looking to as models. And so the process of transitioning something in that way jurisdictionally will be will be different than in other countries and challenging. All right well sadly I was given the signal that this is the last question. So, I want to thank you both and Jeff, and you know for this wonderful opportunity to get architects and others involved, I think it's just the beginning, obviously. Maybe we'll continue to follow up with more events get more questions for discussion going but it's a hopeful moment right now I think to be able to think about this right to actually think this might really have a chance so wonderful thank you all for coming. Thank you for posting us. Thank you to AIA New York and the Center for architecture. Yeah. All right. Bye everyone. Thank you guys and I did want to let everyone know we do have upcoming webinars to dive into the other chapters within recap over the next three weeks will be looking at the equitable and just transition tomorrow, which talks about our job analysis policy and implementation later this week. And then we have more of our sector chapters materials industry and food and land use in the following weeks. These slides and the recording of this webinar will be made available on our Z cap website that has been entered into the chat several times. So give it a few hours for us to upload our recording but you will be able to access that after this. Again, thank you Roger, Laurie, Ben, and we'll see you guys next time. Bye.


Yuma's flight line and others across the globe have purchased a new FODFinder system, which uses state of the art radar technology to not only locate the problems, but eliminate them as well. This is an area where debris has been found. How did that debris get there? Was it a tool? Was it a part of an aircraft? Was it just environmental, rocks, things like that? Over time, you start to build that database up and it tells you where you have FOD problems on the airfield and then you can use these maps that we provide to tell you, hey, this is a place where we need to focus. The system's radar can scan the equivalent of two football fields every two seconds. It can also detect an object as small as a one millimeter wire with its 360-degree pan-tilt zoom camera. This system includes the radar, a vacuum to pick up the debris, the 360-degree camera and a wireless camera that syncs to a GPS to mark the location of debris for future reference. Running off of a 12-volt battery, it is easily transportable and can be hooked on to potentially any vehicle. If we can stop the debris from meeting the aircraft, that saves us an engine loss, that saves us entire loss, it saves us on damage to the aircraft. So you think about the hours that are put in building engines, repairing tires. If we can decrease that by just a little bit, it allows the warfighter to spend more time improving our warfighting capability rather than repairing what we've damaged. The next step for the FOD finders is to deploy the system. This is Lance Corporal Laura Cardoso, Marine Corps Air Station Unit.


Good morning, welcome to morning prayer from right here downtown in Kalamazoo, Michigan, where we are crying out from the heart of our city to the heart of God, asking him to move, seeking him to move, to heal, to restore, to do the incredible things that he does. And whether you are in this room today or you're joining us online, maybe you're in your car or you're at home or you're in your office, regardless of your location, we have the incredible privilege and the honor to awaken the day and to start our day, to bring to God the first of our day in adoration and worship and exaltation and with thanksgiving. This morning I, I want to read out of Psalm chapter five. This is, in my opinion, one of my, well this is just one of my favorite texts about what it looks like to wake up every day and to seek the Lord, starting out with the first of my day and then waiting all day long and seeking him all day long for him to answer and respond. The psalmist says in verse one, give ear to my words, oh Lord, consider my groaning, give attention to the sound of my cry. So this isn't just prayer recital. This is a man who is crying out from the depths of his heart, from the pain within his heart and he's crying out to God. He's not just bringing him words of religion, but emotion and feelings. He's bringing to him not just his day, but what is, what is hurting within him and what he needs, my King and my God, for to you do I pray, oh Lord, in the morning you hear my voice. In the morning I prepare a sacrifice for you and watch. When he says watch, what he, what he's saying is I, after I bring it to you and I lay it before you, what he's saying is now I wait expectedly. He doesn't just move on and go about his day, but he waits with expectation for his Lord, his God, his King to answer him. For you are not a God who delights in wickedness. Evil may not dwell with you.    The Lord abhors the bloodthirsty and deceitful man, but I, through the abundance of your steadfast love, will enter your house. I will bow down toward your holy temple in fear of you. Lead me, oh Lord, in your righteousness because of my enemies, make your way straight before me. Jesus, it is through the abundance of your steadfast love, not through my good deeds, not through our best efforts, not through our perfectly rehearsed prayers, it is through the abundance of your steadfast love that we are able to come into your presence and Lord, we come this morning with boldness and with great expectation because of your blood, because of your sacrifice, Lord, when all of our sacrifices fell flat, Lord, your sacrifice, your perfect sacrifice brought us back and restored us and gave us permission and access to enter, to come to you with expectation. So Lord, here we are, we come to you this morning and we start, Lord, by saying we love you and we're thankful for you. Consider our groanings, consider our requests this morning, Lord. Not because we are good people, but because you are perfectly good, because you are awesome, because you are holy, because of your steadfast love, Lord, which you consider our groanings and our words, but you give attention to the sound of our cry and our pleas today, Lord.  We're not just going to sing them and walk away, but Lord, we are going to speak them and sing them and with great expectation, we are going to wait all day long for you to answer us. Lord, we thank you for your steadfast love. Just begin to thank him for his steadfast love, that despite what happened yesterday and last month and six months ago, that despite what's going to happen tomorrow, his steadfast love will be fast and never slows down and never backs down. Jesus, thank you for your steadfast love and what doesn't happen your steadfast love endure. It has never slowed down, it has never ceased, it has always remained. Lord, would that reality grip us this morning? Would it grip us despite what we have going on, and despite what we've walked through with that reality grip us this morning? Would it not just be words on a page or words that we sing, but would the reality of your steadfast love shatter us and shake us? Lord, your steadfast love endures forever. Lord, your steadfast love endures forever. Lord, your steadfast love, because we know that, know that to be true, we have come to worship you. We have come, that's why we're here. It's why we're up at this hour. It's why we're doing this right now. It's why we're not busy in the traffic of today. We have come to worship you. So we welcome you this morning. We welcome you. And Lord, we say have your way. Have your way. Many of us have schedules and agendas today that we have to do and meet and accomplish, but Lord, in the midst of all of that, we lay them aside and we say, Jesus, have your way. Have your way. We bless you, Lord. We have come to worship you. Come to worship you. Have your way. In this play, in this play, a song, a song, a song. Hebrews 9 verse 11 says that when Christ appeared as a high priest of the good things that have come, then through the greater and more perfect tent not made with hand of this creation, he entered once for all into the Holy Places, not by means of the blood of goats and calves, but by means of his own blood, thus securing an eternal redemption. For by the blood of goats and bulls and the sprinkling of defiled persons with the ashes of a heifer, sanctify for the purification of the flesh. How much more? How much more will the blood of Christ who through the eternal spirit offered himself without blemish to God purify our conscience from dead works to serve the living God? Jesus, it is only by your and we thank you, Jesus, for your blood. We thank you, Lord. We don't take it lightly. Remind us of your blood, Lord.  Remind us, Lord, for it's only by your blood. How much more? How much more will the blood of Christ? Lord, we speak the how much more of your blood over our lives. We speak the how much more of your blood over our city, over Kalamazoo, over Richland, over Portage, over Plainwell, Otsego, Battle Creek, all the way up to Grand Rapids. Lord, we speak the how much how much more blood of Christ over Southwest Michigan, Lord. It's only by your blood, Lord. It's only by your blood and we plead your blood over Southwest Michigan.  Over the forgotten, marginalized, the downtrodden, the weary, the neglected, Lord. We plead your blood over Southwest Michigan, Lord. The how much more blood of Christ over Southwest Michigan, Lord. We plead your blood, blood, Jesus, over our families, over our schools, over our local government, Lord. How much more? The how much more blood of Christ? We plead your blood over our marriages, over our children, Lord. We plead your blood over our first responders, over the police officers, the firefighters, the paramedics, Lord. How much more? We'll sacrifice for all sin, sacrifice, Lord. We thank you that because of your sacrifice and their lawless deeds, no more. We hear sacrifice, Lord. There is forgiveness of sin that where there is forgiveness of lawless deeds, there is no longer because your sacrifice paid it all. It didn't pay partially pay it and paid it all, Lord. And so we thank you, Lord. We thank you for your sacrifice, which is the full embodiment of your steadfast love, which endures forever, Lord. We for our families, over our kids, over our marriages, Lord, over our parents, Lord.  For thus says the Lord. It has a foundation in Zion, a stone, a tested stone, a precious cornerstone of a sure foundation. Whoever believes will not be in haste and I will make justice the line and righteousness the plumb line and hail will sweep away the refuge of lies and waters will overthrow the shelter. Then your covenant with death will be annulled and your agreement with shield will not stand. Jesus, we thank you.   Lord, we thank you for your blood. We thank you, Lord. I pray that today as we go about our day that there would be a melodic melody, a melodic anthem in our hearts pleading the blood of Christ over our Christ over the crown that we walk on pleading the blood of Christ over the people that we walk by and pass by. Jesus, you are the precious cornerstone, the sure foundation. You are the one whom who has made justice the line. You are the one who has plumb lined the reality of righteousness.  You are the one, Lord, who's annulled the covenant of death and the power of death, Lord.   It is you, our precious cornerstone, Christ alone. It is you, Jesus. And we love you. We say we love you. Thank you for your steadfast love that has annulled the power of death that once gripped us and had us within its talents and it entangled us with its cords. But you, Lord, broke it. You, Lord, destroyed it. Cornerstone. Christ our cornerstone. Christ our cornerstone. Thank you, Jesus. Thank you, Jesus. Thank you, Jesus. That when the rain falls and the floods come and the existence it is you and because of only you, that the house, that our lives do not fall. It is you, it is only you. You are our rock. Again, Jesus, we plead your blood over our lives, over our families, over our city, our government, Jesus. We plead, bring us joy, place we go, and every conversation we have with your blood speak a better word over us, to us and through us. Jesus, we thank you for this day that you have made. We choose to rejoice and be glad in it. It is you and it is only you and it's because of you that we all say, to this day, to this hour, amen. Thank you for joining us online. We will be back tomorrow morning. We invite you to join us. We always want to invite you down to the prayer room to be here in person if you can make it. Otherwise, have a blessed


It's very astute, I think, to point to survival and the fear of death as occupying a keystone place in our culture. I think it's obvious that human beings are not only motivated by survival and maximizing security and minimizing risk. People do all kinds of things altruistically all the time, which evolutionary science has tried to explain away as kind of malfunctions of the genetics which love is supposed to be to help your progeny survive, but sometimes it kind of misfires and you altruistically help somebody who doesn't have your genes. I mean, that's a nice try. Even like Maslow's hierarchy of needs, I think in a way is upside down. People do heroic things in the most extreme circumstances and more generally, you can try it. I mean, you can verify this personally. See how you feel if you just dedicate yourself to being as safe as possible and not giving anything to the world because why would you give anything if you could have more for yourself that would make you a little less secure? See how it feels. You're not going to like it. You're going to recognize a drive in you to do more than that, to make the world beautiful, to do something better than you need to for the customer, for the market, for the money because you're devoted to that thing in and of itself, whatever wants to be born through you and whatever the world wants to be through your participation in it. This is a different story of what a human being is than the one that economics and genetics has narrated to us. So as far as death goes, our society and our belief systems make death a lot scarier.  We're at the apex of knowledge, and they just didn't get it right.  How much has to be excluded in order to maintain that view? A lot has to be excluded, like all the reincarnation research, like near death experience research. There's voluminous documented research about this kind of stuff, and a lot of people have had personal experiences. I've had experiences that obliterate the story of self that I have received from the culture. A lot of people have those experiences, but you kind of keep those out into the spiritual realm or like you were saying before, like you don't let the word healing get into the world economic forum or the academic conference or sacred or spirituality. We only maintain a world in which we enact the story of self-interest maximization to the detriment of this planet. We only maintain that by shutting out all of the data points that don't fit, and all of the experiences that don't fit that narrow, confining story.