This is Dave Gary During his 15 years as an underground coal miner Dave has experienced his share of non-routine events But one Event that he was involved in is something that seems to be happening far too often the past few years Dave I'd like you to take us to the day in question and Tell us in your own words what happened and how you felt Well on that day I was a minor helper And his midnight shift When we arrived in a section on a portal bus we went to the dinner hole like usual and the boss came in to Tell us what the conditions we had for the day brought the 4 to 12 bosses report and He told us that we had a It was a retreat section. He told us that we had a push-out stump and then we had to move across the section So after we left the dinner hole, I will know it was a power center to walk the miner cable like I always did I walked up to to the miner and 4 to 12 shift had left a push-out stump set up for us to go in Boss had already run the face The operator of my body He took his gas check. I Watched the cables. He pulled up into the cut through the cable out of the way and then my buddy started to mine her up and I flagged for the first buggy to come in. He just started turning ahead and something and I positioned myself in the back of the miner to the right To watch the front part of the cut and the formula run around to the back side to watch the watch a roof from the backside It was all like I said, it was in a push-out stump. So it was already The cold was already loose and the roof was a little drippy But he loaded the first buggy Send him out on that signal for the second buggy to come in Second buggy just got underneath the boom and he started to run the conveyor load him up And I noticed a crossover top of the miner on the other side. I could see the foreman Flagging me out But when it when I it was a dual thing whenever I saw him flagging us to pull out I Could notice the post up along my right-hand side starting to bend so I ran up to the Operator the kitchen and tapped him my torting. It's pulled out of there So I grabbed the cable We started backing the miner out and it's you know after you've done it for a while You hear noises that maybe other people wouldn't hear and I could hear the timber snapping So that told me it was time for me to get out So I dropped the cable And I started running out, but I'd yell for my buddy to We better get out there now I Never I Never looked back I Was off and running and I ran into the boss as he was coming across from the backside and But the time I ran into him we heard it come in now when it came in and it Rolled way back it came back past through the intersection and And the dust was just so thick you couldn't see anything so Foreman asked he said you know is everybody out and We counted heads real quick and we were missing one And we pretty much figured it had to be the operator At that point in time. I hoped that he'd stayed in a cab You know and didn't get out and try to run it Foreman sent one of the buggy operators up to phone to call dispatcher and let him know that we'd had a fall on a minor and As the smoke was clearing the former myself we went we started walking up in towards the cut to see what we could see how bad the how bad the conditions were and As the smoke as the dust cleared You could see the boom and then you could see I Could see a big piece of slate that it fell back across the back of the canopy But that was it. I mean the rest of it was totally covered. I couldn't see anything so Which as we were walking up towards the minor You could see that the minor has was back the boom had cleared where the roof had fallen and And It looked like the most of the the slate that fell Had hit on top of the minor and slid down And covered the minor that way so we walked up to the lip where the and gave it a quick look to look for real ugly pieces drips or whatever and We thought it was okay, you know safe enough to stand there And we started calling for the operator calling his name And we called several times Before he answered and he answered it sound like he was far away His voice was real real small We decided, you know, rather than have him wait, we'd get him out as quickly as we could and Sort of through caution to the wind and you know, it wasn't the best thing to do to go underneath the unstable roof Like epic which I'll be better to get him out So the form and I both called down underneath the boom and underneath that big piece of slate and got to him and We explained to the operator what we were going to do how we were going to try to extract him and The only way we could see that we could get to him was taking him out through the back panel in the canopy So I reached through the the canopy and grabbed him underneath his armpits and I told him that you know I was going to try to pick him up a little and If you feel anything, you know, let me know and we'd have to try something else And I said, you know, if everything's okay, I'll grab you pull you up out You help me a little bit to get him out so we gave it a try and we pulled him up and out and We'd be drug him out from underneath the boom of the minor and took him out to the last open cross gun And he was you know visibly shaken But no it didn't show sign of injury About that time help started arriving from The shift boss came and he brought several his general people with him To look the situation over and the mistake that we made then was that we sort of forgot Charlie, you know, he he was still pretty shook up and We just left him sitting for a while and went back up and started looking at the minor to see what you know what we could do it to straighten it out and at By that time we we walked up to the minor when we're looking around and looking around and Forming one desk the shift boss one dashing the operator some questions about what occurred, you know, because we really didn't have the answers So that's when he came back into mind. We had we'd left him so we went out and back up to where we left him in a breakthrough and He was visibly sick now. I mean he was the reality had set in and he just came close to getting it and The shift boss asked me if I'd take him out in his Jeep and take him outside You know, they asked him if he wanted to go to the hospital or anything and he didn't want to so on the ride out I Asked him. I said jazz. I said, but didn't you you know, what what took you so long didn't you you know see anything happening, you know and he said that he was so intent on Doing the job that he was doing that he really wasn't paying attention to the post situation and the roof and I tried to explain to him that you know, I Had to get out of there.  It was just He said and you know the noise of the roof breaking up was really loud And he never heard it. I mean he he said he just All of a sudden he was in a dust filled situation and in a dark And he said that was good And it happened that way because if he were to realize what was happening He would have tried to get out and around and then he definitely would have made it The bad thing was That as later on after I Got him outside The roof came in three more times As they were trying to pull the miner out. It kept it kept coming in and You'd ever realize how you put yourself in jeopardy when you Because you know the mind it kept coming in back further out in the intersection and we'd all been standing there just moments before minutes before or whatever and It just was totally unstable and you really couldn't tell I mean it Like I said it came in I think three other times Before they got to the miner back and cleared how much Supporting did you and the face boss? Do it at the time you were trying to dig the miner operator out none We thought And and I don't actually Really believe that we even gave it much thought to post around the lip Our primary thought was to get in and get him out, you know, see what kind of shape he was in if we could help him In an emergency situation like that, I don't know if you always think a lot of times you just do and I'd I Can't say that we ever gave it a thought to post that up Maybe if we'd been you know instructor that would have been drilled into us That you know you never Go under an unsupported roof even in a situation like that. Perhaps we might have Gave it thought But to me it just seemed like it was a natural reaction just to go and try to save your buddy If you had thought to do that Where were the posts? How much time would it have taken to support? That lip to do what you could do to make the place safer before you crawled in well We unloaded our the way we used to do it in retreat sections was that we always had posts unloaded in Basically every entry with stacking along the ribs So they were always nearby 100 feet or no more than that Then perhaps to set three or four posts Or to get three or four jacks and put up along that lip that might have been you know Maybe it wouldn't have taken that long. Maybe we'd only taken a couple minutes And as it turned out we had more than you know a couple minutes with plenty of time we could have done it but We didn't give that a thought. I don't think I'm thinking Just reacting


