It's close to the end of the day. I hope you had a coffee. So my talk would be interesting, because it is indeed one of the, you know, the title is JavaScript in WebAssembly. Why would you have JavaScript in WebAssembly? So it's really why and how. So let's talk about why first. So when WebAssembly first came out, it was designed to run side by side with JavaScript. That's how it's get started. So in a browser, you would have a JavaScript interpreter or JIT JavaScript engine like V8. And then you would have a WebAssembly runtime. And they communicate through something called Watson-by-Gene. It's for Rust. And you could also have a C-based bridges. That bridge between WebAssembly and JavaScript. So the idea really, when WebAssembly was invented, I think it's almost 12 years ago. It's hard to believe it has been that long. The idea is to run native application in the browser. So we know that we can run JavaScript in the browser. But there's a whole bunch of applications for various reasons are written in C, C++. And we want to compile them and run them inside of the browser. And obviously, we can't just run compile native coding browser. So WebAssembly was invented as a security sandbox or as a sandbox format for that purpose. So while the Chrome achievement actually happened early this year, Photoshop says they have compiled the Photoshop application written in C into WebAssembly. And you can run Photoshop in the browser. So that's how it started. WebAssembly originally was designed as a supplement to JavaScript so that you can run native application in the browser. But how it's going, I think the evolution of WebAssembly has strong parallels of technology evolution in the past. Something started from the browser and then moved to the server side because it becomes 10 times more front-end developers than back-end developers. So people learned, front-end developers learned it. And it's become standardized and supported by the two chains. And then it becomes a back-end technology. So I think if you're old enough like me, you would remember that's exactly how Java got started. It used to be the applet and the serverlet. It's also how Node.js started. It used to be JavaScript. JavaScript used to be exclusively on the browser and then it becomes a server side technology. In fact, when people start to use Node.js to develop a server application, so we're all like, this is impossible. This is the wrong way to do it because JavaScript is a single-threaded execution environment. How can you possibly do a server-side application using a single-threaded execution environment? WebAssembly is moving, going through the same evolution or the same process. So that's how we see the direction it's going, is that you would have a VM or a runtime and it can run JavaScript applications and other applications inside this VM. So this is not necessarily as a supplement to JavaScript, but to run JavaScript inside WebAssembly. Of course, there's lots of engineering work that has to be done and a lot of developer APIs that has to be developed, which would be the focus of my talk. So all those plugins that plug into the JavaScript interpreter or JavaScript runtime that's running inside the WebAssembly. But it still has an answer to it. So this is an article that we wrote that's how to run in JavaScript inside WebAssembly. But with all this, we still have an answer to why. People look at that and say, why would you want to do that? I get this question all the time. It's because when we use WebAssembly on the server-side, we want to make it a container. There was a famous saying back in 2019, is to say if WebAssembly was invented in 2008, then Docker wouldn't be invented. And Docker's founder said that. So the world that we are envisioning is really to make WebAssembly much more like the JVM of the past. And the Docker container of the more immediate past is to make it into a runtime that can stand on its own instead of just a plug-in mechanism for other platforms. WebAssembly has been very successful to act as a plug-in mechanism for other platforms. So for instance, in the browser, you don't use WebAssembly by its own. It's always interacted with the JavaScript runtime with, in some capacity, because it doesn't have its own network support. It doesn't have access to the file system or other parts of the operating system. So you use WebAssembly to do compute. And then when the result comes back, you use JavaScript to render it. So in the browser. And another big WebAssembly use case is on the blockchain. It's the same. So you have the consensus mechanism and all the platform being built. And you use WebAssembly to do one thing around smart contracts. So the smart contract thing is really, in my opinion, is what serverless functions should look like to begin with. Because it's a piece of code that you write or anyone can have where it can be, have bugs in it or have bad intentions. And you submit it to a network. You don't care whose computer is running it, whose node is running it. And but somehow, you're going to get the correct result coming back from the network. And you pay for each execution. That's, in my mind, at least this is what serverless computing should look like. But in that context, WebAssembly still runs as a plug-in mechanism. So you have a much larger platform that isn't built. And then you use WebAssembly to, I would say, an important but small piece of work that is doing the computation. I do stateless computing in particular. But our vision for WebAssembly, at least, I started the project Wasm Edge, which was a WebAssembly runtime in CNCF. So we have always wanted to make WebAssembly more like the JVM or more like the Docker container so that you can run an entire stack of software, including the networking to use WebAssembly to create, say, microservices, where you can call out to other servers and you can respond to other services as well to make WebAssembly to do AI inference, replacing the Python layer of AI programming using Rust and compile that into WebAssembly. In order to do that, we need a WebAssembly runtime that is more encampmenting. And the benefit of that is also very strong, because by using WebAssembly as a container format, one of the things I learned from this conference is that there is a huge focus on cloud security and software supply chain security issues. I'll leave it there. That's in this conference, right? And WebAssembly is really one of the, I think, at least from my point of view, is one of the leading candidates that can help with those security issues. Because if you have Linux container, you essentially have a very wide attack surface. You have, because you are running Linux, you could have SSH turned on and not knowing it, right? So there's lots of issues that you have to deal with. But for things like WebAssembly, you can really lock it down. It has a very tiny attack surface exposed. It has a very simple software supply chain, because you compile everything into a single bytecode and run it. So there's many, many benefits of running WebAssembly as its own container format or as its own runtime for microservices. And we can make WebAssembly to be fully OCI compliant, which is the graph that I draw on the other side, which is the green boxes are the things that we already implemented and support, is to say, I can build a Docker image that has only one WebAssembly file in it, and then publish it on Docker Hub. So if I use Kubernetes to run that Docker image, it would say wrong format. It would complain, because it doesn't see Linux in it. However, by changing at the OCI level, at the OCI runtime level, by changing C wrong and C wrong, so we are now already merging into the upstream of C wrong, I can make the runtime aware whether this is a WebAssembly runtime or a Linux runtime. And if it sees a single WebAssembly file that in the Docker image, it would know to invoke wasm edge to run this WebAssembly file and run all the services and applications in it. So by making that change, because Kubernetes is such a really nicely layered system, so it can work with container D. It can work with all the CRI runtimes and the Kubernetes applications and everything about it. So our idea has really been, we want to use WebAssembly as a security sandbox and container to run microservices side by side with other OCI, with Linux containers and VMs and things of that nature. So in order to do that, we have to support JavaScript, because a lot of microservice developers, we can't tell people you have to use Rust to do that, although I love to tell people that. But in reality, maybe 90% of the developers are using JavaScript or languages of that nature. So in order to make it widely applicable and to make it widely adopted as a microservice runtime, we would have to figure out a way to run JavaScript inside WebAssembly. Because now in order to run this whole, because the whole value proposition is this is a container. It contains everything that runs in it. I can't have a lot of things that hanging around it, those VAs or something like that, that hands around the WebAssembly runtime and give people a big binary. And to say, just run this, I have to put everything together as a container, and then it runs WebAssembly bytecode. So in order to do that, I think that is the primary driver of trying to run JavaScript inside WebAssembly, is to say, I want to write microservices. And the microservices is completely contained within the WebAssembly runtime. It's managed by Kubernetes, like a Docker container and a VM that exists in the same cluster. So this is why we spend so much time trying to run JavaScript inside WebAssembly. So there's lots of use cases. There's a, yeah, so I'll go over them just very briefly. So there's many cases where you want a microservice that is managed by WebAssembly instead of a Linux container. Today there's lots of microservices that are managed by Linux containers. Those are long-running services that needs the full capability of Linux. However, you can have a lot of services that's transactional in nature, or it has to live on the Edge Cloud, on the CDN network, or it has to be run on an Edge device. For instance, the example I always give is say if you have a door camera. The door camera has taken a stream of pictures. And one of the things that you don't want it to do is to send every picture into the cloud to recognize it, because there's lots of privacy issues. And most of the time, it's people you know. It's your family members and things like that. Only in a rare case, it would find a stranger. And in that case, you should recognize that. And it's a new alert. So there's a lot of benefit to do it on that device, although the device may not have that capability. So do it in your home, in a server you install in your home, like in a setup box, or in a NAS. And if you're buying that to go to an Edge data center, that's something within your city to do it. Instead of going all the way to the internet and get processed, you don't know where it is. So for cases like that, I think those are the sweet spot for, say, web assembly-based microservices. That's because those services can be programmed and executed in a very efficient manner. And ideally, people want to use JavaScript to do that. They don't want to, at least at the stage where there are not that many Rust or C++ developers who can, who's available to do that. So that's the use case. Well, so for the rest of the talk, I will talk a little bit about how we did it. So the basis of implementation is also simple, and it's built on other people's work. So there is a wonderful project in the community called Quick.js. It's a very compact JavaScript interpreter. It's written in C or C++, I forgot. But it so happens it can be compiled into web assembly. So now we can have a JavaScript interpreter that's understand all the JavaScript syntax in the language and run it inside the web assembly. And with that, I can feed that interpreter another JavaScript file so that that JavaScript file can also be executed inside the web assembly. So that's really the basic idea. So you can see it does basic stuff. That's, it does understand JavaScript syntax and it can run the JavaScript program. However, when I tell people, we now support JavaScript. People immediately take an existing JavaScript application and try to run it in the most 99% of the time it failed. Because JavaScript has such a big ecosystem, you can't just say, I can do pure JavaScript or standalone JavaScript program. Most JavaScript applications out there have some, depend on some kind of other modules. So you all have to support other modules in your runtime as well. So this is the work that we did that's to support ES6 modules in our JavaScript runtime. So this example, if you're interested, you can look into the code. But it's not, it's just a very, I mean, a demo that shows how to define a module and how to call the module. Of course, the JavaScript ecosystem has more than ES6. So we went ahead and supported Common.js as well through the row up.js, right? That's it allows you to, what's the word they use for this? It's not cross compile, but row up. So it figures out all the dependency of your JavaScript application and download all those modules and combine them into a big file. And then you just execute that big file of JavaScript. So that solves the Common.js modules support problem, right? So Common.js, NPM, and ES6 can both be supported with this, with the runtime that we have built for web assembly for Wasm Edge in particular. But we should not stop here because one of the great advantage of web assembly is its performance. And if we introduce a Java interpreter and just stop there, then the performance would really suffer because the benchmark or the leading JavaScript engine is V8. V8 has, I think, 15 years of optimization and thousands of PhDs that's working on that, right? So it's impossible to exceed the level of GIT optimization and performance that's being achieved there, right? So to have a simple JavaScript interpreter, you would have the problem that people would say, it's nice to run it inside the web assembly and have those security and footprint and start time benefits. Those are orders of magnitude better than, say, running Node.js inside a Linux container, right? However, you don't have V8. So at runtime, you are three times slower. So that would be unacceptable. So one of the things that we really wanted to do is to take advantage of the multi-lingual or the ability for web assembly to support multiple compiled languages. So the solution that we come up with is really to build a Rust API that allows Rust developers to write JavaScript APIs. So the idea here really is that if I want to perform something like AI inference or something that takes a long time to complete, I write this function in Rust. However, there is an API that allows me to expose it as if it is a JavaScript function. So other developers come in, they can just call that JavaScript function. And the system knows how to route it to the Rust application that the compiled web assembly and then execute it in a much more efficient way. So I think by using that, we can increase the runtime performance of a lot of functions by a large margin. Because essentially, this is how Python does machine learning. That's when people always say Python does machine learning, but it's not. That's Python. Most of the heavyweight machine learning stuff is passed to the underlying C++ library. So if you just have a pure Python interpreter environment, you actually cannot run TensorFlow or anything like that. You have to have C APIs plug in there. It's the same kind of ideas. So you have compiled language and high performance language that allows system developers to develop those APIs and then present them. As if they're JavaScript APIs, so that JavaScript developers can use them. And based on this idea, there are a couple things that we did. So for instance, on Wasm Edge, using JavaScript, now you can invoke other web services or you can create a server that responds to inbound requests. Using non-blocking network IEL, meaning that's, although it's a single-threaded environment like other JavaScript environments, but it's non-blocking. So there's a scheduler that can schedule things around. So you can have multiple connections at the same time while it's waiting for each of them to finish. It can accept more connections instead of blocking. So here are some coding examples that's making an HTTP request and getting an HTTP response. And the way that we implemented that is through Rust. So we write a Rust program that we also have a socket API for WebAssembly by supplementing the WebAssembly's WASI standard WebAssembly system interface by giving it ability to handle sockets. And use a Rust to access that layer and then expose this Rust API as JavaScript API that allows people to write applications, programs like this. So a program like this should be very familiar to JavaScript developers because there's no Rust here. There's not even WebAssembly here. As far as they're concerned, I'm writing a JavaScript application that does some kind of server or HTTP kind of operation. And I can package it as a web service and enjoy the benefits of all the WebAssembly container formats that give me security, like footprints, the startup time, and all that stuff. So here's one example.  It's a fetch API. With fetch, you can do a lot of interesting stuff. For instance, you can do server-side rendering. You can have a React application that's rendered on the server because it can fetch all the data from where the page is being rendered. But in order to do that, in order to do that on the server, you need the server-side stack to be able to access other network protocols, access of database, and access other web services. So we implement that as well. And then there's another use case where I thought it was interesting is that we have built a WebAssembly extension that interacts with TensorFlow. So it's pretty much like what Python does, right? So you have Python, the interpreter, and then the TensorFlow library underneath it. So we replace Python with WebAssembly. And for inference only, right? So we have a, so that allows people to write a Rust application that interacts with the underlying TensorFlow library so that it can run TensorFlow models to do things like image recognition and things like that. And on top of that, we package that Rust library into JavaScript APIs. So here is just an example. I think it's fairly straightforward to understand. It's just a really image, input image, really image. And then define the input cursor tensor to say what is the input format of the model? How do I structure this image? And then run through the model and then it gives the results. So we have a demo on our website. So it's give it a picture of a hot dog. It could tell you it's a hot dog. So it's a very typical mobile net demo. So that's also ties together. That gives a very simple JavaScript API to do AI inference. It's hence, it's the example that I have just mentioned, the facial recognition. You can see it can be done this way, right? So a JavaScript developer wouldn't be able to write an application that does facial recognition from a camera. And underneath it, it would take advantage of all the TensorFlow. If there is GPU, it can use GPU. And all the data preparation is done by Rust. But the API stays JavaScript. So that's the developer would be able to, you know, the application developer would be able to use a very simple API to build their service, to build their microservice for H devices, you know, things like that. Yeah. So, you know, here's a more complex example. You know, we can do actually the four React 18 streaming SSR, you know, React 18 allows a way for the entire UI to be rendered on the server side by executing the JavaScript that meant for the browser on the server side. You know, it's called isomorphic application web programming, right? You know, meaning the same piece of code that can run on the client side and on the server side. So, you know, we have completed this demo to show that this thing works fully from end to end. You know, that's so, you know, our JavaScript engine can handle a complex use case like that. So, yeah, this is a demo, you know, that's, you're interested, you can look into that. But there are more, you know, that's, you know, so we have done all this. However, you know, we have also encountered a lot of issues. You know, that's what are the issues that we have encountered? You know, that's, it's one way to start to tell people that we support JavaScript. People immediately get an existing JavaScript library, like I said, and try to run it. However, if you look at the JavaScript libraries that's out there, maybe, especially on the server side, maybe 90% of them use some kind of Node.js API.  That would, you know, that would cause issues on our end because we only know JavaScript. We don't know Node.js APIs. So there's a big community effort that's going on with, within the Wasm Edge community. And I'd love to have you guys contribute to that or, you know, it's our GitHub repository is issue 1535 and we have a long list of JavaScript APIs that we need to support in our runtime. And some of them, you know, they each have different priorities. You know, that's, we have one's, priority two is the most important ones that we need to support immediately. And we have also, some of them, we can use other JavaScript to polyfill, right? We can use JavaScript to implement JavaScript. But quite a few of them that we have to drop down to the operating system level, meaning that we have to use Rust or C to implement them and to supplement the runtime in order to support them. So, why call it the community effort because we are working with the Linux Foundation's internship program. So we have four summer interns, they are graduate students and they are working on different aspects of this. And, you know, so hopefully by the end of the summer, you know, by, you know, the next conference we would be able to say that we have full support of the Node.js API. So now we should have, by then we should have a much more complete, you know, JavaScript story because most of the JavaScript libraries would be able to run, you know, on a multi-managed platform. So, you know, that's, but that's also something we would love to see, you know, more community engagement and, you know, come to our GitHub and tell us what you want to see and whether this approach is right or wrong, you know, or, you know, what are your favorite JavaScript libraries that you want to see that runs inside the WebAssembly and we can figure out what API it uses, right? And then prioritize the kind of APIs or whether it's, you know, Node.js or something else that we can support, right?  So, well, that will have went through all the, you know, implementation, I think, ideas and, you know, and the need, right? You know, that's, so I have one last topic is QuickJS versus V8.  You know, but, you know, so the first objection really is that QuickJS is much slower than V8, especially with GIT turnout, right? You know, however, like I said, we believe the key bottlenecks can be improved dramatically, including stream processing, including AI inference, including things that are really takes a lot of time, you know, because if things only take like five milliseconds, then being three times slower is not a big deal, it's 15 milliseconds. However, if something takes close to 100 milliseconds, then being, you know, 10 times slower would take about one, four seconds, that would be bad, right? You know, so we try to identify those performance bottlenecks and implement them in Rust, and try to improve JavaScript performance in our runtime this way. And the second thing I think that speaks to the benefit of QuickJS approach is that it's much smaller than V8, especially if you consider V8 is not a container, so V8 has to be run inside Barker or inside Linux container, that would give you like one gigabytes of footprint, you know, that's because you have to have the Linux libraries and, you know, things of that nature put in there. And WaterMage with QuickJS is like 10 megabytes or less, you know, so that is a very big difference in terms of footprint. And we'd like to believe, or we'd like to say that QuickJS in WaterMage in a WebAssembly container is safer because it's a smaller attack surface, it's a simpler supply chain, and the WaterMage runtime is designed to be a security sandbox, at least in the browser, right? So in fact, you know, V8, which JIT turned out, has become problematic on the server side, you know, that's, I think a lot of people know that because, you know, one of the fundamental problem is that V8 is fundamentally designed for the browser. So if some issues that only happens on the server, you would have, it's, you know, the V8 team say that's, you know, it's not a priority for us to fix that, as a which I can completely understand, you know, that's because, you know, the most important thing for them is to make it run better in the Chrome browser, right? You know, so on the server side, especially in large computing density environments where you have to run a lot of other people's code, we believe WebAssembly is, we argue for that, WebAssembly is a better security model. Yeah, so of course then the last thing, quick jazz in browser image is more manageable, it's because we can do OCI compliance, we can have full integration with Kubernetes and the other, you know, contender tools like contender D, CRIO and all those, we have experiment, no, we have tested and validated that they can load, you know, WebAssembly files or WebAssembly basic images and have them run in the same cluster with, you know, so our ideal world is you have one cluster that runs the VM, the container and WebAssembly runtime, so all three things can be run side by side, depending on what type of task you want, you know, so WebAssembly would run, say computational intensive, but transactional in nature tasks, right, you know, and the Linux container would run long running tasks and the VM would run high security tasks, you know, so you can have, you know, that would give, you know, I think it's ops people a lot more flexibility to do those things, yeah. Well, so there are, of course, you know, that's the approach we just talked about is our approach. There are other ways to do that, you know, so there's, Mozilla has their own JavaScript runtime that's called SpiderMonkey and there is a major effort to compile SpiderMonkey into WebAssembly and also have a Rust interface to that, so that allows it to do everything that's, I have just shown, but in a different WebAssembly, in a different JavaScript runtime, you know, so instead of Quick.js we can do SpiderMonkey, we really look forward to that because SpiderMonkey has GIT in it, so it could really improve performance, you know, although it could be bigger than Quick.js, but it would be super nice to offer the community's choice, you know, whether you want a larger footprint, but or you want faster performance, right, you know, so that's one thing. And then Shopify has a project called Javi and it's a Rust wrapper around Quick.js, which is also similar to our approach, but it's, you know, that's where we say Javi is more of a runtime independent approach, you know, so it's trying to conform to the WebAssembly standard only and we do a lot of our own extensions to WebAssembly runtime because we are, you know, because our project is WebAssembly runtime, so we try to optimize it for the use cases that we identify like running JavaScript, right? So, you know, so I think that would be the difference, so I think Javi would have less capability than the things I have just demonstrated, but it's gonna run across different WebAssembly runtime so it has better portability, so yeah. And then the other approach that we have been experimenting with and I would really love to hear the community feedback and to see if anyone wants to do it is to use V8 as host functions, meaning that's a cam occasion, but at the bottom you have WASI that goes to libc, you have, you know, the AI inference stuff like TensorFlow that goes to the TensorFlow library and then you have JavaScript in execution goes to V8. So this is also something that we are experimenting with, but, you know, we are open source project, we'd love to, you know, I'm talking to researchers and students and developers and try to convince them to do this, right?  So, yeah, that's the end of my talk, yeah, that's, thank you very much for your patience, that's, you know, you know, late afternoon today and if you have any questions, you know, I'll be back in a couple minutes, that's, you know. Yes, please? Yeah, so let me repeat the question. So the question is how exactly it works, how different components fit together, right? You know, that's, so it's, the way it works really is that, you know, so you have Quick.js that written in C and Quick.js compiles into WebAssembly and Quick.js, and then we have a Rust API that is, that is compiled with Quick.js, okay, but access the plugins that we build into Wasm Edge, you know, meaning to access the networking, the file system, the TensorFlow and all that stuff, right? So what you would get is the Wasm Edge container and the WebAssembly module that runs inside it. This module is the JavaScript runtime and then I feed it with a JavaScript file, right? So the JavaScript file is a text file that's passing as a parameter to this module and so from the top all you see is Wasm Edge. So when you start Wasm Edge, let me show you the command line, I think. Yeah, so this is how to use Wasm Edge on the command line, right, you know, there's many different ways to use Wasm Edge, so at Wasm Edge, so it's the Wasm file is Wasm Edge Quick.js, which is the Quick.js compiled Wasm Edge, okay, and with the Rust API already bundled in it, and then you pass another parameter, it's called holo.js, which is a, you can pass that as a string or you can pass that as a file and so the Wasm Edge loads the Wasm module first and then from the Wasm module it loads the JS file and then it loads the rest of the parameters. It's execute that JS file inside this module, so there's only one Wasm runtime that's involved in here. Yes? Oh, yeah, so that's in our documentation, you know, that's, it's a Rust compile, it's, so this Quick.js, we have a Rust wrapper around it, so it's presented itself as a Rust project, so you build it with Quick, and but say the target is Wasm instead of a CPU target instead of ARM or X86, you know, so it would, and so the build artifact, the result is a binary file that start Wasm, you know, so basically. Yeah, so there's something that's, there are things that already build in, like the networking stuff and you know, everything I show, they already build in here. However, if you want to add your own, you know, that's using Rust to implement your own JavaScript API, you would have to fork that, that's a Wasm Edge Quick.js project and there's an extension folder that put your Rust code in there and compile it into WebAssembly again. So that's also one of the interesting things about WebAssembly is that it always produce, or at least at now, you know, I think there's a lot of talks about, you know, dependency modules and you know, things like that, but at least for now, it produce a single executable binary and so it's really easy to determine, it's a supply chain, you know, it's so what goes in there, you can fairly easily analyze it, yeah. Okay, yeah, please. So one last question, please, yeah. So the question is, what's the difference?  You know, one is the implementation is different. You know, Wasm time itself is implementing Rust. Wasm Edge is implemented in CC++ and it has many interfaces and Rust is one of the interfaces it provides, right? We believe, although we are in the Rust community, so a lot of people keep asking, you know, why don't you do that? It's strongly reminding me though, days of Java communities, they always ask, why don't you rewrite this in Java?  You know, that's, you know, but from our point of view, because we want Wasm Edge to be more adapt to edge computing, so we want it to be in places where, you know, where the Rust 2 chain may not be so well-established. For instance, on RISC-5 CPU, inside the Intel TEE, you know, the Intel SGX, and you know, that's sort of hardware environment. And also in non-linear operating systems, like, you know, like we adapted to CELFOR, which is a real-time operating system. You know, that's, so there's a lot of those places and open harmony. You know, there's a, there are a lot of those places where the Rust 2 chain may not be that well-established, but we still want to compile the runtime, right? You know, so that's one of the reasons. And another reason, of course, I think the community need diversity in terms of web assembly runtime. You can't have just one web assembly runtime, and if there's a bug discovery in there, and then everybody breaks, right?  The second is the features. You know, I think, one time I think it's a, it's a bytecode alliance project. We are a CNCF project, right? You know, so, we take, you know, our philosophy has been built first and see what becomes a standard. You know, we don't try to come up with a standard first. You know, so, for instance, our contribution to WASI has been, we have been trying to, you have seen all the experiments that we have done, and none of them are current standard. We want to see what's the community going to adopt and then try to push them as standard, right? You know, so, one of the issue with the standard first approach, however, you know, that's, we have seen that work clearly from, from the early days of Java, you know, when there's EJB versus Spring and, you know, all that things, you know, and today, you know, one of the big frustrations in the web assembly runtime community is that, say, networking capability in web assembly was in socket has been lagging for almost two years, and there's very little progress made in the standard community because, you know, I think people who make standard doesn't really have this need because, you know, most, because a lot of people are running web assembly as an embedded runtime. So it's not urgent need to make a web assembly standalone runtime that runs microservices. So things like that has been lagging. And, but for us, you know, that we take a different approach. We implement first. It may be right. It may be wrong. Who knows? But the community is going to tell us, you know, if all the 10 things that we did, nice things may well be wrong, but one thing would be good. You know, we'd be right. And we put that to be a standard. So, you know, that's, that essentially our approach. You know, so I, of course, there's many, many technical details that we are different from wasm time and wasm runtime, but I think those are the biggest high level differences. All right, yeah. Thank you.


