Anyway, thank you very much for coming. I'm not Dave Ings, as it says in the program. I'm Michael Dawson, IBM's community lead for the Node.js community, and a contributor and developer. And we have a great panel here today, and we're going to talk about the state of Node.js. I'll let our panelists introduce themselves. So maybe we'll start with Trevor at the end, since you've got a mic. Yeah, hello. My name is Trevor Livingston. I am a principal architect at HomeAway, which is an Expedia subsidiary. Previous to that, I came from PayPal, where we did Node.js at scale. And we're doing the same thing over at HomeAway now. I am Tracey Lange, notification community manager for the Node Foundation, last part of the Lange Foundation. Is that it? Maybe we just need to be closer. Is that better? Oh, thanks. I think so, yeah. I can just talk real loud. It's been about two years since the foundation came together. And just wanted to get your opinions on, you know, what you think is working well, what's not working so well, and, you know, sort of where we're on, where we're going to lead us off on that one. Sure. I mean, when the foundation was first started, the immediate question was, like, how do we work? It happened relatively quickly. I mean, it was definitely a line during the process. Doing that work would probably double the number of procedures in the project as well. So we had a lot of kind of new sale problems. We had an LTS policy that was just created. And a lot of that stuff was kind of a movement.  The final version that actually worked everything together was version four of what they asked. And we've just recently put that in the maintenance mode. Now we've been out of LTS, right? So we kind of looked back at, like, a full cycle. And that's all worked out really, really well. I mean, adoption of the node has continued to double every year. But most importantly, you know, adoption of new releases of the node is really good. And it continues to get faster every time we do a release. And every time we do, you know, a new LTS line, we see adoption skyrocket again. So we can kind of say pretty different than those policies they work. They really do encourage adoption. And that having, you know, a fast pace of initial development really gathers more commuters because now we have, like, over 100 commuters. So yeah, we know that all of that kind of stuff is working. I think that when your community is growing that quickly and the contributors are growing that quickly, you're always going to have new scale problems. You're always going to have, like, single points of failure where this person took on a responsibility because they had the time to do it. But now that responsibility is, like, three times what it used to be. And so we need to figure out how to break that responsibility up into more people and bring up new leaders and all that kind of stuff. So I think that there's always something that's not working in the project. The important thing is that there's a process of re-evaluating what isn't working and changing it and fixing things. Right. And I think, you know, your key point there about bringing up new leaders is one of the really important things, like how to bring up new people and enable them to help out in those areas. Yeah, I think the key for me that I've seen in coming up with Node and sort of its maturing is collaboration and sort of understanding what that means, but that means within the technical group with companies coming together and coordinating efforts through the foundation of Node and then people working together in the ecosystem as well. Even with you think about the idea of the fork with I.O. and those collaborators coming back into the fold with the companies that they needed to come to a neutral standpoint with. It's really interesting to see the challenges of Node growing as a community and ecosystem and the scale that we're operating at now and how every portion of the project has to find new ways to work together. It used to be that we would have single owners of areas of even the technical project and it's an awesome blessing that we're not having that bus factor anymore but that also means that then multiple people have to work together and it's interesting to think about how large the Node project is and how we could still have single owners on those things and we're trying to fix that because that's important to not have that bus factor. But yeah, getting everyone to work together in that and even looking at things like how we're working so much better together with the V8 team at Google because we rely on a lot of upstream so it's really important that we have been able to focus on that so that's exciting for me that we've seen that coming of age and that's sort of the new era with us I think in the maturity of Node. I don't really have a lot to say other than that it's been a night and day difference. It's amazing to see how quickly things have progressed since the fork has merged back in and as Michael was saying, the number of contributions that have gone up has been fantastic. It's almost too fast at times. When you work at a larger enterprise and you're trying to operationalize and you have these new versions coming out and everybody wants to get it and then you're kind of trying to hold people off so that's kind of a challenge but that's a good challenge to have. Right. I'm just wondering from your perspective, we're pretty close to the foundation and sort of getting the core run time out. In terms of more of an end user, is the foundation doing all the things that you'd like to be seeing being done or are there some things that you'd like to see more of, less of that kind of thing? To be honest, I don't have a lot of insight into the operations of the foundation. It feels like the right things are happening but it's actually really hard to say from completely outside the community because I have a lot of connections to core contributors. And so I have a little bit of the kind of insider info sometimes on things and I can also use that to sometimes get things addressed that need to get addressed. So one of the things I don't have insight into and I wish I knew more about is how people that don't have that connection are perceiving whether things are being addressed like they need, whether it's a feature suggestion that sometimes feels like a little bit of a... not really a club-based mentality but sometimes it feels like there are a limited number of people who have the final say and there may be good ideas out there and people are having a hard time getting it in. And when you have the inside track you can just kind of go talk to core contributors directly and try to socialize it. So it's hard to say, I'd be kind of curious to learn more about that from the outside. Right, okay, that's a good point. I think in general it would be nice to have more direct input from external users who aren't quite as slow so that's a good point to think about that. Yeah, I mean it gets harder every year because the community is doubling. We have about 8 million users now. So how do you get a beat on how 8 million users feel about something going in? We certainly can't just optimize for whoever happens to be the loudest in an issue. That would not be good. But we do have a fair amount of metrics, we have a fair amount of data. We can look at the NPM ecosystem and what's growing and what people are doing and we can actually respond to what people are doing. So I think a lot of the stuff that really pushed some of the recent promises work over the line is that you can see how people are using these now. You can talk to a bunch of people that are using them in different ways and go like, what are the problems that you're having? How do we actually improve this experience for you? Whereas before it was a very opinionated person that was maybe not even running the stuff in production yet. When we have this many dependencies, we can't be leading like that, we can't be adding APIs that we're going to have to deprecate in the future because they were the wrong idea. So things are getting easier. But if you just have a random idea for a feature, it is somewhat hard to get that in without just code. If there's code, everybody can evaluate it. There's a decision making process that's all there. But when it's just an idea and not code, that does get very tricky. Something that we've talked about, I think in some of our community committee conversations, we'll talk a little more about that I think later, but is the concept of, if you think about our project almost, it's not a product, but if you think about it in the sense of like, how many people we need to support, then sort of from a customer support angle, we do need to start moving forward at how we can help support all of those people. Like, do we have easy getting started? Are they easy to find from a search perspective? Are we supporting them or are we expecting the ecosystem to support them? Do we have active chat channels? Other companies are adopting channels other than IRC for their customers being able to reach out. Our customers or users or developers need to be able to have ways to do that. But we also can't rely on our core contributors to answer all of those questions because otherwise then they're also not able to work on their code because it's too many people. So sort of like trying to solve that problem moving forward is a really interesting one. Yeah, that's a really good point too. So one of the things Trevor mentioned was the releases that are coming out. So we just had Node version 8. We have releases. That's our biggest win from these days. We have releases. So we just had Node version 8 come out. So I thought I'd, you know, see what you guys thought about it, your favorite features. I know which one mine is since I worked on it, but get your input on what you like about what just came out and what you're most excited about. So maybe Trevor, if you want to start? Yeah, I think that my own favorite is the rewrite of async hooks or async listeners or however you want to call them. But I know that that's still experimental, but I think that's going to be really promising. I know firsthand kind of the problems that something like continuation local storage can cause in software. So seeing an opportunity to potentially improve those things, improve the performance, I think we're going to see a lot of wins across the board in areas where we need to use those kind of things. So I'm a little bit hesitant and it's maybe not a feature that I'll personally use a lot, but I'm hoping that we see some improvements that come out of that. I think one of the other ones is, you know, and I think that is a common favorite is async await. I'm not a huge fan of promises myself, but I know how well it helps transition new developers into Node. And I think that that's just one of those things that that little extra syntax sugar gets people excited and they feel like they can ease into it a little bit more easily. Yeah, I think I'm going to echo the point of the promises looking forward to more promises support. So you told I'll promise if I, I think it's my favorite from a technical standpoint. And what a challenge I think it was to make that happen, but also that it represents us making sure that a lot of people are taking care of if they want that option. And I think that that was a really important win. And then I'm also going to throw in another win. I think that was really important to call out that NPM 5 being rolled up release wise with Node version 8 was a huge win in terms of us understanding how much it takes to coordinate and collaborate. And I don't think we'd had a major release coordination like that since the early days of Node. And that's when the leader of NPM and Node were the same person. So it was pretty easy to coordinate. So it's just, you know, that in itself, I think is it shows us that it can be done. It's not that we need to be doing that regularly, but I think it's really going to concrete, you know, a good year for us moving forward. Yeah, I think that along with your comment about the, that along with your comment about the, you know, the closer relation relationship with the VA team really shows that, you know, as a community, we're making good strides in building those bridges. So that's, it's a really good thing. So on that note, I think, so my favorite feature is, is that the native API finally landed in some form. So that's, I mean, in literally, you know, the first week of I OJS, we started to try and repair and create a better relationship with the VA team. And that's only gotten better. In fact, every time that I'm at any conference, I get to say the relationship with VA is better than it's ever been because it's only gotten better from that point on. But I think that this is where the foundation really went out by coordinating an effort between Microsoft, Mozilla, Intel, IBM and Google to not only create this native API, but for all of the existing VM developers to say, we're going to support this indefinitely. Doesn't, this was an argument that we had, you know, before the fork, which is, you know, Node can say whatever it wants is, is it's native API. It could make that up a ton of times in the past. But if the VMs don't say that they're going to support it, then we're going to eventually have to break that API. It's not actually going to be stable. Because we know from experience that the VM APIs are just going to alter themselves enough that we're going to have to make some kind of breaking change. We've seen this with Nan, right? If you were to go into the code base, if you were to send a PR to Node, and it was like the best feature that anybody had ever heard of, but it required 30% of the users of Node to go and intervene into their project and do something, that feature would never land. But we do that every major release, because every major release we have to take a new API from B8. Finally, we can kind of see a light at the end of the tunnel now where eventually we will stop doing that. We will stop breaking 1% of the packages in the ecosystem that are native, that are transitively depended on by 30% of the ecosystem. We will actually stop breaking those, right? We can ensure a level of stability that we haven't before. And I think as good as our numbers are right now for people adopting new releases of Node, it's going to go up even further, because now there's just no barrier to updating, right? Being part of the group that's been working on that, it's really good to hear the excitement. The other thing that I found interesting, it's a little too early to name names, but there's been a few people from outside the Node community that have been looking at the API as something that they might want to use for their languages as well. So I find that that's really interesting. It's like, hey, maybe it'll be a problem, an API that solves a broader problem, or Node, which is really a good thing as well. I've run into a lot of Java developers at this conference, so I think one of the things maybe it would be good to touch on is what kind of advice we have for people who are coming from other languages and want to get into Node.js, how to get started, some of the issues that maybe they're going to run into, and just basically what advice you guys would have on that front. Tracy, do you want to start with that one? Sure. So the first thing, I think, with Java or .NET developers, who are coming from other languages, especially those types are, they're used to awesome IDEs, tooling that allows them to get up and get going very quickly. And we have that with Node and JavaScript now. We didn't have that so many years ago. But Eclipse, IntelliJ, Atom, Cloud9, VS Code, which is awesome. All of those have really great Node support and much better than they used to be. So that's really easy to get up and started. And you're also really used to good documentation. That is something that we are still struggling a bit. But that's also because our language is very small. So we rely a lot on our ecosystem. And the documentation in the ecosystem, especially if you look at all of the packages in the NPM registry, a lot of them have really good documentation. And you can, I find that you can also rely on our community, which is a big part of being, you know, being able to write this language that people can recommend really good packages for that. Yeah. And there's also a lot of good courses. So you have the advantage if you've already written another programming language that you understand a lot of the constructs that we're operating under. There are some unique ones that you have to think about that might be different, like threading or streams. They might be a little different than the language that you wrote previously. But there are really good courses on, like Udemy, as well as Free Code Camp. And Westboss, who is prolific in the JavaScript community, has a really good node course as well. And that's hours and hours of concepts that are going to make sure that you really have the JavaScript pre-rex down to understand what you're doing with your node. So. Trevor, again. Yeah. I would second everything that Tracy just said. I think that the tooling has come a long way and it's been pretty fantastic. Most Java developers, I actually, myself, a reformed Java developer. I've programmed Java for about 15 years. And then once I picked up JavaScript and started using Node.js, I never looked back. I don't think I've written Java since. But one of the things that was challenging for me at the time was tooling and the kind of immaturity of the project at the time. Also, really common concepts, things that are really the most important is just how the runtime works. It's one of the fundamental things that you need to grasp before you can actually do anything. And I think that that's missing and from a lot of education. People tend to educate based on the language and the language is the easy part. JavaScript is not a very complex language, but understanding the Node.js runtime and how the event loop works and those things is really, really key. So grasping those concepts makes it a lot easier and avoids a lot of common mistakes that you'll make jumping just from, you know, a multi-threaded language to a, for all intents and purposes, a single-threaded runtime. So at the foundation, we've talked to a lot of enterprises that are going through digital transformation. If you have that buzzword on your enterprise bingo, you're welcome. But it's interesting to talk to them because it's rarely just that they adopted Node. It's also that they adopted a bunch of new workflows and a bunch of new ways that they managed their team and a lot of new ways that they write their code. And one of the things that I've always been really skeptical of is, you know, taking the entire workflow that people do for Java development and then just replicating that on top of JavaScript because you skip all of that, like, nice reforms you have, right? But you do sort of throw the baby out with the bathwater sometimes. Like, there are some really nice things in there that would be nice to have. And it's nice to see some of these tools come along, like TypeScript and FlowType, that replicate a lot of the things that people miss but don't completely change the entire workflow, right, and integrate in the same way. I think another good example of this is, like, Visual Studio versus Visual Studio Code. It is amazing. It's not an IDE. It's an editor with every feature that you ever wanted from an IDE in your editor, right?   Okay, that's great. Right, so, you know, I think we've talked a little bit about where we're at today. I'd be interested to hear, you know, what you think the most exciting and interesting things are going to be that happen over the next year or so as we move forward. So, I don't know, Mike. Mike, do you want to start with that one? A year from now. So, Node, well, Node's already in space, so I can't go there. Yeah, oh, wow, that's a good one. I can't really predict where the native API is going to go. I think, so for a long time, I was sort of expecting that a platform would come along and supplant Node. Like if you've been around long enough, you see new languages come up and other ones die and all that. And a couple of years ago, I started to look at the kind of market share numbers and think, like, I don't know, that might not actually happen. There's a lot of good languages that have come out since then, but they just haven't gotten the kind of traction that Node has. And then I started to think, well, maybe that's not what you should be looking for. What you should be looking at is, what is the layer that people live in when they write their application? And that will probably be something that's not Node. Maybe it's built on Node. Maybe it's something entirely different, right? I think that there's a lot going on right now in the web to try and make it easier to share HTML components, CSS styles. Like in Node, we have this amazing amount of reusability, and you can take a module from five different people and use them together, and those people never knew each other or coordinated, right? This is not the case in HTML components. Like no matter what framework that you're in, you have to integrate these into your application. But a lot of the stuff going on in web components actually give us some primitives that we need to abstract that. And then you can start to imagine a platform where at the same level of authority that you have JavaScript modules, you have HTML components. You actually have a module system and a compatible ecosystem there. And it's kind of unclear what that looks like. I think Webpack is getting kind of close. It's just that right now there's 12 people with opinions about CSS modules, and it supports all of them, right? And that's not a layer of compatibility. But I think that we're nearing it and the further along that the web standards get the closer that we're going to get to this kind of standard. Yeah, I think something we haven't really mentioned that's being worked on and has been worked on is HTTP2. Shout out to James Snell, who's doing a lot of that work, amongst other people. So that's, I think, going to be really exciting. I think people are watching that, and we get a lot of engagement from that when people are speaking about it at our events. Yeah, I mean, I think it's still more, I'm interested to see where the promises conversation goes because I don't think anything that we do in Node related to promises is going to be easy to adopt. From the technical group perspective, it is still very contentious. A lot of the people I feel like in the CTC as well as the TSC are not super excited about promises, but that chip is sale and they understand that it's still needed, right? The option is still needed. So I'm excited to see where that goes, and also ES modules. I still think that that's... What happens with that and when it chips is going to be interesting, but we still are waiting to see. And then from a community side, I think we're still seeing where the community committee can best be used, and we'll talk about that in a little, sorry, as well as how... Yeah, as well as the community committee can best be used. Yeah, as well as... I'll just talk about it. Okay. So how the community committee is going to be collaborating with the TSC and the board, and the community committee in Node is a relatively new thing. It was chartered back in February, I believe, for final adoption, but this isn't really something that's common in code projects, and that is community given a top-level voice. So in most projects governance, you have a technical steering committee of some sort. If it's a foundation, you also have a board which is in charge of the business aspects, and then you have this whole ecosystem contributing in various ways, but in Node, we're finally recognizing that there are serious technical contributions, but that the community itself, the ecosystem has very much been bolstered by all of these things that are outside of the scope of our technical steering committee, but also need a voice in how the project moves forward, and that's from a technical and from a social or cultural perspective, because so much of that is sort of like being in a workplace. You can try and ship a project every week. You're working on this thing together, but are you? You can't work together if you can't collaborate if you're not getting along. If you don't have the ground work where everyone is enjoying themselves, they're going to go elsewhere. There's a lot of programming languages. So we want to lay that ground work for making it a more pleasant place for the people who are already there, so they'll stick around and to get more people involved who are really excited about programming and maybe they want to help us. So that's really a big effort this year is figuring out how we can all help. It's sort of not land grabbing for things that are already in existence that need to be worked on, but it's saying we have so much room for more people to come in and help out from every part of the project. You stole HTTP2 from me. I'm also very excited about that. One of the other things that I'm really kind of hoping for is just generalized improvements or continued improvements in crypto because that's always been kind of a thorn in the side of Node.js development. It doesn't affect everybody, but I think that in the future, as we want to become more secure, it's only going to become more relevant. And it's going to be something that everybody's going to be doing crypto pretty soon. So as we continue to try to become more secure and do perfect forward secrecy and all these things, we need performance enhancements there. So I'm really hoping to see that. I think there are people working on it, and there's been amazing improvements over the years anyway. I think that Node 6 was just a massive improvement in that department. Then the other thing is just kind of coming from the ecosystem is that we're seeing such amazing tooling, and I think that's really exciting. I'm really curious kind of where it's going to go. We see all these major APM vendors like Dynatrace and AppDynamics supporting Node as a first-class citizen. Their tooling is continually improving. I think that we're going to see a massive explosion there. We've got nice tooling like Insolid as well, which is a runtime on top of Node. So I'm really kind of excited about that. What I'm concerned about is the complexity of application development. So you have all these great technologies out there, but often what's required is just gluing them together. And as that, you mentioned web components, but today when you have an application that's using React and Redux, and has GraphQL in there, and it's doing isomorphic rendering, and if you look at a typical application just even a simple one, they're incredibly complex, and that's a huge barrier to entry for people who are trying to learn. If you just do Node.js module development, it's super fun and easy. Once you get into application development, it's no longer that thing where you're like, oh, look how easy it is. That was one of the big kind of exciting things about writing JavaScript on the server side also was you could show it to people and they'd say, oh, that's so easy. I can be so productive. And now when you build a really modern web application, it's not quite the case anymore. So, I don't really know what the answer to that is, but what I'm hoping to see in the next year is that something that gets kind of under control either through better frameworks or better standards. Okay, thanks. I think we just have a few minutes left, so maybe we can see if there's any questions in the audience at this point. The Node.js certification. What's the status plan? I know that's Tracy. Yes. So, we're still actively working on putting together the infrastructure between the different groups that are working on that with the LF as well as with Hacker Inc, which is the environment that we're actually going to be running the certification in. That's an experiment between us, between the Node Foundation and Hacker Inc, which I think is really exciting because it means anybody can take it around the world, almost instantaneously. It's a very quick setup. We don't have to worry about provisioning in the same sense. We're still able to plug up our proctoring layer to make sure that people are who they say they are when they're taking the exam and also not cheating. So, that's helpful to make sure that we're having a legitimate exam that's still offered in browser and you don't have to go to a location to be able to take it. That was really important. And we can also have language support. So, we'll be able to have it in multiple spoken languages down the road very quickly, which is lovely because we have a very global community and we are looking for Q3 release. So, yep. Any other questions? Okay. Well, thank you very much. Thanks a lot to you guys on the panel. Those were always really great and insightful answers and questions. And thanks to everybody who came out and spent the time to listen to us and we hope to see you again soon.