One of the one of the people behind the scenes that's critical to your care is the pathologist Oftentimes the pathologist is often a different part of the hospital evaluating tissue and and helping the clinician figure out exactly what The path out what the tissue looks like It's become as as young mentioned as we start to think about personalized approaches to kidney cancer The relationship between the pathologist the surgeon and the clinician has become ever more important So Dan Luthringer is the head of our gender urinary pathology Section here at Cedars-Sinai Medical Center and a professor and he'll talk to us about How the pathology report and how what he does is important to how we then decide how to approach treatment Dan Thanks, thanks Bob and thanks for the invitation to come and participate in this conference today Again, I'm the guy behind the scenes who really is responsible at least at this institution for of doing most of the histologic microscopic analysis of the genitourinary malignancies specifically the renal cell primarily the renal cell carcinomas All right, there's really two main categories of specimens that we receive one is as our Samples from the renal tumor itself. These can either be biopsies or resections as dr. Kim alluded to and Or samples from a metastatic site or recurrence or a metastatic site the most common specimens that we see are Nefrectomy's resections of the tumors and they're either the partial nefrectomies or a complete nefrectomy and these are Examples of some of these a partial nefrectomy is as dr. Kim suggested our Smaller sections partial resection of the entire tumor which include a little bit of the nephric fat And a little bit of the perinephric tissue as well The goal is to try to get the entire tumor out with a negative margin of resection when the tumors are bigger Generally or infiltrative we tend to get the entire kidney and this is an example of an nefrectomy with perinephric fat the Sinus fat drainage area down in here Maybe an adrenal gland up top and this would be an example of a tumor that's been completely resected occasionally we will we will get biopsies from metastatic sites or Unusually from the primary renal tumor will get a core biopsy usually which is really a much smaller sample of the the tumor mass Usually, it's about a millimeter or two in diameter. It's a core Maybe up to several millimeters or a centimeter in length, but generally it's just a small sample of a much larger tumor A little bit about the specimen handling generally within a few minutes of having the tissue removed It comes up to the pathology laboratory and we're able to do some initial assessment on it We have workstations Where they will come and a pathology team will assess let's assume it's an nephrectomy specimen We'll look at it measure it cut it open We'll procure some of the tissue if there's some tissue that needs to be taken Fresh for potentially for a biobank to be stored away or maybe some tissue needs to be taken for immediate Diagnosis or a margin or something like that will do that or if there's a the if the if you're enrolled in a study Where some fresh tissue needs to be taken and sent off to a particular institution or reference laboratory for analysis We'll procure that as well and make arrangements to send that off on an immediate basis and then at that point We will do photography tissue fixation and over the next few hours. We will dissect the specimen Analyze it do a lot of important Evaluation with our eyes and ears and whatever it takes and then we will take what are called representative sections of that tumor or the Specimen put them into these little take sections of the tissue Put them into these little capsules called cassettes and then we process them overnight in these tissue processors These are pretty standard from institution to institution The next morning the tissue is taken out of the processors and it's manually placed into these other sort of Tissue cassettes which are filled with paraffin wax essentially and they're embedded in Into these wax molds and then the blocks and then very thin sections fortified microns are cut with these special Microtomes they're picked up on glass slides. They're again processed stained cover slip and then ultimately we get as a Sample of glass slides from that tumor that's been removed on an average partial or complete nephrectomy We'll do anywhere from five to ten paraffin blocks Therefore equating to five to ten glass slides This takes about a day or two to complete this and then the initial report and the slides are delivered to the pathologist Who will begin the process of doing the microscopic analysis using obviously as microscope and whatever other tools he needs Looking at that set of slides and it usually will be the sections from the kidney Maybe some lymph nodes margins adrenal gland things like that that were provided by the surgical resection The whole process usually takes about two to three days to complete. So there is a bit of a time lag Because of mostly the technical processing that's involved The elements of the report once we generate the report and becomes available. There really are sort of three Categories of information which are really relevant to to the to the Not just the diagnosis, but the future care of the patient The first thing really is is the diagnosis. What is the diagnosis? Is it renal cell carcinoma or some other unusual type of renal cancer and I'll talk more about that and then Aspects related to cancer stage the tumor size local infiltration has a metastasizer spread and then other features that dr. Kim sort of alluded to resection margins grade vascular invasions We'll talk about each of these just briefly The first aspect is diagnosis the important thing is to remember and again I think everyone in this room is a little bit beyond this, but just remember that at the initial phase tumors are resected and it's oftentimes it's not known whether it's a renal cell carcinoma often times It's not even known if it's even a neoplasma at all not all oops Not all tumor masses are neoplastic or even malignant. I'm sorry. That's fine and so Examples of non-tumorous masses would be things like cysts a lot of renal cysts like this or areas where the Collecting system is dilated called hydronephrosis or multiple cysts can present and look just like a renal cell carcinoma And they're resected as if they're renal cell carcinomas, but in fact, they're not they're benign There are other types of tumors besides renal cell carcinomas Angiomyelopomas are very common tumors. They could be big big like this one. Here's a kidney Here's a big one. They could be multiple here's two They can be small one or two centimeters like this, but they all look like fatty tumor They're not renal cell carcinomas different types of tumors like fibromas Acocytomas can be very big and aggressive looking, but in fact, they're not they're not malignant at all there are other types of Malignancies true malignancies of the kidney which are not renal cell carcinomas Eurythiolial cancers those tumors that are derived at the lining of the kidney That it can extend into the kidney and be derived to the kidney These are examples of some of these here and they these were resected thinking that these are probably renal cell carcinomas but in fact they proved to be Eurythiol not renal cell carcinomas different types of Tumors like sarcomas can to be derived to the kidney or around the kidney other types of tumors can metastasize To the kidney or near the kidney adrenal tumors lymphomas There's a whole host of malignancies that can mimic renal cell carcinomas But what we're really talking about today here obviously is renal cell carcinomas which represent probably 90% or more of all true malignancies of The kidney and these are the tumors that are derived at the renal tubular epithelial cells those little ducks that that are Line the the epithelium of the kidney the diagnosis of renal cell carcinoma Really depends it's it's contingent on microscopic analysis You can't make the diagnosis any other way the pathologist needs to look at the growth take his sections look at the microscopic And then there are a spectrum a range of features that that will ensure the diagnosis or put it into a diagnostic Category of renal cell carcinoma Sometimes it's not so simple sometimes we need to employ special testing through the use of antibody Immune histochemical studies or even as dr. Young Kim alluded to sometimes we need to refer to some molecular Analysis to put it into a diagnostic category of renal cell carcinoma Once we've done that the next phase is to determine the subtype There are different many different sub types of renal cell carcinomas Really based primarily on the appearance of the tumor cells and their architectural growth patterns and that sometimes we need to again Rely on immune histochemical some of the molecular properties or the genetic profiles that To put us in the proper subtype category now the sub classification of renal cell carcinomas You probably all know this because you're all familiar with renal cell carcinomas. It's not so simple It's an evolving sort of complex and and ever-changing Categorization in fact the overall category categorization of subtypes just changed just a few months ago We like to think about renal cell carcinoma subtypes really in sort of developmental Pathways there's a sporadic type those that just happen to occur Just because they just happen to occur which is probably the type of cancers that most people in this room have and those are our typical Typical clear cell Chromophobe papillary renal cell carcinomas and maybe a few of the other rare variants There are those which tend to be familiar and these represent probably 90 plus percent of all of all renal cell carcinomas The familial patterns which again are associated. They're pretty rare. They're associated with In families multiple tumors Different family members can have these and we'll talk a little bit more about these and then there's actually going to be a talk a little bit later In the afternoon or in the morning about genetic based or familial based renal cell carcinomas there are those rare really associated with treatment of other types of cancers and then there's an unusual Category when you have scarred or damaged kidneys those kidneys are at risk for developing renal cell carcinomas So let's move through this a little bit once we've made the the the diagnosis of renal cell carcinoma. We've subcategorized it I know it seems complex, but there really are only three or four main Subtypes that we really need to talk about especially in the context of a setting like this the most common subtype is The clear cell type this represents about the vast majority of all sporadic type renal cell carcinomas Then there are the papillary and chromophobe renal cell carcinomas. These are really the usual types The the much less common type is collecting type collecting duck carcinoma, which is more like a urethanil cancer It behaves more like like that. It's a little bit more of an aggressive type of renal cell carcinoma These are really the main four that we need to be concerned about They're each unique based on their gross appearance and these are all partial nephrectomies This is a complete nephrectomy down here But partial nephrectomies and look at the gross appearance. They're very unique Look at their microscopic appearance the clear cells of the clear cell the papillary architectural growth pattern of a papillary tumor These chromophobe this unusual eosinophilic cytoplasm of the tumor cells probably doesn't mean much to you But it means a lot to us and also some of the clinicians So they have very characteristic gross Microscopic and also they're very unique biochemical and as dr. Kim alluded to very specific Molecular and genetic profiles as well. This is all really evolving as we speak They also And this is a small graph, but we all know that that the different subtypes behave differently some behave better than others So it's really important that we subclassify these renal cell carcinomas Based on there on the appearance all the appearances that we talked about And the other thing that dr. Kim alluded to and I think we're going to talk about this a little bit later And I won't get into detail on this, but just to point out that the subclassification subcategories are They respond differently to the different armament area that we have in terms of treatment modalities And so it's very important for the pathologist to specifically subclassify Subclassify the type of renal cell carcinoma. So on any Standard pathology report you're going to see the diagnosis renal cell carcinoma That's what it is and then the subtype somewhere buried in the report will say clear cell type Papillary type chromophobic type or something like that. So that's an important one important aspect of it to diagnosis The next important aspect is really the cancer stage And the cancer stage is dictated Really by the size of the cancer and it's local the local growth Is it extending sustained confined to the kidney is extending outside the kidney into the local fat Is it going to any regional lymph nodes that that might have been removed or is it extending into the the adrenal gland? Which might have been removed as well And so we analyze each case based on what we have and what we see This is a typical example of a partial nephrectomy specimen of a clear cell renal cell carcinoma With a margin that's out here here measures about 2.1 centimeters the margins negative This is a very small tumor of clear cell carcinoma. This is a stage out as a t1a a pretty low stage tumor This would have a pretty good prognosis based on that on that Staging profile now compare that to this particular tumor Which is a complete nephrectomy specimen showing the kidney a lot of perinephric fat Here's the sinus of the kidney and here is the tumor out here much bigger about 9 centimeters It's growing into the fat. It's growing into the sinus fat. It's demonstrating more aggressive local growth This would stage out. This is a microscopic showing it extending into fat We would stage this out as a t3a tumor because it's obviously more its larger and more infiltrative a Different example would be a same thing a renal cell carcinoma clear cell type This is a full nephrectomy specimen. Here's the kidney. Notice though the tumor is extending into the renal vein This is another feature that we analyze to look for we look for it grossly and microscopically and look for tumor extension Into that vein because we know that this will upstage The tumor the overall tumor stage and this is associated with generally adverse outcome It's telling us this tumors behaving more aggressively with its local growth in a case like this We might have received a lymph node. This is a lymph node with metastatic clear cell renal cell carcinoma again another aspect We would analyze both microscopically and under the microscope or Grossly and microscopically so we take all these features once we've analyzed the the tumor and we apply a grading system the American Joint Counsel on cancer staging the AJCC and we apply the pathologic stage Why because it's dr. Kim alluded to and we all know that? Cancer staging and it's true for any type of cancer the higher the cancer stage The more aggressive that that tumor will likely behave and therefore the therapy needs to be tailored to that particular stage Okay, and the report will clearly should clearly dictate. What is the tumor stage? And that's part of the standard reporting of any good cancer report Cancer the final cancer features are going to talk about a resection margin the grade Vascular invasion the presence of necrosis and then this unusual Circumitri to rabdoid differentiation. These are elements which go beyond cancer staging and the diagnosis Here's two exam. Let's talk about resection margins. These are indirectly related to or they indicate The local aggressiveness of a tumor if it's growing to a margin. It's ideally It's ideal that when a partial nephrectomy or a complete nephrectomy is that we have here is performed the surgeon always Tries to get the whole thing out. So we achieve negative margins. That's optimal sometimes It's not possible especially when we have a high stage renal cell carcinoma like this Which is extending into fat? Sometimes it's impossible to get a clear margin. This might again pretend some additional therapy When it comes to therapeutic Time for therapy with a smaller resection Sometimes it's impossible to get a negative margin or the surgeon needs to go back and take a cleaner margin That's interpreted for frozen section analysis Whatever to try and clear out that margin again because optimally went we want to try to achieve a negative resection margin The next factor is vascular invasion Vascular invasion when the tumor invades either into those lymphatics that dr. Kim talked about its surgery They have a propensity then to go to lymph nodes or they can go into veins or even sometimes arteries And then they have unfortunately the capacity to go to the lung or bone or other sites Those confer an adverse prognostic indicator Those are an indicator that this tumor might behave in a more aggressive manner So if we see it Microscopically we included in the report also if there's tumor cell degeneration undercrosis that is usually associated with aggressive gross growth of the tumor and We too will report that because sometimes that Will dictate how the next round of therapy will be undertaken dr. Kim already talked about tumor grade We apply the pathologist applies the tumor grade The Furman grade is the one that's used for renal cell carcinomas and it's a grading system from one to four Really it delineates the degree of differentiation grade ones are well differentiated tumor grade four are poorly differentiated and In any type of tumor it doesn't matter if it's breast colon renal cell carcinoma Generally well differentiated tumors behave better than poorly differentiated tumors So we assess the tumor under the microscope and we assign a a grade based on our observation And then finally sarcomatoid or rabdoid differentiation Most tumors will have just one type of differentiation. This is an example of a renal cell carcinoma The vast majority of it was this typical clear cell type renal cell carcinoma Sorry the conventional type But in it there were some pockets where the tumor cells Sort of had this unusual morphology under the microscope called sarcomatoid differentiation Or over here with a heat we had this rabdoid differentiates. You can see it looks very different than clear cell These for whatever reason are associated with tumor aggressiveness. So when we see this we need to report it We need to quantitate it and we put it in the report because these mandate some additional therapy independent of stage because they are really associated with aggressive tumors and All of these last category of features that I talked about once we've observed them We include them in the report and again usually enter any standard RCC report will have these features indicated in them Because they will potentially impact on the therapy Two quick categories and then I'll be I'll be done here I was asked to see a couple words about hereditary genetic syndromes associated with renal cell carcinomas and Again, this is taken out of that that long list that I presented a few slides back We all know that they're well known well-defined syndromes Genetic syndromes are familial syndromes that are associated with increased risk of developing different types of neoplasms including renal cell carcinomas notably von Hippel-Lindau Tuber sclerosis Burt hog debate these sorts of things The bottom line is as a pathologist I can't look at most of these tumors and say this is a clear cell carcinoma It's clearly von Hippel-Lindau tuber sclerosis or whatever all I can say is that it's clear cell carcinoma There are a few types of tumors that I can look at and if they have unusual Morphology like this tumor up here or this tumor up here I could say they don't comfortably fit into the typical types of renal cell carcinomas Maybe it is a syndromic type of carcinoma Very very rare less than 1% that we would ever suggest that to a clinician that maybe is this a syndromic but what we can do when we get samples like a renal like a renal resection like these three different cases where there are multiple tumors here We have multiple tumors or multiple cysts with here We have maybe 20 or 30 different tumors in this particular kidney or here's a younger patient with one two three separate tumors Then we can suggest that there's something odd about this because we do usually don't see this in sporadic type tumors Maybe it's associated with a genetic syndrome So multiple tumors cysts a young age presentation at a renal cell carcinoma or unusual histology Well, we will suggest to your treat treatment team that maybe this is a genetic or syndromic pattern of renal cell Carcinoma there's going to be more on this this after or later this morning on this topic the final topic for one minute I was asked to talk a little bit about the performance of secondary slide reviews. It's kind of important It's really important when you come to an institution for your definitive therapy It's always good to have that team and we do this all the time Review the outside slides to ensure that you have an expert team who works with their treating physicians And we work as a team through tumor board reviews and discussions of each almost every single individual case to ensure that We have the correct diagnosis. We've had the critical elements included in that report. We've under we've that these the specific Special testings have been performed and we have accurate diagnosis and staging and things like that what you need to do to provide is is when you come here is to provide the Copy of the report and a set of the glass slides the so-called recuts we sometimes call on the recuts That's really all we need to provide that incoming secondary review The other scenario is when you go off you might need to go off somewhere else for For some additional testing or some additional therapy and in that situation You might need to take or you should take a set of slides with you off to that institution Because they will probably want to do the same thing and review to ensure that we're all talking about the same disease process Remember that your slides and blocks when you're treated here or whatever institution generally those tissue blocks are stored in an incredible Huge file either in the basement of the hospital right below us here or in a warehouse as we have down in torrents They're basically saved forever So when you need to go somewhere in five or ten or fifteen or twenty years God forbid that there's a recurrence and you need to get some additional testing we can pull those blocks out of Torrents create a second set of recuts or a third set or four set And we can send it off to wherever it needs to go for some additional testing or evaluation And what you need to do is fill out this authorization form here at Cedars if you're if you're being treated here at Cedars And all you need to do is check off get a copy of the pathology report and please provide a set of recuts It'll take a few days two or three days We'll get that for you we can send it to where it needs to go or we can give it to you directly And you can just carry it with you to that next institution or wherever you need to go All right on that note. I thank you for your attention and I'll take any questions either now or during the break I know I think I'm a little bit over Thank you So in our efforts to try and stay on time Dan's available for a few minutes and let's take a coffee break and come back in 15