proudly we hail New York City where the American stage begins here is another problem of the cast of outstanding players public service time has been made available by this station to bring you this story as proudly we hail the United States Air Force our story is entitled conquered the future proudly we hail the missile men of the United States Air Force the men who have in reality conquered the future our first act curtain will rise in just one moment but first high potential what do those two words mean to you to a young man concerned with his future well they can mean success in his chosen field because the young man with the high potential in today's specialized world is the one with specialized training now you can get that training as an airman in the United States Air Force today Air Force schools all over America are graduating skill specialists in literally hundreds of jobs previously unskilled men are now highly qualified x-ray technicians aircraft repairmen and intelligence specialists and these are only a few of the wonderful assignments open to ambitious young men there's a job to suit every aptitude and interest so if you're of military age well now is the time for you to decide on your future and your Air Force offer some of the finest specialized training to be found anywhere yes the young man with the high potential for success is the one with the good training so start building your future today by becoming an airman in the United States Air Force the friendly people at your local Air Force recruiting station will be only too glad to talk it over with you give you complete information so see them soon and now your Air Force presents the proudly we hail production conquered the future the Matador guided missile has been added to the long line of perfected weapons developed by the US Air Force to assist in the defense of the nation from enemy attack but although no pilot guides this deadly craft to a pinpoint target hundreds of men skilled technicians are needed to get the Matador into the air and then to read the complicated instruments which tell where the missile is going maneuvering the dials with a delicate touch guiding it to its destinations and finally pushing the magic button when the target is reached these men are trained for their jobs at Air Force schools trained in electronics mathematics mechanics and other sciences to do a job in which one mistake could cause death or injury to hundreds or thousands of innocent people the courses are stiff but the results are worthwhile ours is the tactical missile squad and tactical missile squadrons are divided into four sections the assembly and checkout section maintenance launching and guidance one important as the other and indispensable to the squadron operation the missiles are received at the assembly point created and here they are put together and checked out now this may sound like a routine job but it is important to remember the Matador is not a bomb it more nearly resembles a fighter plane and is powered by a turbojet engine it has nearly as many moving parts as any aircraft sometimes more after special recording equipment has been installed for test runs well assembly and checkout is my section we keep a pretty tight schedule even under normal conditions but somehow conditions are never quite normal but let's hear the story of one of my men who as they say fly the Matador I was at my desk one morning assembly Captain Davis yes sir yes yes I do no sir I haven't received that yet I see I see yes I think it can be worked out Colonel yes right the sergeant Stevens in the shop right no don't call him to the phone ask him to come over to the office right away that's right thanks evens arrived at the office a few minutes later he'd only been with us a few months but when my assembly chief left he had recommended him as his replacement I had interviewed Bill Stevens at that time and although he was young and relatively inexperienced he certainly seemed to know what he was doing so I gave him the job it remained to be seen what he would do with the assignment I was about to give him you sent for me sir yes sit down Steven thank you sir I just got a telephone call from Colonel Burns and you're aware of course that we're scheduled to move from our temporary quarters to the new assembly hangar at the end of this month yes sir we have a plan here that was prepared in anticipation of this move I'd like you to go over that with me a little later and see if there are any suggestions you'd care to make all right sir now in addition to this move Colonel Burns has just informed me that these tests which are scheduled for the first part of next month are going to require some brand new telemetering equipment installed in the missile I see sir yes now I haven't received anything official on this as yet Colonel Burns says it's coming through now and he'll send it along but from what he says it's going to require a highly experienced crew and will add considerable time to the normal assembly procedure I see sir now a colonel wanted to know whether we wanted to postpone the move until after the tests and I told him I didn't think so that we could handle both jobs I think we can sir we'll make much better time than you hang your sir floor plan is so much better range we'll have so much more space mm-hmm okay that's what I wanted to know and you report back here this afternoon after Chow and we'll go over those plans and by that time we should have some data on this new equipment as well yes sir oh and by the way Stevens do you have any plans for this evening no sir well you've been working rather hard there's a dance in town at the high school for the airman here at Patrick why don't you uh Doris this is Bill Stevens Bill Doris young how do you do nice to know your bill Doris is just your speed bill brainy yes she's a teacher imagine this cute number of teeth here only for three I'm bigger than they are the bill bill and I was telling you about Doris we'll smart oh now if you too will excuse me I'll go get us all some punch um what do you think about Florida web I like it warm yes yes it's warm it's nice though you like teaching yes yes it's interesting I guess it would be do you like your work oh gee yes it's just fascinating to I mean yes well I'm sorry the trouble is that we don't get a chance to talk shop much oh you have any hobby no not exactly unless you call fishing a hobby of course do you like fishing living here in Florida all my life of course I do of course it's most likely quite different where you come from well I've never done any ocean fishing at all I've been too busy since I've been here and to tell you the truth this is the first time in my life I've ever seen an ocean really imagine that sure like to try some deep sea fishing on my next leave though would you my brother has a boat charter oh gee that's nice oh I could never afford I mean I that is he wouldn't mind if I brought someone along sometime gee well sometime I mean maybe you love to have you come that's great well I'll let you know of course it'll be a little while yet before I can go tell me when you can and I'll call Ralph that's my brother so he won't get another charter and we'll introduce you to fishing as it ought to be morning Captain Davis anything special you want to see sir how those telemetering devices doing giving you a lot of trouble Sergeant Stevens is working on him sir he never seems to stop he's over there and back if you want to talk to him sir oh yes I see him thanks Stevens how are you coming along they tell me you've got everything rolling anyhow just about oh it's you captain some job what did you say sir I said you're doing a fine job thank you sir you think we'll get under the wire yes sir I think so okay stick with it personal example with seven such as I had never seen before of course everyone was anxious to make the move we've been operating for a long time in inadequate space but the extra work involved was tremendous and this in itself often acts as a dampener of enthusiasm however in this case it was the reverse several times the men work 16 hour shifts to complete the operation and only quit when I ordered them off the job but no matter how long the others worked Stevens was always there a little longer I told him what I thought of money said to me come on forget it there's a good movie on at the base theater come on let's go anyone see Bill Stevens over in his bunk asleep and all his racket they came in with the rest of us after work been sleeping ever since Bill Bill hey Bill wake up what's the matter what's the matter with you six o'clock on a Friday night and you're sleeping yeah I just dropped off you're working too hard listen though I got something hot the squadron's been transferred to tack tactical air command yeah hey that's great darn right think of what it means it means that the Matador is out of the experimental phase we're a combat outfit now it's right you think we'll be transferred not right away anyhow we're going to be right here with the missile test center I see and that we will be getting the benefit from the test being conducted here we'll probably hold our launching in conjunction with the tests right oh that's great hey hey fellas you hear that we've been transferred to tack transfer the technical air command was well planned but the squadron holding their launchings from Cape Condeviral result was an economical and efficient operation progressive refinements on squadron techniques were to be merged into a finally integrated weapons system and Matador was on its way as a tactical weapon you're listening to the proudly we hail production conquered the future and we will return to our second act in just one moment are you a service veteran well if you are then listen real carefully because this message is just for you you may be qualified to enlist in the United States Air Force in a grade that will surprise even you if you possess one of the critical skills needed to keep America's air defense strong the Air Force offers you an opportunity to put your skill to work and at a higher grade and higher pay than you may realize the Air Force needs experience and know-how gained in the armed forces and now thanks to the new career incentive act you can put your service gain skills to work to your best advantage by returning to the armed forces as a member of the Air Force team you write or visit your Air Force recruiter for special prior service man's folder it's full of important details you'll see why today and tomorrow you're much better off in the United States Air Force you're listening to proudly we hail and now we return to act to have conquered the future the pressure was really on we all had a job to do and we knew it I was glad though when I heard that Bill was planning to go to another high school dance he needed to relax nice seeing you again nice seeing you again miss young my first name is Doris if you'd like to yes I would Doris mine's Bill I enjoyed talking to you last time I guess I talked too much no no it was very interesting I love fishing it's so unusual for a girl I mean oh would you care for some punch yes it'd be wonderful that was when you should have asked to see your home I never thought of it you didn't think you didn't think some other guy's gonna beat your time if you don't start thinking yeah but we hardly know each other and at this rate you never will you get her out on the terrace real romantic like and what do you do start talking about some old fish that got away he didn't get away that was the point but oh oh I see what you mean hey I did make a date with her a date for what to go fishing fishing but she likes to fish I can get a pass the end of next week I think so we're going out with her brother fishing well it's something no I don't know fishing now Stevens come in I want to talk to you about something yes sir I've been over the week's reports since we've completed the installation of these telemetering devices also understand that today is our first official day in the new shop yeah that's right sir and we've made our deadline and better well everyone seemed to understand how important it was they all sure pitched in well it was a fine job and I want to give you full credit for your partner thank you sir now I have another project for you do you think Finley can take over for you for a few weeks I think so sir good the guidance section is very short-handed for the installation of some new equipment I think it'll be a good opportunity for whoever gets the assignment so I told them I'd send over one of the best technicians I've got yes sir that's you sergeant Stevens me sir well thanks right you got a report to guidance tomorrow morning they'll have some orders for you I hope I'll be able to make good your recommendation now I'm not a bit worried where is the equipment to be installed sir if I may ask Grand Bahama Island that's a short hop from here that's wonderful that is something wrong I sort of thought you'd like it I do sir I've been anxious to see this set up on one of the downrange basis but I just never dreamed I'd be able to go well as you know the launchings will be starting in about 10 days from now you will still be there then so maybe you'll have a chance to get in on the picture from the other end for change see what happens to the missiles we fire that would be terrific you understand the security regulations on this now sir with the firings coming up they tighten up on everything of course and your trip down there can't be divulged to unauthorized personnel of course you have in the family here so you have no problem on that score no no sir well good luck thank you sir dick yeah hey dick come here oh Phil sure I'm glad I ran into you I've got some news and I've got a problem yeah I'm going to Grand Bahama in the morning Grand Bahama what for I'm loaned a guidance temporarily I'm going down to install some new tracking equipment oh how long you've gone I guess about two weeks the captain said I'd be there for the test gee that's great yeah oh what's wrong you got a grand sans seed in the biggest show yeah yeah yeah but this is the weekend that I had that date with Doris to go fishing we'll call her up and tell her you're going away and make it for later in the month that's just it I can't captain says I can't tell any unauthorized person I'm going no kidding it makes it more complicated oh yeah if I just tell her I can't make it she'll probably think I don't want to go she'll get sore yeah yeah I see what you mean but you'll just have to try anyhow oh she's not that kind it'll take it the wrong way oh gee Doris I'm looking all over for you I've got to talk about Bill I don't want to hear I've got to explain it won't take very long all right no matter what you say I'm not going to change my mind well okay but but just just listen he he's got cold feet you see he's in love with you so much in love with me that I haven't seen him in over a week well that's just it yeah yeah he he he wants to marry you and and he's afraid that you don't like him yeah and well he doesn't want to see anymore because it makes him feel so bad that you might not feel the same way he does yeah yeah that's it why on earth doesn't he ask me how I feel oh well he can't he it get well they would make him feel too bad if you turned him down I mean you wouldn't know that is he asked me dick what dick something awful has happened you've got to help me well sure sure what I wrote a letter a letter yes I was so mad when he broke our date well not mad but well I guess I didn't think he could be very interested so so I wrote him and told him I'm glad he couldn't come because I told him I was gonna marry somebody else oh gee what did you do that I don't know but the important thing is he mustn't get that letter gee I don't know how gosh you see each other every day don't you get your mail together well sometimes make it a point to go with him tell him anything just tell him it was a letter I wrote to a girlfriend and I got it in the wrong on below well I don't know you've got to do it it is midnight early morning firings are the preferred one that keep kind of around the weather at the impact site is better as a result work has begun at midnight by the men of the launching and guidance sections and often they work around the clock hey Davis what are you doing up this hour of the night this is sort of out of your line isn't it yeah sort of I'm an observer got some new gimmicks on this series and we had a slight flap getting them installed so I thought I'd come around and take a look it's plenty to look at there is there is there's a central control central control calling Clambake to come in Clambake to Clambake to here how do you read me five by how about you only about three by how's that loud and clear what was the trouble all bad court I'll use another pair right I'm talking to Grand Bahama only I can get through the bill everything I think of gets things more mixed up this one might just be the one to un-mix Captain Davis yes sergeant are you busy sir there's something I'd like to ask you about what is it well sir it's about Sergeant Stevens Bill Stevens now go ahead we've got a few minutes yet he told me the whole story and I promised that I'd think about what I might do and I went back to work again the sergeant had a problem all right but by that time the preparations were in full swing and there was nothing I could do about solving it for the moment through the periscope and the blockhouse the Matadors are visible this time there were three of them noses pointing skyward to where the first rocket thrust would shoot them until they would level off as the turbo jets took hold the Matador is painted a brilliant red for easy visibility it's not for artistic reason as they get their scarlet coats but as they stand silhouetted against the first rosy rays of dawn the brilliant blue sky behind them and the white sand and concrete beneath they make an inspiring and colorful sight the time is x-minus 10 9 8 7 6 5 4 2 the end of the countdown this is it check with a chase plane right away yes sir central control the cross be one central control the cross be one seven come in cross be one come in cross be one cross be one here right sir yes sir I think cross be twos coming in now sir okay yes cross be come in cross be two right there sergeant over Roger a 7 6 5 2 with them off one to go each Matador has a different target each is tracked carefully to it and then finally pointed into the sea and destroyed today the Matador and the men who yes fly it have been placed in the defense service of the nation as an integrated weapons system the future is conquered and will continue to be there was one more piece of business on the morning's agenda at least for sergeant Keating in me sergeant Keating if you're not too busy now will you get me clam baked to on the line yes sir clam baked to come in please sorry to be so long getting to the control room this is Captain Davis sergeant oh yes sir I want you to listen carefully yes sergeant there are times in the man's life when Davis sir the letter it didn't get mailed return no stand just a moment I'll be able to talk to you later never mind Bill thanks I'll see you when you get in here yes right Keating what the devil now she gave it to her little brother and he got so interested in the stamp that he kept it for his collection and dumped the envelope into the mailbox without it what a relief oh sir I I don't know how to thank you anyway that's all right sergeant that's a pretty good man who wants to help a buddy out as much as you didn't you know sergeant I think we might help things along if we had that miss young here the morning he comes in and reports to me but you catch him before and do a little orientation swell he'll be there that'll be easy after what I've been struggling over everything worked out perfectly sir yes it did I mean good we'll go into that in a minute now first I have a little news I recommended you for another stripe and I just got word on it you better get over to a tailor right away and get it sewn on oh yes sir seems to me a technical sergeant or to be able to support a wife and pretty good style him if he had a wife sir well as sergeant Keating tells me if a fellow was to ask the question he could be pretty sure of an affirmative answer that's what he told me too sir that's well if you'd step into the next office I think you might find the girl Doris that's right yes sir let me know how it all comes out yes sir or as peace power and today the United States Air Force is seeking alert and ambitious young men become airmen and help safeguard the peace of our country while serving their country today's airmen are attending the world's finest specialized schools there they're learning such interesting and rewarding skills as photomapping guided missiles aircraft electronics and gee many many others and upon graduation they're highly skilled specialists ready for interesting and good-paying assignments in the United States and in many fascinating countries around the world so if you're a young man of service age well then you owe it to yourself to investigate the amazing career opportunities open to you as an airman and in addition to an outstanding career while you'll enjoy educational and travel benefits that are second to none you'll wear the smartly styled blue Air Force uniform and you'll enjoy the respect and prestige that goes with being a member of the world's finest Air Force visit your local Air Force recruiting station talk it over with the friendly people there they'll tell you how you can qualify as an airman in the United States Air Force this has been another program on proudly we hail presented transcribed in cooperation with this radio station proudly we hail is produced by the Recruiting Publicity Center in New York for the United States Air Force and this is Dick Herbert speaking and inviting you to tune in the same station next week for another interesting story on proudly we hail