So team keeping clean like where do we even start after everything from yesterday? And you know, I wanted to talk about it yesterday, but then I was like, you know what I need a break I need a break from everything from yesterday even though we freelance and we still got to take breaks We still got to pace our sales, but then I figured everybody else needed a break to collectively gather their thoughts on all the All the events that took place yesterday Because it was just crazy it was crazy and the craziest part wasn't even that the Baltimore Ravens used a non-exclusive tag on Lamar As crazy as that is as risky as that is that wasn't even the craziest thing that happened yesterday But let's briefly go over that. Of course, they did use a non-exclusive tag So that allows Lamar Jackson to negotiate with other teams come up with a price I come up with a salary come up with a contract with other teams and the Ravens have the opportunity to either Match it or to not match it if they match it they keep Lamar Jackson if they don't match it They get two first-round picks from whatever team it is now Whichever team it is they have to have a first-round pick this year and next year If they don't have a first-round pick this year, they cannot sign him to an offer sheet until after the draft Robert Griffin RG3 He brought up something that he was apparently leaked from the Ravens Good timing, huh? But anyway, he said from a team source the Ravens hope negotiating with other teams We'll give them and Lamar an unbiased look at the market for him Ravens aren't reluctant to give Lamar a top QB market deal But hope the non-exclusive franchise tag will speed up their own stall negotiations with him And yeah, that makes sense because Ravens been trying to sign him to whatever they have been and Lamar Obviously ain't been going for it because there's no deal yet So now you can get other teams involved to see what other teams interest in Lamar And what other teams would be willing to sign him for but but Now hold up there, buddy Because yesterday a lot of teams coincidentally started dropping out of the Lamar Jackson race and You know what was funny went whenever you um if you watch a certain genre of Television or entertainment or really anything if you find yourself Learning about a certain subject or topic Something that interests you over time if you are learning about whatever that subject is you're gonna learn certain words That you may not learn if you are interested in something different like yesterday a lot of people Will learn in the word and I mean we've heard it plenty of times before but yesterday was a big day for the word collusion Collusion and looking up the definition of collusion it says secret or illegal cooperation or conspiracy especially in order to cheat or deceive others and Another version of it is illegal cooperation or conspiracy conspiracy especially between a sensible opponents in a lawsuit so a Lot of people were throwing out the word collusion yesterday when coincidentally After it was announced that the Baltimore Ravens were franchise tagging Lamar Jackson, which was and you know I was weird to thought of Hey, maybe I'm not sure if they did this before or not But I felt like it was weird that the Ravens just announced. Hey, we're franchise tagging Lamar Jackson They didn't announce which type of tag it was and I know that's like that's something that they strategically do or strategically did But anyway, um It was weird because right after the Ravens announced they were franchise tagging Lamar Jackson then all these teams coincidentally out of out of nowhere They start saying all these reports are coming out that these teams are not interested or they won't be pursuing Lamar Jackson It was the Falcons. It was the Dolphins. It was the Panthers It was the commanders and it was the Raiders even though there's been a report From Diana Rossini that came out a little bit later after that that said the Raiders actually May like look into Lamar Jackson. Maybe they're gonna explore all that QB option something like that. But anyway, it was just weird and you know like obviously we know owners talk we know owners talk and We already know like Steven Shaddy been came out and said it like that he ain't want to do no fully guaranteed deal That that's not what he trying to do But you know so many of the owners were so heated at Jimmy Haslam and them over in Cleveland for giving that to the Sean Watson um But he still got it He got it Amidst all the allegations amiss not even playing football for like a year and a half two years He still got it And now when Lamar Jackson Who has been playing football for the past five years? He gets franchise tag the non exclusive franchise tag All these teams are just coincidentally just dropping out It's like come on now. We see what it is. It's it's the game and it's a nasty. It's a dirty game We always talk about that how the NFL it's a nasty game Nasty one. So right now it's like it's Lamar Jackson versus the world This Lamar Jackson versus the world and you know like Ravens are so happy right now they're so happy and it's almost like a bittersweet thing because We want the Ravens to keep Lamar for sure but I didn't really want it to happen this way in in a sort of nasty way To where is it because you know, you know Steven Shaddy all them owners talk they talk their owners Their owners they are owners of NFL teams.  It seems like it's definitely some funny business going on um because for teams for teams actually like right right after he gets tagged Right after to come out and and start and start saying that and then all them reports just start dropping Hmm, okay And these are teams that don't have quarterbacks Like one of them like the dolphins they got to a and then shout out to to a tool is cool but The Falcons they ain't got no quarterback. Well, that's marita. They ain't got that quarterback Uh, the Panthers ain't got that quarterback Uh, the commanders they ain't got that quarterback The Raiders they just cut their quarterback So it's like really Now Of course over time Stuff could change situations change. Um, and like my guy, uh, sam the joku continuously said that all it takes is one team All it takes is one team Uh, one team that's willing to sort of buck the system. Uh, one team that's willing to go against the grain Uh, and one team that's just willing to be like, you know what? We'll take them We're gonna go for it So but it was just crazy, man and I wonder what was going on in lemar's hair right now Because again, it is him versus the world and we know, um, the nfl pa they've been involved heavy with lemar They've been involved really really heavy with lemar, but obviously the owners they've been involved with each other and the owners they're powerful And they want to make sure like this whole guarantee contract thing No that it does not go down They they they do not want it to be the norm. They don't want it to be regular They do not want it to be consistent They want it to be anomalies when fully guaranteed contracts happen Why? Because that's more money literally more money out of their pockets Even though they got a lot of money these players make them a lot of money But it's more money out of their pockets And they don't want to do that Another thing too with lemar jackson that they don't want to become the norm either On top of the fully guaranteed contract is a fully guaranteed contract something of this magnitude with no agent Because lemar jackson, um, he can and he still has an opportunity to But he's been a pioneer right now a pioneer that a lot of agents A lot of NFL owners just they don't want him to be a pioneer for that They don't want him to inspire the like players to not have agents because that's taking money out of their pockets Like that's that that's that bread. They like hold up now. Wait a minute. Don't don't do that So it's just it's crazy man, but again, it's the game It's the game. So We're gonna see how everything ends up playing itself out We gotta see and I don't know when it's just It's like now again. Now it looks like the ravens will keep lemar Um, looks like they'll hold on to and which again, like I said, it would be a great thing But just how is being gone about It's just it's just fishy. It's real fishy and one of the craziest parts about it is that Nobody can really do anything about it Though owners are so powerful Nobody can do anything about it Yeah, well, at least I I can't think anything that anybody can do to really like because again player versus owners Like it's pretty much lemar jackson versus 31 other owners Because excluding the browns because they the ones that that started Well, actually the vikings because they gave Kirk Cousins a fully guarantee But that's not the one that everybody's looking at. Everybody's obviously looking at the sean wiser So It's tough It's really tough and it's it's just a situation. That's just It's crazy, but um anyway Back to the non-exclusive tag Um, I know this has been seen as sort of a ravens initially when they put the non-exclusive tag on them A lot of people felt like it was the ravens just showing that confidence like hey anything that anybody offers him We can match it. We can do it. We can make it happen. We can give him the best offer But go ahead talk to other teams but it's like The ravens have already talked to other teams and been like no, no, no, don't Don't do it Don't do it because again all of the backing out coincidentally right after he's franchise Yeah But anyway, um, we'll see how the whole thing ends up playing out Brian McFarland You know Raven salary cap who always keeps us up to date with everything going on with the uh, the ravens salary cap Which we appreciate shout out to Brian McFarland um He said that with the non-exclusive tag This puts the ravens nine mil over the cap um Now a couple of things with that by march 15th the starter free agency the ravens have to be under the cap So what that means is that you will be seeing A lot of this freelancer over the next week Because the ravens need to make moves to get under the salary cap If you're over you you cannot be over the salary cap Heading into free agency where free agency starts when the new league league year begins You have to be under the salary cap. You have to it's a requirement Now after the league year begins you can do whatever and you can you can be over the salary cap, but when it starts You got to be under you have to so that means the ravens. They have some moves to make And what I appreciate about Brian McFarland, um, he lets it be known like uh, some different suggestions Well, not suggestions some different options that the ravens have as far as getting under the salary cap um, some of the potential moves that he listed Were signing the more Jackson to an extension. That ain't gonna happen yet. Um, but restructuring Ronnie Stanley again How many times we don't restructure Ronnie Stanley? It had to be like I feel like it's been like six It probably ain't been that much, but maybe like four Maybe four, but it's been a lot. I feel like that that would always be like with the first contract They go to restructure Ronnie Stanley It used to be Brandon Williams. Y'all know it would always be Brandon Williams They'll always be restructuring Brandon Williams. Um, but anyway, uh, they can restructure Ronnie Stanley restructure Marlon Humphrey Trader release Kalaeus Campbell, even though, you know, if whatever they do, they're gonna bring them back Well, not if they trade them, but they ain't trading them if they release they they gonna bring them back. Well, anyway, um restructuring Mark Andrews Trader release Gus Edwards Trader release Devin Duvenay Trader release Chuck Clark restructure Roquon, uh, signed Kevin Zeilert to an extension uh restructure Tyus Bowser, McCurry, Morgan Moses, Michael Pierce, uh, or release Michael Pierce, uh, or release Patrick Ricard. Whoa Now that's a sneaky one right there especially because What Todd Monke, when he spoke he was talking about how fullbacks are dying For like the the league don't got nearly as many fullbacks as they used to have and he talked about like he sort of Gave a little jab to Greg Roman Talking about a fullback being uh being like mashed up with a lineback or something like that And having to be a weapon and anyway, so we'll see we'll see but The bottom line is the Ravens. They have to make some corresponding moves to get under the salary cap by What is it next Tuesday? I think it's next Tuesday But yeah, so Oh, no the 15th is next Wednesday because today's the 8th So, yeah They they they got to make some moves to get under the salary cap Within a week So, yeah, it's time to get shaking now back to Lamar Jackson real quick. Um Well Lamar Jackson he can begin negotiating with other teams in a week Once the the new league year opens that's when he can start talking To other teams that are potentially interested in him And we'll see again. Well, what which team is going to be that ends up going against the grain Because again all this the public like hey, we know we're not interested. We're not going to pursue Lamar Jackson Even though Atlanta Falcons retweeting the report I said, whoa, okay Atlanta Falcons social media team. Let us know how you feel apparently they did but um next week That's when Lamar can start talking to people So, yeah, again now, uh, it is nice to be in the next step of whatever's going to happen Um, but we still we still got a little bit of a ways to go So but anyway team keep it clean. I appreciate y'all. I love y'all. I always appreciate you all listening I thank you all for supporting this freelancer. Hopefully we just a temporary freelancer, but Hey, everything will hopefully eventually work itself out very soon Now like we said the end of march is big for us because that's when hopefully Um, we when we do reapply uh to be monetized again. Hopefully it can be approved Um, and we could just get back to normal, but I I appreciate y'all still supporting like crazy and just Showing a lot of love. I really do. So thank you. I love y'all and we out