Well, administration officials say slowing economic growth and a deepening worker shortage has shrunk Minnesota's projected budget surplus to just over $1 billion. That leaves lawmakers nearly $500 million less to work with as they begin assembling the state's next two-year budget. Governor Tim Walz and other Democratic leaders say the updated forecast shows the need for more spending on education, jobs and transportation, and stepped up efforts to attract workers from other states. Republican leaders say high taxes are the problem, and the tax hikes Walz proposes on gasoline and other items will only choke off growth and make Minnesota less attractive. The updated forecast is now the starting point as legislative leaders set final spending targets for hammering out a budget before the session adjourns in late May. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


ṬṕṢaba nī ṬṚṢamutra palatichhi Ṛādialṣahara. uldghātana ussa bra ṬṚṢaṃ atihāsi ka joghe matdharu m'aṣṭā jātra bhari ṬṚṢaṃ m'aṣṭaṃ manchare pakĒle bhāk ch Ballahā aaṭi Āti, ṬṚṭhāti jātua ṬṚṭhāti Āti yaṭa ṬṚṭaṃ Ṭṭhāti.  endings, left books and stories of smartphone how much is r fr e వారడాసంమాతూత్తోందొత్నిరందునిల్దురissyటర్ఞ్. దాప్రారిందారోనినుదామిరందు. For know this tension is rising to the Mint for a few months but still maybe a dust to silicon we'll have that kind of a special announcement everyday January 3rd, AarambohitーバKhadiyal couple have held a 마чabha in February 2 After chaining someone dropped a small jewellery down to college flashy jewellery Toni's first night was really disturbed Zoopan was very excited to see it With this our video was finished Please like,share and subscribe to our channel Earth I love that you were so cute when you made me laugh ?