The federal government has charged all stakeholders to deliberately initiate measures to increase food production for the population by the year 2024. The Minister of Water, Resources, and Sanitation, Professor Joseph Husev, made us known as the flag of ceremony of the 2023 and 2024 dry season farming, which took place at the Benin-Orwena River Basin Development Authority in Edo State. The Minister stated that President Borla Tinibu has mandated the 12 river basin development authorities in the country to end forced capacity in the country by the year 2024 by taking advantage of the dry season farming and other avenues available to them. We are here to flag up the 2023 dry season farming. We are here at Benin-Orwena River Basin Development Authority to flag up. I want to use this platform to call on all the 12 river basins under my ministry to commence the dry season, the 2023 dry season farming around the country as this will boost food production in line with the President Borla Tinibu Renew Hope Agenda. I also want to appeal to all the communities and state governments to make available land to our river basins. They are the one that has the mandate and the capacity to provide water that is needed for the dry season farming. We are providing the water that is being required for the dry season farming to our farmers and our commercial practitioners that are partnering with us in line with the food security agenda of Mr. President. Earlier in his opening remark, the managing director Benin-Orwena River Basin Authority engineer Salyu Ahmed assured the Minister of their commitment toward achieving the mandate by the President. The river basin development authority is poised to be the reference point for all planners, consultants, researchers, agriculturalists and other stakeholders in the water sector. We are in a position to collaborate efficiently with sister organizations. So today, Honorable Minister, you stand on the stands of history as you formally install or unveil this huge resource of knowledge and data for the benefit of our country, Nigeria and Nigeria.


