 So I'll have to add to those updates already I'll get this out of the way first the QBA ILA 20 I made a mistake should have fully read the documentation for the device As it turns out you can only override the boot process using a micro SD card so Micro SD card versus M-SATA Obviously the M-SATA is better for storage. So that's something I still would have bought in anyways But I have to pick up a micro SD card to actually do the boot I mean I could play around with getting Android to work as a test bed, but I getting the That that platform so closed off it's hard to get the compiler loaded onto it and everything And I mean it's really hard to build the compiler in the first place. I'd just rather not mess with that I'd rather get like a Linux or free VSD just something on to that and use that as the test bed because What I'm really interested in testing is not the platform, but the processor architecture That being said Would still be a good idea to have some kind of Android device to test on but I'm I bought this device as Intending to use it as just arm test bed not specifically an Android one Could always buy a second for that but really good value on the thing anyways Some of you probably would have seen it Those of you who follow me on github, I believe I mentioned it on Twitter, but I don't I don't know I Think I did anyways the VS code extension that I developed the the Ida one not the spit one I Wound up learning some really useful things when it comes to writing those kinds of extensions Specifically How capture groups work so that you can capture something in the begin but then also reference that in the end that's actually really important and Just some other sophisticated trickery like some of the specifics behind how the look ahead and look behinds work because I was kind of under the impression that you wouldn't be able to use a positive look ahead to Constantly reference the semicolon in a more and more and more narrow scope like if the if the So you have a type definition Obviously the type definition begins with the type keyword and ends with the semicolon If you have something like an aspect clause within that as well That also ends at the semicolon. So I was under the impression that you wouldn't be able to reference that semicolon But as it turns out The positive look ahead Still finds it. So that's good So that it is enabled considerably more sophisticated matching And as fit and enabled fixing quite a few problems like how Line breaks inside a lot of these statements would completely break the syntax highlighter. That doesn't happen anymore. So that's good. Well That doesn't happen in a majority of cases. There are a few instances where Begin and end are too hard to define An example of that would be like the range section within a type definition It's not happy if you put a line break between the range keyword and the range itself It doesn't like that But you can put the new line Before the range clause and after the range clause just not in between the keyword and the definition So I've been working quite a bit on that because I'd like to get that up to feature parity and pushed to the VS code Marketplace as quickly as possible I Don't have too much farther to go on that one. I've already got the Specifications working almost flawlessly The stuff for the bodies would not be that hard to to add on to And then I would just be adding features that I couldn't add before but I can do those after it's already been published to the marketplace so that'll be a bump in major version number because it's an entirely different approach but I'm excited about that because that will help out the highlighting for my own code and you know, I do use my own products That's kind of how I find most of the problems people contribute some bug reports, but Overwhelmingly I have to find the problems myself. It's the best way to do that is to actually use your product Kind of like the best way to make sure your product works. Well is to actually use your product So Yep, that's what I'm working on right now I don't know what I'll seriously say Have a good one