Yeah. Oh, now you can see everything very good, very good. Okay. Okay. So we go to the next page. Can you still see? It's a little out at the top from now. Now it's good. Now it's good. Yeah. Okay. Now the integrable highest weight g-height modules with central charge is small c. So, so see this is small c was the level of the central charge which was fixed once and for all. So now let's look at integrable highest weight g-height modules. So g-height is the finally algebra with central charge c and central charge just means the action of this capital C, the central element. So that is in bijective correspondence with the set dc which was introduced on the last page. So dc was this set consisting of dominant integral weights such that lambda theta check is at most c. Okay. So, so this dc parameterized edge all the integrable highest weight g-height modules with central charge is small c. And let's denote given any lambda in dc, let's denote by each lambda the corresponding integrable highest weight module. Now, so this is the fundamental object in this conformal field theory. So this is the space of dual conformal blocks. And there is also a similar conformal block, but that's just the dual space of conformal blocks. Okay, so now we have already taken the S pointed curve sigma p, where this p vector p consists of as many points, all of them are smooth and distinct. Sorry, I should have mentioned that there is smooth and distinct points. Now, we take one more ingredient here. And that is this vector lambda, which consists of lambda one through lambda s exactly as many as smallest many. And this lambda i is attached to the point p i. And what is this lambda i so lambda i is an element in DC. So we are thinking of that each point p i is attached to a representation h of lambda i with same central charge so we are not changing the central charge c. So we define h lambda to be the tensor product of all these. So h lambda one tensor up to h lambda s. So that's now on this one. So this is the algebra. And what is this the algebra g tensor c sigma minus p. So what is that. So we are removing the points of P one through PS from Sigma. Okay. And now we are taking the affine coordinate ring there. And we tensor it with G. Now this is the algebra. Okay, so so I should define the bracket first. So the bracket here is maybe maybe again it might go off the screen. So the bracket here is extensor f y tensor g. That's the plane and simple bracket x y tensor f g where f and g are functions on sigma minus p. Now there is one technical thing I'm crossing over. And that is the choice of P should be such that every useful component of Sigma must get at least one point. Sigma minus p and a fine variety and that will that will give up for us a ample supply of regular functions on Sigma minus p. In any case, now the basic object is this dual conformable blocks. And that is, we take this H Sigma, sorry, it's Lambda, it's vector Lambda. So that's the tensor product of these representations. And we mod out by action of G tensor c Sigma minus p to each Lambda. Now I have not told you exactly how it acts on each Lambda, which I'm going to tell you a minute. So take this le algebra act it on each Lambda. So that will generate a sub space of each Lambda take the quotient. And that is the basic object in conformal field theory that is called a space of dual conformal blocks. Now the conformal block is nothing but a dual of this space. So dual dual is the conformal block. Now, now let me tell you what is the action of G tensor this C Sigma minus P on each Lambda and that action is given by is it in focus. Can you move it to the left and a little bit down also. Yes. Yes, I think we can see it now at least for a while. Okay. So X tensor F where X is in the le algebra and F is a regular function on Sigma minus P that acts on this tensor product V1 tensor vs where Vi is in H Lambda I and F is a regular function on Sigma minus P. So this action is, we take the sum from one through S V1 and on the ith factor we act by X tensor F. Mind that F is really a regular function on Sigma minus P. So what we do, we take it's, we fix a local parameter at the point Pi. Okay. Now Pi is a smooth point. So we can, we will have a local parameter. So let's fix a local parameter Ti on Sigma Pi. And now we take F at Ti is the Laura series expansion of F at Pi through the coordinate Ti. So we use this coordinate Ti and get a Laura series expansion of F at Ti. So that will give us so F Ti becomes an element in the Laura series in Ti. So that will act, see the H Lambda I was going to be acted upon by G tensor CT are the central extension of that. So that's the action. And we sum over from one through S. Okay. Now, there is this lemma, which says two things. First of all, this is space which I defined the space of dual conformable block. This is finite dimensional vector space. So that's fact number one, which is not too difficult to prove but that it does require a proof. It's, it's not totally straightforward, but it's not too difficult either. So this is a finite dimensional vector space over complex numbers. Moreover, it does not depend upon the choice of the local parameters. So I said that let's make a choice of local parameter Ti at the point Pi. It does not depend upon the choice of the local parameter up to a canonical isomorphism and that canonical isomorphism is canonical up to a scalar choice. Now, in this whole theory, there is the whole thing depends upon a choice, which is usually okay, but only up to a scalar multiple. Now, this is a finite dimensional vector space. Now, it depends upon the curve sigma, the points P, and the choice of these weights lambda one through lambda S in DC. And it's a finite dimensional vector space. So if you have a finite dimensional vector space, the most important question, the most basic question is what is the dimension of this space. As I said, this is based depends upon the choice of sigma, the curve, the points and the choice of Lagrange. Now, Eric Warland made a conjecture in 1988. And actually it's interesting. He made this conjecture. I think while he was at the Institute for Advanced Study, where I am right now. Okay, so, so now I am going to tell you the basic idea of the proof. The full proof really is fairly long. It has several other ingredients and many of those ingredients take several, several pages. Actually, if you write the full proof, it will be, it will occupy 100 pages. But I'm going to give you the basic idea of the proof as to what are the main ingredients and how does one really prove that. So, so I'm going to list some of the theorems and I will explain to you. Okay, so again, it might have gone out the focus is the last lines readable. It's a little bit to the right, can you move it to the thing to the left. No, I move it to the left or I move it to the right. You can see your mouse, instead of your paper. We can see your mouse instead of your paper. Okay, okay, okay, okay. I see, I see. Okay, okay. Okay, so, so I know what do we do it. Can you see the paper now or it has gone even worse. Move it where the mouse was. Ah, okay. How about this. You're still missing something at the right side of your paper. Oh, right side of the paper. You moved the camera to that. Yeah, now we can see it. Now you can see it. Okay. So the first theorem, it is called propagation of Vecua. So what it says, so this V Sigma is the space of dual conformal blocks. So V Sigma P Lambda is same as we attach one more point. Okay, we attach one more point. Let's call it q zero. This should be a distinct point and it should be a smooth point. That's the requirement that it should be a distinct point from peach and it should be a smooth point. And to that point to be we have already attached these weights lambda I, but to the point q zero q zero, I am going to attach the weight zero. The central charge is still small C. So the corresponding representation of a finally a zebra is not the, the trivial representation is the representation with G highest weight zero but central charge small C. Okay. Let's move to the next page. So that's one theorem, and it says that you can add more points without changing the dimension as long as you attach the weight zero to those points. Now, next comes the factorization theorem. Is it visible. No, it needs to go towards the mouse again to the left. Yes. Okay, very good. So the next theorem is called factorization theorem. And it is a very important theorem in this whole theory and you will see why, but let me first explain the theorem. So, so let's start with a nodal car. So it can have one node and it can have several nodes. So no basically means that it's a singularity of the type x times y equals zero locally. It just means that it has a singularity of x times y equals zero. So let's start with a nodal curve. But, but keep in mind that the, the, the points P vector, these are all the smooth points. And let small q be that nodal point, which we are just going to choose one of them. I mean, it might have several nodal points, but I'm going to choose one of them are fixed one of them to. So that's the node nodal point. And now I'm going to take the normalization of the curve only at q. So we are going to normalize the curve only at q. Sigma height be the normalized curve. And now this q will blow up into two points q prime and q double prime. Now this, even though Sigma was connected, there is no guarantee that Sigma height will be connected but but never mind. Okay. So now this factorization theorem, what it asserts that this V Sigma P lambda that was the basic space of dual conformal block that space is canonically isomorphic. And again this canonical is up to a scalar this whole theory is canonical is up to a scalar so projectively everything is canonical, but not otherwise. So now we are going to take the direct sum where mu runs over all the weights in DC, they're only finitely make many weights in DC, because lambda theta check has to be at most C. So they're only finitely many weights. So now we take the space of conformal block not for Sigma but for Sigma height, where we have now this point q has been resolved, and it has obtained two smooth points.  So the smooth points in Sigma, they remain of course is smooth in Sigma height. In fact, we have not done anything to them. But now I add two points q prime and q double prime. Now they have become smooth points in Sigma height. So this is completely legitimate. The original one attached to the points p, but now to the point q prime I attach mu star, and to the point q double prime I attach the weight mu, where mu runs over DC, that's a finite set it's running over that. So now I take this finite sum of dual conformal block, and this factorization theorem says that the original space of conformal block is isomorphic with this direct sum of these conformal blocks. Now, let me tell you right away what is its importance, and we will tell, I mean we will discuss it in more detail in few minutes. If the arithmetic genus of original Sigma was G, okay, so arithmetic DNA genus just means that H upper one of Sigma with coefficient in the structure sheath. So arithmetic genus G is nothing but dimension of H one Sigma or Sigma. That's the definition. Okay, so now. So, when we start with Sigma with arithmetic genus G, the Sigma height has an arithmetic genus G minus one. So, right away what we see that when we are calculating this dimension of conformal block for a curve of genus G. We reduce the problem to a genus G minus one car and eventually we will inductively reduce the problem to a genus zero curve, which is nothing but P one. Anyway, I'm going to come to this in more detail in few minutes. Okay, let's keep up. Okay, I am two more minutes before now. So, so far we talked about conformal blocks are dual conformal block for a single car with some mark points P, and weights attached to that lambda. Now we are going to shift if I the situation and how we are going to shift if I we are going to take Sigma T over T a family of S pointed curves. So basically what it means that T is let's let's say T is a smooth scheme, although it does not have to be just for convenience let's assume that T is a smooth scheme. And Sigma T to T is a proper morphism and a flight morphism, proper and flight morphism. And what we are requiring that this pie this map from Sigma T to T had sections now P one through PS, and PI are sections of pie. They are mutually disjoint at every point. And if I take a small team capital T then by university is a S pointed curve for any geometric point T in capital T. So what we are doing we are just if you find the earlier situation. Now we are allowing a family of curves with. I mean family of marred family of curves with Mark points, but we are keeping the same lambda we are not changing the lambda. So we will still keep lambda one through lambda s, and we will attach at every point is multi in capital T, the same lambda one through lambda s. So this gives us chief of conformable blocks. And so we have Sigma T pre lambda. So this becomes a sheaf over T now. And the sheaf has the property that if I specialize the sheaf at a small tea in tea, then we get the original sheaf up, sorry, space up to a conformable block, but we can shefify the situation that's the sheen. And I see that I have just 25 minutes. So we can have a few minutes break at this stage, unless anybody has any question.