closes in 30 minutes and then it's extra magic hours from 9 p.m. to 11 p.m. for a resort guest. I obviously am not a resort guest but that doesn't mean I have to leave. I still get to see Epcot a little bit less crowded. I just can't go on any rides. So let's go do this. With only a half an hour left in the park, test tracks down for refurbishment. I'm gonna try to get on Soren. I thought I would check to see if there are any fast passes available and let's just see what happens. Nope, there are no fast pass plus experiences available at this time. Bye bye. So hopefully a lot of people are lining up to watch Epcot forever and I can get on Soren with like a 10-15 minute wait. That's the plan. Let's see if it goes that way. And maybe, just maybe, we'll be able to get in and on Soren and off and then head on over to the seas in time to see Nemo swimming out to heat. The time is not in our favor though. It is 8.35. We have 25 minutes left. This is gonna be a close one. And sweet. Soren is only a 15 minute wait. This is not no 15 minute wait. There is nobody in line here. I think we might have lucked up. The Soren music just makes me feel like I'm about to do something very important. Like I feel like honor and integrity as I walk down this ramp. Somebody asked me to describe Soren. I would definitely say it's an exhilarating gliding adventure that includes dramatic drops, turns, swoops and lifts. I think that is pretty precise. And I definitely would not recommend it to those who have fear of heights. I also politely asked for a B because I don't want no leaning eye full of tire. I don't know. I don't think we're gonna make it guys. 8.46. We haven't even got on yet. Thank you. Oh yes. Favorite seat. Make sure you check your seat belt. Seat belts go left to right and then prepare to fly. Four minutes to get over to the seas. But I have something important I have to say. And I don't know if I should just say it later or if I should just try to get there. I don't know. I don't know. I don't know. He's got the same idea. Okay I might as well tell you what the important thing I was gonna say was because I don't think I'm making it to the seas. I have a minute. That's not happening. But are they gonna redo Soren?  So they're gonna have to updo that right? They're gonna have to. And in a twist turn of events as I was leaving the Lampavilion I ran into some friends who were actually staying on property and I was telling them how I was gonna try to make it over here but I ran out of time and they said that's okay and they actually brought me over and they let me go through with them but then they left because they don't want to ride the seas. They said that they wanted to ride Soren real bad. So thank you guys. I appreciate you and now we get to see Nebo swimming out to sea. I'm sure when it comes to extra magic hours a lot of people aren't flocking over to the seas. As you can see the queue is a little bit empty.  In a big blue world it's okay because no one's in line. This one? Thank you. Seriously I'm gonna be doing this alone guys. Nobody here. I like it. There he is. Well that was nice but what do you think about doing turtle talks in some in here? I mean do they even do turtle talk if there's nobody in the Ampute Theater? I don't know. I'm gonna find out. And yeah they do do it. The next show is at 9.35. There's only two other people in here with me so I think I'm gonna look at some cool fishes and then come back and see how much more interactive it is with the less people. There's nobody up on the upper levels so we get to look at the dolphins. Well look at there's one right there. You see him? Here he comes. Come here now. Look at that. Wow this is really good to be able to just explore in here without a lot of people. I'm linking this. Well there's the dolphin. Look at him go. Hey buddy. Come back. I want to be friends. Oh I don't think they like me. But look at this guy. We gotta get back to turtle talk. They're calling last call. I hear them from up there. Five minutes. Oh now we got a crazy, crazy stingray here. Holy moly. It's the crazy stingray right there. Here's another one. They're crazy. Well we got a couple more people here actually. Why don't you look at that. I don't think I've ever sat in the front row for a crush. This is pretty fun. I'm excited. Two humans and a human tank. Crush. Check this out. Hatchlings Gromit Off-Spring Chillin Sub-Level. Hey let's talk to the dude chilling ever on this side. Yeah hang it on the white show. Hey bro. Bonus. Answer the question. For Squirt what does a human do? At a beach. Shout it out. Swim. No lie. Who just said swim? Wave that fin if you said swim. Bunch it. Watch out for the glass dude. Thanks Hank. How long has that dude been there? Dude. Well that was fun and actually a couple more people showed up than what there was in the beginning. Even though there wasn't a lot of children it was still a very interactive show and I think that's awesome. Well I guess we'll head on over to the other side of future world. But that was really nice that they let us on finding Nemo. Thank you guys again. I appreciate that. It is now 10 o'clock and there's still an hour left of extra magic hours and look at this. This is what I'm talking about. I love the parks when they're like this. It's like a dream come true. It's just nice relaxing stroll. Stare at spaceship birth without worrying about someone running up behind you. It's a very relaxing feel. Well look at that. A Disney rabbit playing in the grass. Look at that little guy. How you doing? I also wanted to come over here because I heard they opened up and actually took down some of the walls around Guardians of the Galaxy. And they definitely did. Interesting. Look at that. You can actually just see right in there. That's really nifty. Oh man. And I'm not sure why they have it roped off over here. Just a big bunch of open land. And that big beautiful spaceship earth. Look at her. Gorgeous as ever. I was just walking and look at this baby rabbit. Oh no. I hope it finds its way back to its mom. Look at this little one. Once the mom rabbit just comes out and attacks me though. Look at baby rabbit. Come on. Let's go. There you go. Come on. Save passage. I think that's the mom rabbit. It is giving me some very very dirty looks. The electric umbrella is still open though. That's really awesome. I didn't know they kept this open for extra magic hours. I like it. I think the thing I'm going to miss the most about the electric umbrella. The talking trash cans. Oh yeah. Going to miss this guy. Maybe they'll actually keep the talking trash can though. Who knows? I mean it's kind of cool. Look at that monorail shot. Beautiful. What timing I say. I feel like this is like a very odd thing to see actually. Like never. I mean unless you're like here until very end but there's still an hour left. There's still an hour left until extra magic hours is over. Nobody in the breezeways but still a gigantic line for this photo opportunity here. I think I actually might wait. I mean why not? What better time now? I can't do any rides so hey. Hey. I have no idea how those pictures came out but I will put them at the end of the video which is right now. Because it's 11 o'clock. It's the end of the night. So love the life you live. We'll see you next time. Bye.


