 Well, that was a tool chain from last week. This week is different. JavaScript. Let me just put this. I have three production audits just named after me. Four. My job is to keep our code running while other packages are changing theirs. Should you learn JavaScript? Nope. Is there any other option? Nope. Oh, look. Another library was added today to patch the problems of the other 150 that were also released. Did you know JavaScript was actually written in seven days? Such a messy language. I love it. Did you know JavaScript was actually not written in seven days? No one ever knows what value variable is or what its type is. Now, we use TypeScript. We still don't know. I'd rather use Rust or WebAssembly. They say adoption is coming. They said that 10 years ago. They say that every year, but this year is different. Is it scalable? No. Is it maintainable? No. Is it portable? Not really. Yeah, we use React. We actually use Preact. We actually use Svelte. We actually went back to vanilla JavaScript. Yeah, we're using a library for this. Well, that we rewrote to vanilla JavaScript because it wasn't efficient. We're stuck with this messy language now. I love it. JavaScript. Yeah, it's the defect of standards. Do you know there's a library for that? I wouldn't trust the, let's say, finance application with JavaScript. What our finance application does is, yeah, it's only fine to use JavaScript, but I recommend using TypeScript. Not that we do. We had callback hell. And then we went to promises. A wait came out. We went back to promises. Now we rewrote everything back to callbacks because it's just more comfortable. At least you know it's bad. Oh, it's probably just a quick fix. It will take me three to five days to find it. We tried CoffeeScript. We wrote our code base. We tried TypeScript. We wrote our code base. And then we went back to vanilla JavaScript because it's just more comfortable. So we rewrote our code base again. Yeah, we use React. And then React 16.8 came out and we had to rewrite everything to hooks. React 17 came out. We had to rewrite everything again. And then React Scripts was updated to version 0.4 and we had to fix everything to work with local images. And now React version 18 is coming out. We'll rewrite everything again. We rewrote our code base around nine times this month. Yeah, you can use Redux. It's only fine. But if you're on it, I'd recommend you use Redux Toolkit. But actually, it's better to use Flux or Flomux or Fluxable. Actually, better to use Recall. Not that we do. But now React came out with the hooks and contacts API which apparently is better than Redux. Apparently. We'll rewrite everything again. Sometimes it just doesn't transpire. We usually rewrite our code base then. We actually wrote a custom transpider to transpile transpider. It's such a messy language. We use it for our website, desktop app, mobile app, for the fridge, the Tesla. It's not actually native. I mean, it is actually native but it's sort of not really native. It's sort of hybrid native. But some of it is native. I mean, some people use it in a native way but we don't really use it in a native way technically. A lot of people are switching back to native. No one has switched yet. Angular? Talk to me when you use Angular 2 or React. NPM is such a bad package manager. No one uses that anymore. NPM is such a good package manager. How many languages have one? So that major version breaks our code but our code breaks the minor version. I still don't know how to fix pure dependencies until this day. Yarn, bit, PNPM, Torbo would make sense, right? JavaScript doesn't think so. jQuery? What are you, five? We use JJQuery. Global variables? No one uses them. It must be somewhere in the window. How do you debug node apps? You don't. You just write good code but not in JavaScript. No one ever master JavaScript. I get 100,000 points in Stack Overflow. I'm still a noob. Node is technically multi-threaded. JavaScript is technically performant. Our code is never safe. When they'll blow up, probably won't work here anymore. Probably will be using Rust or WebAssembly or whatever. JS. An array is technically just an object. Objects are objects. Null is technically not an object but objects can be null so they technically can be non-objects unless they're an object, right? So technically null is an object. Yes. It's a bit hacky, I admit, but JavaScript is by design. Is it easy to learn? Have you tried JavaScript? Probably will be a bit hacky. Have you used JavaScript before? I don't recommend. I don't like our tool chain. Documentation? And another advantage is that it's free. So was Java before it was bought by Oracle. So we prepare ourselves by installing modules from NPM. Then we compile it to TypeScript. Then we use a term, Spiler, called Bubble, to turn Spiler to ES5, load it with System.js, file for bankruptcy, bundle it all up with Webpack, use it in a framework like React and let the state be managed by Redux or Flux, Flummox, or Fluxable. Or Recoil. Or whatever. JS. And voila. All of this just to avoid using jQuery, or in our case, JJQuery. But that'll be probably less performant as most of the things. This isn't our production code. It will be tomorrow, though. Probably gonna get fired again. I mean, there is really no alternative to JavaScript right now. Defecto. No one really knows what the value is until we get an error. I love it. Well, try writing anything without JavaScript nowadays. JavaScript. I love it. No, I don't recommend it.