 Хлори, ми з Валерій. Я софтер-інженер у Red Hat. Я працюю на еклипсія проєктів. Також, як говорити про еклипсія, еклипсія є директора і клауда ID. Це додає для спеціальностей, які вважають рантейнів і ID. Є браузерська ID, плагинів для лангвіжів, фреймворків, тулз, і СДК для створення плагинів і ассамблістів. Є ідея на еклипсія, який вважає в тайп-скріпт, і, звісно, вимагає вирішення UI і UI-фронтів. Тея додає для спеціальностей, і додає для лангвіжів, бо п FSM uniform of the �ер-карміimoバイтецю вважає вирішення ID. І Cord uncles of this απ'ятке understand of several att juvenilles API is very close to VSCode API and we can run VSCode extensions as a terabacant plugin. So I have a short demo to demonstrate how to deploy SonarLint VSCode extension into Chia as a plugin. SonarLint is an IDE extension that helps you to detect and fix quality issues. So I prepared a quick video. So here is Eclipse here. It is dashboard when we can create the workspace by choosing custom stack. I'll choose Chia 7 stack with Eclipse layer and I also wanted to change configuration of this workspace to add one more plugin. SonarLint, it should be added into a plugin as a plugin attribute. It should be the URI to metayaml file which is described the plugin. The main block here is extension where we should put ID of VSCode extension that we can take from the VSCode marketplace and what we need to do is just put the URI which can be to the GitHub and add it into the plugins. And let's start this workspace. Actually, it can take about one minute because we need to pull all images and also we need to pull the image for this plugin which will be run in a separate container. So I'll scroll a bit. Here we have the IDE and we can check that our plugin is here by opening the plugin view and we can see that SonarLint plugin is here. Also we can check how it works by adding a simple JS file at some world and we can see that we have some warning message from SonarLint here. That's basically it. Yes? Thank you. All right, so I found this slide from 2011. I was trying to find... I have a version of this presentation with nice... No, no, no, no. I have a version of this version with beautiful artwork so you're going to have to survive with the bad artwork. I'm sorry about that. But one of the things that we've been doing in the last couple of years is a thing called the Embeddingator 4000. Now, the Embeddingator 4000 is, in my opinion, a beautiful piece of technology. What it does, Embeddingator 4000 takes a .NET library. Let's say that you build yourself a .NET application or a library, a .NET standard. It doesn't matter. You have your beautiful piece of code. But your boss is super hipster. He's building some go code or maybe he's building some Swift code or he's building some PHP stuff or he has to do in real life with another platform. So what we did with the Embeddingator is that we take your assemblies. We compile them. There's a couple of options that you can use. We put the model runtime in front of it. And we try it to a .NET library that you can consume as if it was a .NET library. So I just did this on the spot. So I don't have any demo prepared. I just did this on the spot. I figure it would be fun to try out. But essentially, you take your code, you fit it to the Embeddingator 4000 and I'm hijacking this logo. And it can generate a number of different APIs. This is an alt slide. That's why I can't find the current one. And for IDOS, we generate beautiful Objective-C API. So we tried to follow all the conventions of Objective-C, the way the class are declared, the initializers, all the changes. We can now do that as well for Swift. This slide predates Swift when I did it. We can generate dynamic frameworks. We can generate static frameworks. We can generate Java packages, both for desktop and for Android. And we can also generate C libraries that can be consumed as is on Linux or can be consumed as is on Windows. So, you know, just another thing, another way of spreading the law that we have for .NET. If you have to use it somewhere else, you can use it there. Now, additionally, and we did a super awesome demo where we embedded some .NET code inside a Kickstarter app, which is written in Swift. So it's just an example. We have all these business lodging in .NET. Boom, you deploy it as a framework. Just you drag it into your Swift project. You drop it and it's part of the project. You get all the type definitions, strongly typed, and you can use it. It's an open source effort, so you can actually go to... Oh, okay, this is going to be interesting. You never know what is in that window. I don't know if I want to risk it. Open new window. Oh, I risked it. Okay. You know what? Okay. If you Google Embeddingator 4000 with four zeros, do not click on the one with three. Do not click on that. It is not safe for work. If you click on the one Embeddingator 4000, you will get to the right project. I can send you the slides, but you'll be able to start embeddingating. It has a pluggable architecture, so if we don't support your language, there's a couple of French languages nobody uses like Perl and Python and PHP and Java and Ruby. You know, none of that's... No, I'm kidding. If you have a French language, you can always add a back into this system and you can bring dots then into your system. As long as you can call into a C library, we're able to provide bindings for you. That is my lightning talk. Thank you so much. And I forgot we're having, just like MayChin's theme is having, we're also having. Okay, well, I guess we're done today.