Hey y'all, I'm Tammy and the Cameraman is Chris, my husband and this is Collard Valley Cooks where we cook like our momma's did. Today I made a special cake just for you. It's a southern praline cake and let me tell you it is going to be amazing. So let's get started where we're going to start with a cup of butter and you're just going to put it in your mixer at room temperature. And you're going to beat it until it's nice and fluffy. You really need to beat it until it turns a light color, almost white looking. And beating it about two minutes is a good time. So we're going to beat this for two minutes on a medium speed. We're going to add two cups of sugar, add one at a time. These need to be room temperature, we're going to use four eggs. We're going to put in two teaspoons of vanilla and then I'm going to put in a teaspoon of butter extract. Instead of sifting my flour and my baking powder and salt together, I'm just going to add the baking powder and the salt to the mixer and then add my flour, okay? Because white lily flour I'm using today is all purpose and it's pre-sifted so there's really no need for me to sift it, all right? Now if you've got a cake flour and you want to sift your flour then go ahead or if it seems lumpy then you should. So I'm going to use three teaspoons of baking powder and a teaspoon of salt. And my butter was salted, okay? So now what we're going to do is mix this up really good. Then we're going to start adding our flour, a cup at a time, there's three cups of flour and then we'll add the cup and a quarter of milk in as well together kind of alternating it. Now once you add the rest of the flour you're going to beat it for two minutes, not over and then we're going to get it in the pan. So I got the idea for this recipe off the Dixie Crystals Sugar Bag. It's on the back, it's called the Southern Praline Cake. However, I did change it up a good bit and so I'm not using the recipe exactly so if you want to make the cake like I did you won't be able to go buy the recipe on the bag or the website. You'll have to use my recipe. And I changed it up because they have soda in it. Normally I don't use baking soda when I bake things unless I'm using buttermilk. This cake did not have buttermilk. I added more baking powder and more sugar, okay? So there was reasons and more salt and there was reasons I did that. So just let you know. It just sounded so good and I wanted to make it. Now you can measure these out so that they're identical thicknesses but I usually just eyeball it. So it's a lot of cake batter which is really good so it's going to make a nice tall cake. Now I'm using 8 inch pans and they're sprayed and they have a piece of parchment in the bottom of them. They tell you to use 9 inch pans but I personally love 8 inch pans because it makes the cake look really tall. So pretty cake batter. It looks a lot like my white cake batter. It's in the bottom when cooked good. Looks delish. Now we're going to slide it into the oven and cook it at 350 degrees. Alright we'll see y'all in a little bit when they come out of the oven and we're going to make a delicious pecan frosting. Alright these are ready and they smell really good. Ooh that one's not. That one's not quite ready. The one on the top is the one that's ready I think. It's ready. Looks good. Bounces back when you touch it. Those are a little thicker so it's going to take them a good 5 more minutes or so and then we'll get them out. Alright these two are ready.  Alright y'all we are going to make a delicious praline type icing and the way I'm going to do that is I'm toasting my pecans and we're going to brown the butter. What gives pralines their delicious flavor is browning the butter. Alright so I'm going to take two sticks of butter and put it in this skillet and let it start melting and we're actually going to cook it until it gets brown and you're not going to want to rush it and burn it or anything. You want it to have just a really brown butter flavor. So you're just going to cook your butter over a medium heat until it begins to brown and I'll show you about how brown you're going to want it before you make your icing. You really need to do this ahead of time so that it can cool down. You don't want to add it to the powdered sugar when it's really hot. Alright it's finally getting a little bit brown but I wanted a nice brown color so I'm going to keep cooking it a little bit longer. See how it's turning? It's going to have a really good flavor and you don't want it to get too brown. Just enough to give it a really good toasty buttery flavor. Almost there y'all. I think that's good. We're going to turn it off and we're going to let it cool and then once it cools down some we're going to make some icing with it. Alright we're going to start making our icing so we're going to take our brown butter and we're going to pour it in the mixer and the mixer will help cool it down some. Our toffee. We're going to start adding icing sugar which is powdered sugar. Now I'll probably use about 5 cups of powdered sugar at least so we're just going to start adding it in here and then if we need to add some extra cream we will of this half in half. Now I'm going to taste it. I think it added dashes. Well the butter was salted. Butter. So good. Oh it is so good. So we wound up adding about a half a cup of cream. You want to just add it until it gets a spreadable consistency because we brown the butter it does make it thicker than if we just used butter and I'm going to tell you it is absolutely delicious. So I am going to take the beaters out of here and we're going to ice our cake. Now I didn't make a ton of icing because we're going to put some caramel on the top and some pecans it's going to be a very, very delicious cake. It tastes just like a praline or toffee. So I am going to go ahead and ice the layers and I'm not going to put a thick, a lot of icing because we're going to put caramel on the top and it's going to be a really sweet cake. I used 8 inch layers. Now you can use 9 and it won't be quite as tall just try to get them as straight up as you can and it don't have to be perfect. Now you're going to want to pretty much put all the rest of it on the top and we're going to put caramel on the top so it don't have to be real thick on the top. Probably even got this a little bit thinner and it worked fine. That fresh layer in the middle is really, won't be getting a little bit of trouble. Now it's going to slide on me. I think this icing is getting a little thicker as it cools down. So I'm going to wet my spatula a little bit just to get it to spread easier. You can always wet your spatula if the icing seems to be a little thick and now I've got to get it around the bottom and the way I'm going to do that is I'm going to grab this and we are going to put pecans around the bottom so it doesn't have to have a lot of icing at the bottom but we need a little cake showed up. That's all right. We're going to cover it up with caramel. Lord, I think I could have used a tiny bit more icing. Yeah, I need it. Oh yeah. Perfect. We got it. Now I'm going to smooth off the sides with my hot water and the top and it doesn't matter that my cake came through because we're going to cover that up with caramel in just a minute and that's all there is to it. Go around it one more time and if you want to use a comb on it, you can see if I've got one. Now make sure you get the edges real smooth so that when you put your caramel on it will flow down the edges good. You don't want to curb on it and if you have a curb and it will stop the caramel from flowing. Now we're going to heat up our caramel but while it's still wet on the bottom, you don't want to wait until it dries up. We're going to put some pecans around it and you can toast your pecans or not. It's totally up to you. There's our beautiful cake. Now we're going to take some caramel and a friend of mine sent me some delicious Sanders Caramel and it says to take it out of the jar, put it in the microwave for about 10 seconds. Now I'm going to make sure it's a good spreadable consistency before I put it on top of the cake and it's delicious. Me and Chris have already tasted it. Now I'm going to put this in the microwave for 10 seconds, 10 seconds. That was 10 seconds and everybody's microwave is a little bit different. No, I think that's good. You don't want to get it so runny that it falls off the cake. All right, here we go. Give me another spatula. I'm going to go around at once first and then I'm going to let it start down the edge a little bit. I'm just going to smooth off the top a little bit. That's going to be good, good, good. All right, we're going to put a few pecans on the top. There you have it. If I spin a little bit, it might run a little bit better. Looks good, don't it? There you have it, my praline cake. Well, that looks good and it smells delicious. Now, y'all, this is going to be absolutely over the top delicious. I promise. It's a southern praline cake. All right, let's cut us a piece, y'all. Now it's fresh. We'll just have to see how it cuts. I warmed up my knife a little bit so that it would go through that caramel pretty easy. See, it's nice and tall and I always put the thickest piece on the bottom because it always seems to get messed up.  Oh, it's so good. I can guarantee you right now this is going to be one of the best cakes I have ever made. It is absolutely divine. Absolutely. All right, let's get it by it, y'all. Make sure you get some caramel. I'm going to grab a pecan. I want everything in one bite because layers are nice and tall. That is absolutely amazing. If y'all make this cake, you'll be making it again. I can guarantee you that it is delicious and make sure that when you brown that butter, you get it nice and brown because that's what makes it taste so good. And the cake is so moist and it's just delicious. Now that's a winner. Y'all have fun icing it up and putting the caramel on it. Everybody's going to love it. We appreciate you watching Colored Valley Cooks where we cook homemade old-fashioned food just like Mama did. Bye, y'all. Love you.