Let's see what that means. I'm quite curious. I haven't been running apps on my desktop. So, welcome then. So, Chashlik, in the beginning, alright, I'm a bird sometimes. Right, my name is Dan Lane, and I've been with KDE for some time now, very nearly a decade. I'm a master's of software construction with some crazy title that didn't fit on my diploma. And over time, I started my involvement in KDE in the Amara community, but since then, I've been working with Caligra, and I've been working with the glue on team. And most recently, I became an employee of Blue Systems, in which capacity I am on this stage today. So, as a base concept of this, I want to explain why Blue Systems is interested in doing something like Chashlik. So, the plasma foam stuff that you've been, that everybody's been very excited about recently, has been all about getting our stuff to work on phones. And getting the sort of the convergence, these are very nice words these days. So, getting our stuff to work on other devices is kind of where we want to be. But obviously, the opposite is also true. So, we want to get stuff that currently runs on phones, all of these apps that are available there. We want to have that also available on desktops, which is the current primary goal of Chashlik. So, it will eventually run on phones, but right now, that's not the prime goal. We will get that, but it will take a little while. So, first of all, now, Android, everyone will tell you, in particular the Linux Foundation will tell you that Linux runs on billions of devices out there. The problem is, they run Android, which technically is Linux, but not really. It's Linux in the sense that there is a kernel. But everything from there and up is different, which is lovely. You have Binder, which is an IPC system, inter-process communication system, which was developed for BIOS, if you remember correctly, which is old but very, very efficient. It is not very popular in security circles because it's basically siphoned directly into the kernel. However, it is now available in the mainline Linux kernel, so we can work around that for now. Then you have Surface Flinger, which is something of an issue in that Surface Flinger is traditionally the way to access the hardware, where we have other ways of doing that on Linux. We have something called Open Drivers, which Android hasn't really worked out yet. And, of course, there's the whole way that Android applications get run, which is through the Dalvik runtime, or the new version, which would be the Android runtime, which is something called Cilic. Basically, the idea is you have the central virtual machine, which contains all of your system processes, and then any application will request a copy of that runtime, and then applications run inside that. Now, the problem. Obviously, there are a lot of applications out there, and we would like those on our systems as well. That's the main issue that I've been talking with some people recently, and they were asking, why are you doing this? Why would we want all of these apps on our perfectly functional Linux desktops when we have all of the content in the Ubuntu repositories, and we have all of the applications in OpenSUSE, and all of these wonderful things? The problem is they're not the things that a lot of people out there want. People want Candy Crush, and that's not really available in there. The problem with being that none of the ones on Android currently run on a normal Linux. You've got a couple of options for doing that right now. There's the Android emulator itself, which requires you to install the Android SDK, and it is terribly awkward to get anything to run inside it, and they're all virtual machines. There's the ACL as well, which is also a virtual machine, and they all come with that weight that a virtual machine comes with. They are emulating a processor, and there's a virtual computer running inside your computer, which, given the nature of a lot of these applications, would potentially not be that much of an issue, but we'd rather not. It's also awkward to do. Then there's the remote run option, which is stuff like advertising and manual, which is basically you put an APK on some server somewhere and they run it for you, so the popular other people's computer issues. Then you've got web browsers. I understand Firefox are working on something similar, so it will run on Firefox OS, but there's the one that was in the press recently called ARC, which basically means you wrap Android applications in something which makes them run on Chrome, but if you don't want to run Chrome, then you can't run that. So what we're doing is taking the Android stack and removing the bits of it that make it really awkward to run on Linux. So we're taking out the OpenGL code. There's a lot of weirdness in that, which means that you can't use the same libraries that exist on Android on Linux, and yeah, it's terribly awkward, but that's why these things take time to get to work. The base concept then is that because this is running Android on a real Linux system, not inside an emulator, not inside a web browser, not on other people's computers or whatever, we have the ability to really deeply integrate stuff, so that's what we want to do as well. And then, of course, surface flinger itself is there. We can't really very easily get rid of that just because there is the possibility of getting rid of surface flinger. If you only run pure Java-based applications in Android, then you can do it. That's what the people in Gentroid have done. Good friends of ours. Well, good work, people. And yes, we work with the Gentroid people. Lovely guys. But surface flinger itself is required for getting anything that's based on the native SDK in Android to run, because they interface directly with surface flinger. We need surface flinger, and what we've done there is that we have ripped out all of the hardware abstraction stuff, and then that hole that was left behind was shaped pretty much like Wayland, so we put Wayland into that. Now, an interesting thing about that is the code that existed there. The code that existed before, people have done things with Wayland and surface flinger and trying to get the two to work together before. The case in point would be the YOLO phone. Salesforce OS is basically doing that. The plasma phone itself is doing that. But what that does is it's putting Wayland on top of surface flinger, which then handles the hardware bits. We don't do that here. We just have to have some EGL surfaces to paint on, which we then get out of Wayland and surface flinger can work with them. It sounds very simple. It's not, unfortunately, but that's the current process. And then we have currently a small application that handles this. Basically, there's a lot of services and things that need to run. This is not a final UI. We'll need to speak with the Visual Design Group once we are a little bit closer to having something that works properly. So, obviously, work in progress there. But the idea is obviously that all of that functionality will be hidden. And the idea is that run an APK button up there is not a run APK button. It's a double click on an APK, install a launchers, application shows up in your menu. And so the idea is to have Android applications, of course, running as full proper citizens on a real normal Linux desktop. So, yeah, that will eventually go away, but right now it's a useful little tool. So, a little demo. Now let's see if I can get this to work. No, it's not working. That's too wrong. There's that controller. And there is Western, which is a Wayland compositor that runs on top of X windows. So, useful little tool for us to do some testing on. Now, I click start all services and a black screen shows up.  Right, so all of the output you can see in the background here is Android running. It's dropping events because there's no touchable windows. There's no application running, so there's no input window. But that is a running Android system. Oh, that is a running Android runtime running on pure Linux. There is no hacks, no changes to Linux itself. It is just Linux, standard user space. One change would be binder, but given binder is now in the mainline kernel, that's not really a hack. But yes, that is... I'm putting a B as interesting as that demo gets. I did my thing though. On account of this whole Wayland thing, I'm switching between Queens as well, so I've lost my shortcuts and I can't type them into the correct window from my scale. Oh, yeah, and now even show up. I've stopped all the services. I'm probably someone with a flappy bird, so I had a flappy bird. Now, what's up next? Now, other than, of course, getting something installed and actually having a flappy bird on screen and being able to play the game and all of the other things that you can do with it. Okay, so my personal goal for this is something a little bit more, I guess, enterprise-y. I have, I'm afraid, not an open form. I have a library passport. It runs BV10, and there is this lovely little application that makes it possible to mirror your messaging system on there, on your desktop, but that only works on Windows, on macOS, and on Android. But, so once we have applications up and running, all of the integration begins to become a point. So we have all of the, it's not just frameworks, there's all the other things as well. As much as possible needs to be done through the FDO specs, all the notifications, and all of that stuff will end up being done through the proper standards, probably using the KDE libraries to provide the functionality. But, yes, so it's all stuff like notifications and contacts, like integrating K-people into Catholic and the task, having the task manager show the Windows, each application rather than just have a single window which contains everything, which is also a problem. Atlas teams in your K-menu, and, yeah, all of these things that make the, that will eventually make the applications run as full citizens, like proper, full, you run an application, an Android application, and you can only tell that there is a difference because, well, it's going to still look like an Android application, but it will run, and it will show your content, it will show itself in the task bar, and you've launched it through the K-menu, and you've, you know, all of that. And then, yes, obviously separate Windows, perhaps. Now, the idea for the controller is to make it a little bit more in essence, I guess, like the, what's that called, the Settings app on Android. It has a lot of detailed statistics for each application. We can't really sensibly filter that into the existing package managers, but as much as possible we want in there, but some things we will need to be, we'll need to have the controller if nothing else for debug purposes, so, yeah, you can't see that because resolution, but, yeah. And then, right now, it's KitKat, and we want to obviously, we want to upgrade that to Android and when that's out, and then so on, N, O, P, whatever, whenever they start coming up. And then people have been asking, oh, but where do I get my APKs? How would I, you know, get all of my applications, all of these many, many thousands of, you know, it's not hundreds of thousands of applications out there. Surely you're not expecting people to go and rip them from Play Store or, you know, whatever. No, the idea is to integrate, again, deep integration into the existing frameworks that we have. There's a wonderful little thing called Moone Discover, which is a sort of centralized application portal for multiple sources. And it's, you know, applications and content, both. So, if we can, but for Froid, I don't expect it would be that much of an issue because it's all open, but the other two might be a little fun. I know that people have done it for Google Play. There is Snap for BB10 and there's a Google Play client type thing for YOLA as well. I think the latter one is even open source, so it should be possible to get at least three apps from Google Play. Amazon, no idea. I don't believe they have an API because this is Amazon. They don't play well with others. Even worse than Google. But, yes, the idea is to integrate as many of the existing stores out there into Moone Discover, potentially, you know, also AppStream, if we can get that to work. And then, obviously, bugs, bugs, bugs, any bugs. And, yeah, once we have all of it done, there's what they're saying about the sound bug content. So, now it's a little bit faster than I expected, but questions? In your phone, if you install something on Linux, would you be able to see it in your phone? Well, in that this is a Linux-based system, the whole thing where you install apps through the Play Store, or the way that, you know, you can go onto the web, like this online device, so on, is a little bit different here. It doesn't quite work like that. That requires the Google services, and that's very specific. But, technically, because we get the APK, I don't see that... Well, it wouldn't be impossible, at least. It's not a... I haven't thought of that one. But, yeah, I can see it working, at least. How do you do something like that?  Oh, well, that would be more a KG Connect thing, I guess. But, yeah, actually, that's a point. Having Shashlik integrating with KG Connect would be really useful. Yeah. Note to yourself. What language is Shashlik from? Shashlik? Well, it does sound orcish, and that would be because I believe it's Russian. It's... Right, so the snack itself... Actually, the Shashlik name is Turkish, I'm told. But the picture I found... The Shashlik picture, that one. That picture says it was Russian. It's sort of that kind of area. I mean, it's a kebab. It's a huge kebab, basically. Sorry. Does anyone here have a cultural connection to Shashlik? There you go. The different architectures and question number two is, is it technically possible to... When the Android model is executed inside the Shashlik, then you can offer the underlying little system for that? Well, yes, you would technically... Well, start from the far end. If I understood the question correctly, you will be able to detect from inside your application if it's running inside Shashlik, because Shashlik has the... The same way you would detect any Android build on any device, you can detect if it's running on an XS5, or you can detect if it's a cyanogen or so on. That information is registered as Shashlik and Shashlik runtime inside the VM. So if you request the version information from Android, it will tell you that it's running on Shashlik. What was the first one? I thought the first question on that was, it's to be made by... Oh, yes, the native stuff. Yes, right. So what we've discovered is that applications which are distributed on the Play Store, at least, will tell you what architectures they're available for. And inside the same APK, you have libraries for all of the different architectures. So, you know, say, Flappy Bird. Again, Flappy Bird has inside the same APK, you have libraries for ARM, two or three different versions of ARM. You've got MIPS, you've got X86, and so on. So it's... That's the thing. Shashlik is not an emulator in the same way that wine is not an emulator. There is no hardware emulation going on here. It's an API that runs directly on top of your local native system. So it's all... If the application lacks its X86 support, it will not run in Shashlik. Technically, I guess it would be possible to do but it's not really in scope at the moment, at least. So, yeah. Let's get the proper sort of system running first and then we're going to get the emulation working. My question is simple. When can I run VLC on Android? Which one? VLC on Android. For VLC, for example, we need SDK, we need NDK, and we need also private NDK APIs. Private is a problem. Not an enormous problem. It's solvable, but right now it's a problem. We supported the VLC in the last month to a code, an ARC, an Android Entertainment Code, and we managed to get a few things on that. There are APIs where you actually need private APIs. Is it possible at some point? It will eventually be possible, but we'll need to... Yeah, we'll need to look at that. Right now it's not out of scope, so to say, but it is not currently possible. Well, yeah. Well, obviously some of the private stuff is bionic. We don't have bionic. We have... Oh, the frameworks stuff. Yes, the frameworks, private stuff, that's all there. Yeah, that actually, yes, that should be possible. We will need to look at it, and that is one of the things that we're working on at the moment. So, yeah, but, yeah. Actually, let me just do this. But, yes, let's talk later. Right now? Okay, so, Plasma Phone. Yeah, someone was going to ask that at some point. Right. So, running it on Plasma Phone at the moment is a problem, because there is already a surface layer on Plasma Phone, because it uses Lepimeras, which speaks to the hardware through a sort of... sort of kind of surface layer. No, you don't use surface layer. Are you sure? There's no surface flinger process running on the phone today. If we can kill the surface flinger on Plasma Phone, then, yes, it will be possible. Basically, the problem is that if you have Lepimeras running with the surface flinger, then the two surface flingers will be fighting over who gets to speak through binder, because it's supposed to be, essentially, a single-term type application. But, yeah, in that case, yes, if there is no surface flinger on the phone, then, yes, we can do it. It'll take some time, because also, right now, it is an x86 project. We will need to add the stuff to Shashvik to get that to work. But, yeah, it should be possible. Is it not just saying things? Yeah. Do you think this kind of thing could upset some application developers? Because it seems like a useful base for, for instance, for creating applications like information, or checking out games, or debugging them, and... Um... Well... Right, so Shashvik is not very useful for that sort of spying on applications type stuff. So I wouldn't think that Shashvik itself would annoy people. The Android emulator itself is much more useful for that, because it has all the debugging tools that are already there, because it's a part of the SDK, and it's supposed to be used for that. So, yeah, I wouldn't think that we would have that issue, at least, on purely on a political level, at least. Important to do devices. Is it a meaning, similarity, that you touch the device... Nope. That's the thing. Because we don't use the hardware extraction stuff, we are just using system libraries. We're using the system EGL, we're using the system OpenGL, everything runs on Mesa. So, and that's, that's really the problem that we have with plotting, we want to touch on all the other libraries-based things to new devices, is that, essentially, you need to modify the libraries to work with the odd quirks that exist in the various drivers. And we don't have that. What we do have, though, is because it is Android, there are some fairly specific requirements to versions of specific libraries. But most of that is something that we can deal with. And it is getting better. As Android gets older, interestingly, they also fix a lot of this sort of hard-coded line-redependency type stuff inside their own code base. So, I have a suspicion that when we do upgrade to Android M, some of that will go away as well. So, let's bring that first. Yeah. So, unmodified Linux or unmodified Linux means my kernel doesn't need binary support? Unmodified Linux means you need to enable that standard option in your kernel. Sorry. Right now, you need Binder, hoping to get rid of that at some point. So, there's a lot of other people, they actually want to get rid of it in Android itself. But they looked at kdbus and found out that kdbus is not an option. So, yeah. But because obviously our requirements are somewhat smaller than what they have. We're not contacting the hardware directly. There's a lot of stuff that we may very well be able to get rid of the Binder dependency. But yes, right now, you need Binder. All right. Thank you then. Thank you.


