 As you can see, it's basically winter here. So I'm going to make this quick. It's cold. A little drained right now. So this might not be one of the most energetic videos. You know, cranked out a good number of videos recently on C sharp stuff, F sharp stuff, and I had a stuff. And the recent thing I've been doing that I really didn't expect to be as big as it's starting to turn into was covering some reliability problems that I was aware of with Ada. And there are some community members that have been pitching into that. Some of these, well, I'm going with my usual thing of if he had direct messaged me, I'm keeping your name private. If it was like a YouTube comment or whatever, then it's public. Some of these, like the last one I did, I'm not naming who that is, you can probably figure it out, but I'm still not going to directly name who that is. But Adam Ward has been playing around with some things. And I've got a few things. Some I'm looking into some I have confirmed, but there are some specifics. For example, as it turns out, you can modify constant values, which is a huge problem. And is something that actually can't be done in certain other well engineered languages, like C sharp, even with reflection, you cannot change constant values, but you can without it. And only on certain architectures, you have to be on a von Neumann architecture that does not have an an expert or something like that. Hey, go back inside. So pretty limited in the machines that that can execute on, but it's still my point there is to demonstrate a flaw in how constants were designed. That is ideally something that you never want to be an issue at all. Not something you want the CPU itself to protect against and throw an exception. It should never ever happen. But it can because of Addis design. The other thing, though, I have a video it's long, I'm working on it, it's just editing here and there. But it's long on reviewing it, of course, extension for VS code. And it's a mess. It's not good for many reasons. I was originally saying that the LSP seemed quite good. And that was something I was considering. Considering I'm apparently working on the VS code extension, I did again, was integrating their LSP into mine, even if it meant relicensing. Because at the time, it seemed quite good from some initial testing me and another person did. It seemed quite good. Oh, boy, I saw things that are not okay. It's mad. But that warrants a detailed video that covers it. And another thing I wanted to cover is another one in the series for the My Issues with AidaCore. And this one has to do with their treatment of community members. And specifically, I want to cover the case of David Tamar, who is an individual that seemed to have a lot of promise and just became totally disparaged with the quality a lot of things and how AidaCore approached him pointing out bugs. It's absolutely disgusting. And I want to bring attention to it. That, unfortunately, is a bit of a rabbit hole. See, in order to cover the case of David Tamar, hopefully I'm saying that right. I'm really not familiar with Israeli conventions for names. I'm kind of basing that off of like, it's an English name. I apologize if that's way off. In order to cover his case well, we have to, because there's some intermixing because of some interactions between me and him. We have to cover my case with AidaCore as well. It's going to be a bit for that because there's even more of a rabbit hole that I did not expect. And I got to delve into some community lies and other things. And oh, that's fun. We can cover some of my stuff right now, because I just want to get some points out there right now. I'd said during my the video that my experience as an Aida developer of 14 years, I'd said that I used to be a commercial, I was paying for their commercial support. And I was for several years. Not my first few years as a developer, but for about four or five years. I'm not sure specifically. I'm more familiar of when it ended, but not exactly when I when I first started paying. But as part of that, you get access to the NAT tracker, which is their special bug submission system. Um, understandably, since you are a paying customer, you get priority support. And that's reasonable. I really have no problem with that. But what I do have a problem with is when a community member, even if they are not paying reports a bug in the software that is affecting all of us. And why are you not taking that seriously? Why this gets into a rabbit hole is 10 years ago and I'll pull up my NAT tracker ticket for this. I'm going to hide the other ones and hide the name that I'm registered on there for. I got reasons for that. I'll deal with that in a future video. But I got my NAT tracker ticket up there. I reported the issue with tabs 10 years ago. I believe it was October 11th, if I'm remembering that correctly, but it was October of 2009 10 years ago. When I got fixed for me real quick, five years ago, I find out that the community release of it, it's still broken. Now, why did you fix something only for me and not for everybody else? And so for five years, I've been occasionally bringing that up, reporting that to the community members, but only as a community, the Atacor employees, but only as a community member, not bringing up the fact that I used to be a commercial supporter. No progress for five years. David Tamar goes and reports it as well. And the same thing. So we're going to have some interesting stories coming up.