Hi everyone, Joe for jasperjasecasebrakes.com coming at you with 2020 Tops Clearly Authentic Baseball brand you released just dropped yesterday This is a 10 box break half case from a fresh case. That's random team number nine as You've seen before the combos are the dime backs in Marlins, and we took out the pirates no pirates on the checklist So let's roll it. Let's randomize it two and a six eight times for each list Oh, I got to double up your names right here, too. One spot gets you two teams So eight times for each list one two three four five six seven and Eighth and final time after eight. We've got Adam Harper down to Adam Harper eight times for the teams two and eight After eight, we've got the Nats down to the shy socks All right, Adam with the Nationals Ricky with the A's Dustin with the Rangers Nick with the twins Nick with the Nick K with the Giants Dustin of the Diamondbacks Marlins combo Adam with the Mariners Ricky with the Reds Dennis He got my Dodgers Donnie with the Rays Adam with the Orioles Darren with the Astros and Mets Adam with the Rockies Dennis with the Indians Clint with the Padres Adam with the Tigers Dustin with the Cardinals and Phillies Clint with the Red Sox Dustin with the Angels Donnie with the Braves Royals or sorry with the Braves Darren To DRs right there Darren Redding with the Royals and Cubs Nick T with the Blue Jays Nick K with the Brewers Dustin with the Yankees last spot mojo and Adam with the Chicago White Sox I'm gonna alphabetize by Team name and while you're considering trades. I'm gonna pop open this case and see which half we're gonna do So I'm gonna switch from this list for just a second And feel free to feel free to trade away All right, so there's ten on the left side ten on the right side We're gonna select a die Let's select that one right there one two three for the left side four five six for the right side And it's four one two three four five six. So this we will save for for next time Which I think is not too here. We'll just put X's on here because I think Break ten is just gonna be it's just a few spots away. These are pretty quick breaks, too So we can rock through these pretty fairly quickly There you go. All right, let's keep those back there because I'm sure we'll do another one of those no trades No trades. So let's print and rip So TWC trade window closed Let's flip back to the screen right here The final print out right there first one out of the gate is Gonna be Aracisa Kino 17 out of 75 Finally getting some baseball back. So the nice to see What he's gonna do this season keep that on the right side there that is for Ricky Holbert and the Reds We've got a bash brother Jose Canseco for the A's Nice that'll be for Ricky Holbert All right Ricky good start Good start. You got ten out of ten I don't know if your friends in the in the break with you would be very happy with that All right next one is six out of fifty Tim Anderson White Sox Ricky Holbert. Ooh Close he has the Reds Chicago White Sox Adam Harper. There go. There goes the run all right Still a lot of boxes to go nine for ten maybe 900 batting average I'd be wild We've got Juan Soto nice 30 out of 75 on That one that's Adam Harper in the Nats. All right now. Maybe an Adam Harper streak We've got Kyle Hendricks Chicago Cubs Darren Redding on the board this time Ricky what's up, and we've got Abraham Toro Astros That'll be for Darren Redding Doing well Ricky the crew keeping us busy here, so that's good Remodeling the shop a little bit and getting prepared to invite some people Back to the shop We got for the Dodgers Max Muncie That's that's for Dennis who has my Dodgers nice Yeah, these are pretty good-looking cars are in age And I want to say that The design is pretty pretty what we're expecting to see but I feel like the checklist is stronger this year At least the hits were pulling a stronger this year We got Joey Votto red ink autograph one of one That is nice Ricky Holbert with the Cincinnati Reds All aboard the big hit express Two more to go second half in the store folks. Yes, these case breaks dot com It'd be a hot case Next up is Bert Blilevin 1970s decades best That's Nick T and the twins There you go Ricky There is a nice Irish pub on the pier All right, and the last one boys and girls it's gonna be Cardinals Tommy Edmond That's 33 out of 75 going to Dustin Colley and the cards Nice cards here boys and girls. Thanks for watching. Thanks for breaking with us. I'm Joe for Jasper's case breaks comm I'll see you for the next half. Bye. Bye