Welcome to World's Best Videos. This video is presented by Miraculous.com We've combined the list of facts about social media sensation FaZe Tico. Let's get into it. Jacob, or better known as FaZe Tico, was born on October 24th, 1993 in Sweden. He is currently 23 years old and resides in Los Angeles, California. Jacob grew up in Sweden with his mother, father, and older sister. His biggest passion growing up was playing with Legos. He played soccer and hockey growing up as well. As a kid, he wanted to become a professional soccer player. The first gaming console he ever played was on PlayStation 1 and would play the game James Bond. From there, he switched the first Xbox later upgrading to an Xbox 360. Tico would always play Counter-Strike, but after hearing his peers were playing Call of Duty, he purchased Call of Duty Modern Warfare. A week later, Modern Warfare 2 was released and he got into sniping. He then would watch videos about Call of Duty and decided to try it himself by setting up books and his parents' camera. After getting an invitation from FaZe leader FaZe Temper, Tico joined FaZe in April 2011. But sadly, after playing video games consistently, Tico eventually grew tired of the same pattern and quit on July 11th, 2012. Throughout his break period, he didn't game often. Instead, he would produce music and got his music featured on the biggest DJ record label. On May 20th, 2014, Tico messaged Temper after having a dream of the leaders of FaZe and him hanging out. He would then get a flight to Boston and get invited to join the FaZe house. His favorite candy of all time is M&Ms and can be found eating it often throughout his videos. Tico mentions his biggest accomplishment was moving out of Sweden to pursue his dreams in the United States. Well that concludes the video guys, hopefully you guys did enjoy the video and if you did remember to smack that like button. Let us know in the comments section below what you'd like to see next and if you haven't already subscribed please do subscribe to keep up with the world's best videos.