Hey, what's up everybody? Welcome to tomorrow. Last week I talked about Virgin Galactic and the results from the crash investigation that the National Transportation Safety Board was doing, and this week I want to talk a little bit more about their competitors, specifically X-Core Aerospace, who has released some new information about their science payloads, as well as a really interesting suborbital space plane project from DARPA, and that's what we're going to be talking about for this, your space pod for August 11th, 2015. So first off, X-Core Aerospace has released a lot of information about the science payloads that could be brought along with their links space plane. Specifically, this would be for the links Mark II, because the links Mark I is just going to be the prototype to make sure that, you know, all their systems actually work for flight. Before the links Mark II, some of the payloads are going to be internal and external. For the internal payloads, a lot of this has already been publicly available for a while, but for the alpha payloads, it would be an experiment rack that would fit behind the pilot's seat, and then for their beta experiment, they would either have a mission specialist or a passenger who would operate those experiments and perform other tasks, or replace the passenger seat with another larger payload rack for experiments. The prices for the alpha experiment have tentatively been set at $50,000, and then for the beta experiment, depending on if you have a passenger or a payload rack, the prices vary between $95,000 to $150,000. Now, their external experiments is where we're getting some new information. First off, their Charlie experiments are going to be two aft cowling ports that would be able to fit up to a two-unit cube set in size, and also about two kilograms of weight. For these aft cowling ports, they would not deploy any cube sets or whatever payload is inside of them, but the payload can get access to power from the link space plane and also have access to the external environment via port hatch. The prices for these aft cowling port experiments are about $20,000, so that's the cheapest of them so far. And finally, the Delta experiment, and this is the one that I've been excited about for quite a while and am very happy to finally get some more information about it. For the Delta experiment, it's only going to be on the links Mark III, and unfortunately, only in the United States. Anyway, an external dorsal mounted pod could deliver a space telescope, returnable payloads, kind of like the Charlie experiments, or have a two-stage booster capable of delivering nano-sats into low earth orbit. The prices for this is ranging between $250,000 to $500,000. The other space plane I wanted to talk about today is actually being worked on, or at least funded, by DARPA. And what they've done is they've funded three companies, Boeing, Northrop Grumman, and Mastin Space Systems, to develop a reusable unmanned space plane that would be able to travel into suborbital heights and then release an upper stage that would also be able to deliver nano-sats and small satellites into orbit. DARPA has initiated the second phase of this program, or phase 1B, of what they're calling the XS-1, with the purpose of identifying core technology, mitigating risk, and developing a technology maturation plan and performing some demonstration tasks to eventually fabricate and fly an unmanned suborbital space plane that would release an upper stage capable of delivering a 3,000-pound spacecraft to orbit, for a cost of no more than $5 million per launch. For this round, DARPA has funded $20 million in all, and it's been split between Boeing, Northrop Grumman, and Mastin Space Systems. Also for some other quick but really awesome news, Russia has formally committed to international space station operations through to 2024, which is awesome because Congress is pretty much allowing NASA to go through 2024, and with Russia support then that pretty much means that the space station will be able to continue operations through 2024. We're still waiting on some sort of decision about the 2024 date from the European Space Agency as well as JAXA, the Japanese Space Agency. But with the two big partners, the United States and Russia formally agreeing and committing to the 2024 date, I have a pretty good feeling that the European Space Agency and JAXA will be not far behind in committing to 2024, so the longer that we can use the international space station the better. Anyway, leave me a comment about what you think about these different space plane ideas and this international space station news. I'm really excited about all of this for sure. Also, if you are willing and able, then please donate to our Patreon campaign at patreon.com slash spacepod so that we can continue to keep making space news videos like this. Thank you so much to everyone who's donated already and it really does make a huge difference. Anyway, thank you very much for watching this video. My name is Michael Clark and hopefully you know a little bit more today than you did yesterday, thanks to tomorrow. Keep moving onwards and upwards everybody and I will see you in the future.