 Good morning everyone and thank you Kelsey for that amazing intro to wasm day and What all this is about now? I am not entirely sure where I fit on the spectrum Kelsey Explained because I I think I have to talk to him more about What all of this means exactly to fully understand it? It's kind of interesting the schedule says that I will talk about new foundations for Building software, but this is a keynote. I have five minutes. So I'll not actually talk about anything really foundational That doesn't make sense Instead I will talk a bit about the why why do we need new software foundations? But even that would Blow way past five minutes. So I will focus on one Specific reason One that none of us will be able to afford to ignore now as reasons go this I admit is kind of on the big side and It's also a bit of a strong claim But then again, I think you all often all of you Really kind of know this to be true and luckily we have a shield against this Almost all software whether open source or commercial is provided under licenses or ULAs that try to minimize Or where possible exclude any sense of warranty and as fitness fitness for purpose any security and so on But this shield it's going to go away Both in the EU and in the US there are legislative initiatives that Make it so that all of us will have to take a lot more responsibility for the software we are shipping Not to put to find a point on it Would you be willing to bet let's say 15 million euros on the security of your application? Or if you work for a very large company, maybe billions of dollars off your revenue every year I don't know but that if the EU is having its way with the CRA the cyber Security resilience act that might become a bet you must be willing to make Now this is all in flux and we'll see how exactly it shakes out But one thing does seem pretty clear this Provided without warranty that shield It's not gonna last much longer Now a lot of a lot is being done to address the security of our applications Impressive amounts of resources are poured into securing the supply chain, which is certainly a good thing given how good we've become at reusing code and Our industry wouldn't be remotely as productive if we hadn't developed amazing ways to do that I'm a bit concerned about the Significant increase in cost that all of this entails and that it might actually slow us down But let's say it works out perfectly Let's say all of our supply chain is magically perfectly secure. We can kind of forget about it We still have to contend with that remaining bit of code the code that our teams write themselves our first party code that code is very often written by Domain experts who have deep expertise in a specific field But not necessarily all the expertise required to build a larger application to make it secure to make it reliable If you allow me the Admittedly bad analogy for a moment. Let's compare building an application or a process to building a house Imagine the person Installing, I don't know light fixtures painting the wall setting up a piece of furniture Would also have to know a really large amount of information about structural engineering or blocks or plumbing because just in the course of doing what they are doing of rolling out a carpet they Could accidentally make the building collapse or they could Make it so that the lock to the front door is twivial to open or Well, you get the picture That is sort of the Situation we have with how we build software where the units of isolation are so broad that We have these really diverse teams with really diverse sets of expertise Building pieces of functionality that are all put together Into a unit of isolation can all affect each other and can all Make it so that for example the security of the application is fundamentally Impinged Now even if we could hide behind the shield, there's no warranty provided shield. I think we should fix this I think we should improve on it But we should do it in a way as Kelsey said that makes it so that we can continue Developing with hype productivity that we can take the millions of developers with us and their languages and that we can migrate to Gradually, otherwise it will not work. We cannot regret the world. I Helped found the bike guidelines and I work at fermion because these organizations are really focused on one possible answer the component model And I believe that we have the right answer to this. I believe that we can fix these issues and do so in a way that increases productivity instead of increasing costs and has all kinds of other nice properties if you want to talk more about all of this then Find me and my colleagues at the fermion booth square on kubecon or also At the happy hour. We are hosting with docker tonight But right now I don't even want to sell you on any specific solution. I mean I haven't Told you what the component model is at all so I'm not doing much selling here instead I wanted to drive home this point that there is something that you just cannot ignore that nobody can ignore here We have to fundamentally change how we build software But also I do want to encourage you to just focus on just absorbing all the amazing stuff you'll hear about today and The cool and fun things people will present and I hope you have a fantastic wisdom day and a great coupon. Thank you