While the previous generations of the Raj Zephyrus were not as impressive as Asus hoped they would be, the laptops paved the way for Asus and AMD's relationship. From it, we got some amazing devices, such as the Strix Scar 15 G533, the Zephyrus Duo 15 SE, GX551, and more. Asus is hoping for a third times the charm, moment here, as they have released a new Zephyrus device, in the face of the Asus Raj Zephyrus G15 GA503. It is powered by the Ryzen 5000 series processors, not the U-Series, but the regular H-Series, and the RTX 3000 series Ampere GPUs which are just insane when it comes to performance. Today we are presenting you with laptop media's top 5 picks about the Asus Raj Zephyrus G15 GA503. Being a part of the Raj lineup, you should expect an amazingly built laptop, and we weren't disappointed at all. The body is built from a magnesium aluminum alloy, which makes the laptop both sturdy and thin, because metal sheets don't need to be as thick as plastic ones, in order to provide the necessary durability. There was a bit of flex, in the lid, but nothing out of the ordinary. The base, on the other hand, is super stable thanks to the honeycomb pattern on the inside. The weight and height are OK considering the dimensions of the device, sitting at 1.90 kg, 200 g lighter than last year's device, and 19.9 mm. The lid opens easily with a single hand, which signals the premium build quality of the laptop. The lid also has the Ergo Lift technology, if we can even call it that. What it does, is prop up the base of the device, so that the fans have more from to breathe. The design is also on point, with the lid having a dotted matrix design, that shines in different colors thanks to the prismatic film underneath. The branding isn't overdone, with only a small glossy Raj logo on the lid. Please remember, it would be of great help to us if you just hit the like button and subscribe to our channel. That would motivate us to make even more and better videos for you. While half of the RAM is soldered onto the motherboard, the rest is upgradeable via one Sodom slot. The RAM works in dual channel, so make sure you pick appropriate frequencies so that you can take full advantage of the performance of the laptop. As for the storage, there are 2 M.2 PCI-EX4 drives, which make storage upgradeability super easy readily available. If you need help in accessing the Sodom or the M.2 slots, feel free to check out our detailed teardown video. It shows everything that you need to do in order to access the slots without damaging any of the components. The display of the Raj Zephyrus G15 has a diagonal of 15.6 inches, a full HD resolution, and an IPS matrix. It has excellent viewing angles, and a maximum brightness of 340 nits, with a deviation of 13%. The contrast ratio is great, sitting at 1,350 to 1. Furthermore, the display covers 100% of the sRGB color gamut and almost matches the DCI-P3 gamut, resulting in an amazing image with vibrant colors. You also shouldn't be worried about your eyes, as the panel doesn't use PWM to adjust its brightness across all brightness levels. As for the color accuracy, we tested it both with the factory settings, left, and with our design and gaming profile applied, right. We got a Delta E value of 2.2 when using our profile. The speaker setup is very well implemented on this device. There are a total of six speakers which are surrounding the device. There are two tweeters on the side of the keyboard, which are front firing, and the rest, which are 4W woofers are put in couples firing in different directions in order to minimize case vibrations. Overall the setup is pretty well engineered. In our audio test, the speakers delivered clear and high quality audio with no deviations across the entire frequency range. Overall the keyboard unit here is pretty good, but there are a few tiny things that keep it from becoming top tier, some of which are negligible for people. The unit has a long key travel and nice clicky feedback. It lacks a numpad, but has a backlight, so you win some you lose some. Furthermore, the arrow keys are pretty tiny, which might be a deal breaker for some people. Fortunately, there are some dedicated keys for mic and audio control as well as the ROG Armory crate. The power button also doubles as a fingerprint reader, upping the security of your device.


Okay now that the scenes started to come together we're going to take a look at the render settings and that means that when we're rendering everything is going to be a little bit higher quality because we're going to change some settings. So to get to the render settings window it's this icon here which is the display render settings window we'll give that a click and there are a few things that we want to change. What we're going to do first we're going to go into the Maya software tab we're going to change something in here so by default the overall quality is set to custom which I think is Maya code for crap. So we're going to change custom to intermediate which is not the best but it's a good trade-off between quality and render time and then we're just going to scroll down a little bit further and we're going to turn on ray tracing. Ray tracing handles things like reflections, high-end shadows, weather light, refracts, bounces, things like that so it's really good to have that turned on and that's the thing that in a second is going to make the projector look really sexy because that's now going to start reflecting. And then we're going to go into the comment tab and we're going to just scroll down until we find the presets by default it's at HD 540 which is okay but it would be a little bit better if it was at HD 720 you can go higher if you want but for my purposes 720 is enough and then click on close. Now frame up a beautiful shot of your room I want to get my creasing shot I think so I'll try something like that do a test render and see what it looks like. So you should notice straight away that the window is a lot bigger but also that it's taking much longer to render and that's because it's doing a lot more complicated stuff with it it's working a lot more out. Straight away you can see that the reflection on the the projector is working it's actually a little bit over the top I think that's more to do with the placement of my light than the reflect the reflectivity being too high but I could turn that down or I could reposition the light you can see everything's looking much nicer now as well so I think what I will do is I'm just going to move this light if I can select the light so I want that light and I'm just going to try and move it off centre like that I'm just going to render again now just to see if the reflections on the projector are a little bit less ridiculous. Any second now? Yeah so that's nicer so it's still very shiny but the colour's coming through and it's got that polished plastic look that I was going for and don't forget to get a real idea of how your scene is going to look don't forget to turn the gamma correction off and that'll give you a nice overall look so very moody very gritty but very sexy


Hi, this is Yoho Sapil Bharati and today we have with us once again, Ibrahim Haddad, VP of strategic programs AI at Linux Foundation. Ibrahim is great to have you back on the show. Thank you Swapnil. I'm happy to be talking to you again. Last time I think was very cool. And today we are going to talk about the recent open source license compliance report that you authored. Let's just go ahead and do basics because last year we saw some disturbing, we should not, I mean, it depends on who you look at disturbing, you know, where companies change the license and then the community responded with open source projects. So I just want to look at open source license in general. When we look at this modern world companies, I mean, most of the code that is being written is open source, but, but a license is what kind of brings, you know, companies or products together because compliance is a big issue. I remember in early days with Linux kernel, the reason Linus chose Ganu was that it was, you know, he knew that what projects he can work with, you know, versus everybody writing their own license, it's not compatible. So I just want to understand in modern word, how does open source license matter for the sustainability of open source? So let's go to the basics. So I think as a background, I have been involved in open source license compliance since year 2000. So it's been almost 24 plus years. And that goes back to the days when I was an engineer. And I was responsible for figuring out what is open source license compliance at a time where there were no knowledge or public knowledge. And we started from studying, you know, what is the new GPL, what is the Linux kernel, and how we can use it. And this is how we started. So fast forward 24 years, we are today in a place where not a single company in the world, regardless of what industry and specific vertical they operate in, can actually offer any services or products without using open source software. So from the moment as a consumer, as a person from the moment you wake up, till the moment you go to bed, you are touching open source software in pretty much any action you do from looking at your phone, from online shopping, from streaming, from using your bank, etc. So the importance of open source license compliance lies in the fact that there are numerous numbers of organizations, thousands of them and hundreds of thousands of developers that are coming together and collaborating on some of the largest software projects we've ever witnessed ever. And all of this code is being available as if you wish, open R&D licensed under an open source license that allows anyone out there to look at the code to modify it, change it, customize it for their own use, redistribute, etc. So there is a massive amount of technology assets in the billions of dollars that are being available for use. And in return as a company or as an organization that you are using and deploying this kind of software assets, the only obligations you have is really to respect the license under which these different software components and technology pieces are being available. So from that perspective it is extremely important to respect the license and in some cases make your changes available under the same license depending on kind of the originating license like the GPL for instance, because that beyond kind of the legal aspect of it, it actually shows that you as an organization, you appreciate the software and the effort of the thousands of people coming together to produce this and you are being a good citizen of this ecosystem and that's your contribution back for using the software is acknowledging the effort and respecting the licenses of these different communities and projects. But certainly from 24 years to go today a lot has changed and the ecosystem today is very different and you've noticed you mentioned the new introduction, change of licenses. So there are a lot of new licenses entering the ecosystem, different startup organizations are licensing or changing their license for their software projects to accommodate certain business requirements if you wish. So it's a very dynamic and moving space. Now let's talk about the licensing when it comes to open source. In general, let's say there is no open source license for example and this is I'm going to very, very basic because I think you and I, we have been working open source for so long that we kind of take it as a granted that everybody understands that but that is not the fact that there are new companies and then there are a lot of companies. So like when you read a piece of technology and then two companies want, they will go and negotiate the terms of usage. You know, hey, you can do this, but I think licenses kind of make it open and sometimes, you know, some of the open source license whether you go with FSM definition, whether you get go with OSI, this is what you can do. This is what you cannot do. But in general, people might see, you know what, it's an open source license doesn't matter is BST or MIT or GANU-GPL, GANU-GPL V2 or GANU-GPL, can you talk about the intricacies of these licenses where we do have to worry about the compliance, not worry about we should be as you said respectful, but we do need to understand the differences and why it matters. When we look at open source licenses, I think we go by the gold standard, which is the OSI definition. So the OSI has approved about, I would say anywhere between 75 to 80 different licenses to be quote-unquote approved OSI licenses, meaning these licenses respect the core freedoms of the software for using, sharing, distributing, customizing, et cetera, the software. So there are about, let's say 80 different, roughly 80 different licenses. And certainly they vary in their use in terms of what's required to be in compliance. So let me give a couple of examples. So a lot of people know the BST license or the MIT license, and they refer to them as permissible licenses because they're very liberal, meaning if you use MIT or BST as an example licensed code in a given product and you ship with the product, you have to include in order saying that this specific product, let's say it's a cell phone includes this component, that is licensed under the MIT license. Here is the license text. You include the license text, which is about maybe like five lines. You include the copyright notices and any attributions. And this is it. These are your requirements that you have to satisfy when you ship a product. Now we go to the other end of the spectrum. So when we move from, let's say, MIT to kind of all the way to the other side of the spectrum, you have, for instance, the GPL licenses or family of licenses. Let's use GPL v2 as a very popular, highly used deployed Linux kernel is licensed with a GPL v2. So under the GPL v2, let's say you have used the Linux kernel, which is already used on many of these portable devices. It's everywhere and a lot of people don't even know it. I mean, it may be in your car as well. So if a company uses and employs the Linux kernel, which is licensed under the GPL license, then in this instance, they need to provide a number of things that are considered needed for a company to meet its obligations for that license. These different things include providing a little notice saying to the end user that this product or the service includes software license under the GPL license and providing certainly the full license text, which is maybe like 10 pages for the full GPL license text, and then providing copyright information and providing something very important, which is any changes they have made to the code. So if you've taken a piece of code license under the GPL, you made changes to it, you need to make these changes available to the deceiver of that code. So how do companies do this? As you notice, and there are about 80 of these different licenses, and the requirements for compliance, they vary licensed by license. So how do companies actually manage this is by creating and implementing a license compliance program within their infrastructure. And what that entitles, or entails, I'm sorry, is automated tools that allow organizations to scan all the source code use, identify all the components used within the certain stack, identify the license for each of these components, and at that point, generating an S1 software bill of material. And then the company knows that, okay, for these different components, that license under BSD, here's what we need to do to be in compliance with the license. For other components, the license under Apache or Eclipse or GPL, and there are different variations of the license, for example, GPL v2, GPL v3, or AGPL, and others, and identifying these different components and their licenses. And then at that point, the company puts a plan, which is in most cases, mostly automated on how they can fulfill these obligations. So a lot of licenses today. And what's adding kind of complexity to the process is all these ad hoc licenses that are mushrooming here and there, where all these automated systems are not yet updated for such licenses. So you may scan a project license under some hacked up license. And it may go under you rather because the compliance tool you use did not have an updated license stack to be able to identify these licenses. So there is always need to have a person looking over what's going on on the automation side. But to go back to your question, you know, there are about 80 of these licenses, they differ by how a organization should respect them or should fulfill the obligations. And to be able to do this at large scale, where you have companies having thousands and tens of thousands of developers using hundreds and thousands of resource components, you cannot do that manually, you need to waste to scale. And scaling is one of the major issues that organization will have to address going forward. So now let's talk about the challenges when it comes to compliance.  It is, as you rightly said, manually impossible to get. Now, this may be a totally different topic. We started talking a lot about software bill of materials, you know, which is more or less like, you know, what's in your code based not to have an inventory. So can you also talk about when it comes to looking at software compliance, does software bill of material S bombs, those, these two things are different or they can help each other because, you know, we have to automate things, but we also have to find, I will of course talk about one of the ways, but I want to just quickly talk about S bombs versus open source compliance. Yeah, so I think they go in hand in hand. And I will kind of explain a little bit. But before I get into that in the past few years, there has been really enormous emphasis on S bombs and S bomb, as BOM stands for, you know, for the viewers who may encounter this word for the first time, software bill of material, which is basically a list of all the software components included in a given product or service with some metadata attached to each of these components that includes the component version, the license, the origin website or origin GitHub, et cetera. And the reason for this becoming so much in the news is that there has been a lot of emphasis across different policymakers in the US, there was an exact order that emphasis the need to have as well as from a cybersecurity perspective. So there has been different cyber attacks and there has been different vulnerabilities discovered in different pieces of code of software that gained a lot of attention. And there has been a lot of momentum going in securing the software supply chain. So when organizations shift and move code from one company to another up the stream or down the stream, we need to make sure that that software is secure and we're able to track any vulnerabilities and address them in a very time appropriate way. And this is why SBOM gained so much momentum. However, SBOM is from a compliance perspective has been known for since the early 2000s. We were generating SBOMs, but we were not calling them SBOMs. Okay, we were able to generate the list of all open source code included in any given product or service with the license information, version number, origin site, et cetera, and sending it to whoever is receiving the source code. And as recently as maybe five or six years ago, all software composition analysis tool provider SCA tools are these tools that help us compliance and security. So these tools were initially created and the focus of these tools was on ensuring license compliance because they scan the code, they tell you what's open source, they identify the license. And then these SCA tool vendors discovered that, hey, you know, we're doing most of the work already. So let's since we're scanning the code and find what open source code is available, we also have the vulnerability databases that are available publicly. And then we can create this dotted line between all the open source components we're scanning and identifying if there are any open security vulnerabilities out there. And if there are, we're going to flag it to the end user. And we're going to flag the priority, how important this vulnerability, and we're going to flag if there's a solution that is available, whether it's a patch or a new version of the software, and so on. So today we are in space where you're able to have a software composition tool that scans your code base, it tells you the origin and the license information of all the software components it discovers, plus it's able to flag to you any known security vulnerabilities. And when you generate that report, this is your S-Bomb. So today the S-Bomb is basically a combination of both license compliance information plus security vulnerability information. And the goal with that is to bring awareness to all the vendors across whom, whose supply chain these components are moving, that this is the lighting of this code plus, which is of higher importance kind of at least from a PR perspective, here are some security vulnerabilities that may exist or that exist with no solution that you must address and to prevent any kind of potential breakout or kind of headaches down the road. So today when you look at the, if you are operating in the U.S. and you want to do business with any federal entities in the U.S., you are required to be able to generate S-Bombs, otherwise you cannot do that business. But it is becoming much widely adopted than that, as most organizations are actually mandating the use of S-Bombs across their supply chain, which is really an extremely important practice because it encourages better license compliance and better security across the supply chain. What are the downsides or dangers or risks of writing code, using code without worrying about compliance? It can be challenging for big companies who may be but smaller companies. Can you talk about those aspects? I'm very glad to say that you are today in a space where it's very rare to come across an organization that thinks that it is okay and it's not important to ensure license compliance. In the beginning, if we go back 20 years, there were organizations that thought maybe license compliance is not enforceable. We can certainly use open source code. Nobody is going to come look on our door and challenge us on it and so on. The experience has showed us that definitely the open source community cares that organizations using the code actually respect the licenses and there will be voices at testing cases of miscompliance or non-compliance. From lessons learned from a lot of non-compliance cases, we can look at all these different case studies and know that at the end of the day, an organization can actually ignore ensuring compliance but eventually they all have to comply. Eventually, they all have to address and ensure they have license compliance programs. In some cases, there were some court orders to even hire a compliance engineer to oversee that and fix any previous product. In many cases, this causes a PR nightmare for the company because their vendors and their customers know that they're not or they don't have good compliance practices. All these lessons learned in the past, at least in the early 2000s, 2010, demonstrated to organizations that it is actually a bad practice to ignore license compliance, that you need to have a proper compliance not because there might be penalties or whistleblowers but it's because it is good for business. It will help you build great relationship with the open source community that is creating these different components available to you and it will also give you better visibility into your own software stack and understanding of the importance of open source code within your platform. When organizations, and I was part of these different companies, I was at HP, I was at Motorola at Samsung at Ericsson and many other places, Motorola and others, where our license compliance practices actually educated us on where we rely mostly on open source, where we have our value at and how we can actually create better leverage and better use of open source code in our platform and services. Although compliance today is mostly what people think of compliance, they think of it as an overhead, as an exercise they need to do to make sure they respect the licenses but certainly experience open source professionals look at compliance also from an architectural perspective and from value perspective. Let's figure out where we're focusing on open source and where are our jewels and let's protect the jewels and kind of make them bigger and larger and enable that through the use of open source. I don't think we are in a place in time where organizations think it's okay not to be in compliance. I think there is a very deeply understood concept and lesson there that all organizations using open source will comply with the licenses and I think very mature organizations with open source use compliance or license compliance practices as a way to discover their dependency on open source and increase the use to maximize their value at where it is. One more thing I want to talk about is that of course this is a big elephant in the room which is arrival of Genitive AI and of course there are some lawsuits going on where news publications are swing some of these companies who are using Genitive AI and Genitive AI companies are also like hey don't take our copyrighted code base so it's becoming a bit complicated space. What does Genitive AI mean for open source license compliance and what does this compliance mean for Genitive AI? I want to look at it from both perspectives. Yeah thank you for the question. Actually this is a very interesting story so at the end of towards the end of last year I was talking with a friend of mine and he was telling me you know Ibrahim you know what are your thoughts about compliance going forward and I told him well you know I think we're in a very good place and kind of compliance is kind of boring today because we know the the landscape and we know how to address it and then two months later Genitive AI is like the big thing and it threw at us a whole bucket of new challenges. So very interesting space we we're operating in with respect to Genitive AI where as a developer we can go to any given AI system prompt and tell the system you know I want you to generate a function that does x y and z and within like you know two seconds you have 300 lines of code that you can grab they're functioning and they actually meet the needs of that you want. So from a developer productivity if you wish this is just an incredible piece of tool that is available to everyone mostly you know junior engineers certainly senior engineers can use it but I think the the the most multiplier of output is coming from the use of junior and you know intermediate engineer and it's really something incredible and I wish I've had that when I was an engineer you know 25 years ago plus when I was writing code. So with that type of benefits and that immediate access to incredible knowledge that is being generated in front of you comes certain risks and you know one of them is the fact that all these different systems were trained on publicly available source code and in some cases depending on your prompt into the system you may actually get pretty much an existing piece of code and what's really interesting and I'll explain a little bit for our viewers who may not be experienced in this. You know I went to a couple of the projects that you host in in my umbrella foundation LFA and data you know very new projects they're in sandbox incubation levels so they're very new projects and I went into their GitHub account I went down the repo for a few levels and I came to a you know a function file I opened it and I copied I looked at it and then you know it's maybe about you know 70 80 lines function you know a function of that was just maybe 70 to 80 lines of code and the engineer who wrote that actually had a description of the function and I said you know I want to test this so I went back to the AI system and I said can you please write me a function that does the following and I copy pasted the function description from the code in GitHub into the prompt system and within one second I got the same piece of code exactly at 100 percent okay so this is a very unique situation where if you're able to provide a very precise prompt similar or equal to maybe a function description somewhere you're going to get the same code because all these models were trained on these systems so it's not generating right it's not creating a new code it might be copy pasting that code and providing it to you and this is kind of a very unique use case where that model or that system is giving you that piece of code but it's not telling you that this came from project x on github and is licensed under the given license so this is kind of the risk and how do companies are dealing with this really depends on the companies there are different approaches to this one of the approach is focused on the use of SCA tooling that are capable of identifying snippets of code so when you generate piece of code using generative AI systems you can actually scan them using these SCA tools and the SCA tool will tell you the origin and the license and you're able to address that challenge right there other companies are either using a combination of tools and policies or some companies are focused on policies only and there are multiple policies that companies can choose from they can be very restrictive policies where a company can decide you know I don't want my engineers to use any generative AI tooling to generate code at this point so basically the policies do not use such tools at this point this is very restrictive now on the other more liberal aspect you can leave it up to the engineers and enforce some compliance at the tooling level or you can be in the middle from a policy perspective as an organization and say we allow the use of generative AI in specific context meaning you can allow it for the use of for generating code for use cases for testing purposes but not production or you can allow it for any type of use case as long as engineers use a specific system or specific tool to do that for example and then this is not an endorsement or publicity but for example let's say GitHub co-pilot or system x or system y you know organization can opt you know we trust the system let's use that system or this tool versus that tool so there are really a variety of approaches at the policy level from very restrictive no we don't use these tools yet until we have a better understanding of the legal landscape and what's going on in that space you can be very liberal and tell your developers go use whatever you want or you can be very in the middle where you allow the use depending on the use case or allow the use depending on the tools and certainly as a bottom layer to all of that it is certainly a good idea to run all the code generated through license compliance tooling because by purpose and by nature these tools work to tell you the source and the license of the code they identify so this will help tremendous and let's not forget there's always that risk has always existed in open source meaning a developer knowing you or unknowing the contributing piece of code that shouldn't contribute to an open source program right and that's why we have DCOs in place and CLA's in place to be able to capture these however now with the use of generative AI these risks are happening at a much larger scale you know hundreds of thousands of developers but the same way that we're able to manage compliance the same way we've came up with tools and methods and policies and processes for the past 20 years to manage license compliance now we're looking at a new challenge with generative AI and we need to update our internal use of policies and update our policies to reflect this new development and accommodate for it so I don't think it's the end of the word I mean there are some in some cases a lot of voices calling you know this is dangerous and this puts you know at risk open source and you know I think it's just new development similar to anything else we experienced you know technology goes in cycle in cycles and we are at a point where we're facing new challenges this is one of them and certainly I think in a couple years we would have addressed it and like also and we would be looking at new challenges anything else that you feel like here so this is really important for this discussion and I feel to us that are you think that we hit on some major points today yeah thank you so I think as a rep the Linux foundation has a lot of research which is kind of a business unit dedicated to producing really top-of-the-line and very timely report across all technology sectors and topics and I think at the beginning of this year we just celebrated 50 reports in the past three years which is really incredible so I would urge people and invite them to visit our website at the next foundation and have access to all these really amazing reports produced by LF research with collaborations our members and a lot of all these reports are available publicly and all the infographics all the graphics all the images figures are also available for use to encourage use of these survey results and others and similarly there are within the next foundation there are many efforts going in support of license compliance whether directly or indirectly so for example stdx is one of them we have the open chain effort which is also pours into that direction we also have the effort of the to-do group which is the collection of ospo offices across our membership that collaborate together for better open source practices plus a number of publications and also equally important free training that organizations or individuals they can go and get free for example free open source license compliance trainings for developers and a number of other publications and best practices so we are working very diligently to produce a number of knowledge pieces whether it's videos training publications and make them available for people and individuals to increase the knowledge in that domain and help them be better at using and continuing to open source so everyone listening to this report you know please consider visiting the website and accessing all these resources available at your fingerprints ibrahim thank you so much for taking time out today talk about this report great insight there and as usual i would love to chat with you again soon thank you thank you very much for you i appreciate it


Selene Dion. Beautiful, talented, successful, and yet still human and fragile. Porcelain.  The past year has provided a remarkable smorgasbord of reminders of just how badly things can go wrong and how much risk each of us faces on the daily basis. We don't really like to talk about that constant peril. Facing your own mortality is rarely a recipe for a good time, but it can sometimes be an important bit of context for how we think about certain topics. This is the starting point from which legal philosopher Martha Feynman develops a model that she calls vulnerability theory, a fresh way of thinking about risk, disaster, and the role of law in people's lives. In the context of the theory, the term vulnerability isn't a special, temporary fragility that certain people have in certain contexts. It's a universal, immutable future of what it means to be human. A constant condition that we all experience our entire lives because we're all delicate creatures of flesh and blood. You, me, everyone shares a common set of permanent vulnerabilities that can be threatened or compromised by various hazards, many of which are totally beyond our ability to predict or control. A drunk driver, a freak storm, a careless neighbor.  According to the theory, the differences we see in outcomes aren't due to differing potential for harm. We all have exactly the same physical capacity for injury, disability, and death. Rather, we see different outcomes because we all have different resources available to recover from the impact of a hazard. Resources that might be physical, social, ecological, all sorts of things. Take COVID infection. No human is 100% safe from COVID, but a given human might have a robust immune system that can fight off the disease, education about how to recover quickly, a family member willing to look after them while they're sick, proximity to a hospital in case anything goes seriously wrong, or even something as simple as a good book to read while they're languishing in bed. All these resources can grant resilience, the ability to bounce back from something harmful, like a COVID infection. Everyone is vulnerable, but folks who can call on various forms of support can recover quicker and easier. Interestingly, there's an implied complexity to this idea of vulnerability and resources for resilience that isn't captured by things like simple risk analysis. As we saw in episode 208, one small failure often impacts multiple systems at the same time, including systems of recovery, causing cascades of disaster. The record cold snap Texas recently suffered didn't just make it impossible to survive without a ready source of heat. It also shut down the electrical grid, which caused pipes to freeze and burst in some buildings, making them uninhabitable. The Texan might have found themselves suddenly powerless, homeless, and freezing to death, all because of the same hazard. We can see that chain of cause and effect easily in retrospect, but a naive analysis of how likely a blizzard would be to hurt people might well miss those second-order effects of lost resilience.  Speaking of Texas, for Feynman, the ultimate goal of regal institutions is to address the vulnerability of their constituents, to use their power and resources to shore up people and organizations so they can recover quickly from peril. This puts the role and maintenance of government on the same outcomes-oriented continuum as its citizens. Just as with people, legal institutions have some inherent, indelible potential for suffering permanent injury, regardless of the specifics of their situation. Loss of faith, disruption, capture, and dissolution threaten these institutions and their ability to provide resilience to their citizens. In this sense, the primary measure of a government's health isn't necessarily its ability to prevent disaster, although that's certainly appreciated, it's the ability to enable each citizen with the tools and resources they need to recover from that disaster. If it can't, it's a cry for help. Interestingly, this framing also flips our normal conception of how law is supposed to work on its head. Our current system assumes a static legal subject who is independent and autonomous.  If someone is, for whatever reason, not able to call shots or make deals due to circumstances beyond their control, we try to identify whatever is special or deviant about them. What category or identity might explain why they can't be the shot calling deal-making walkie and they were born to be, then try to build some legal framework around them to apply an equal and opposite force to restore them to this theoretical independent autonomous standard. Feynman asserts that this approach has been historically insufficient from the perspective of vulnerability, as numerous institutions continue to produce and exacerbate the advantages of certain groups over others, generating new and creative ways to circumvent explicit legal restrictions on discrimination, while supplying even more protections to individuals who are already in an exceptionally resilient position while others suffer harm. She also notes that the vulnerable group approach is constantly embarrassed by its over-generalization of group members, as though Donald Trump and Joe Biden are in desperate need of the same special legal protections against age discrimination as any other random person over the age of 65. Under vulnerability theory, the goal of law is to maximize the resilience of a population against hazards. It can't do that unless it acknowledges their existing resources, where they're weak against trauma and where they aren't. By focusing on addressing vulnerability and resilience directly, not only do we get away from the awkward over-generalizations of protected groups, we can address people's needs as they change over the course of their lives without trying to constantly normalize them against some locky and ideal of independence. My independence has fluctuated wildly over the course of my life, and will continue to change drastically as I get older. My vulnerability on the other hand, my physical instantiation as a human being who needs certain things to keep living, that hasn't gone anywhere. Everyone needs help to bounce back from threats to their fragile existence. Some of us need more help than others. Maybe our institutions should focus more on that aspect of what it means to be human. But what do you think? Does Feynman's notion of universal human vulnerability seem like a good framework for thinking about things like law and society? Can you think of an interesting application of vulnerability theory? Please, leave a comment below and let me know what you think. Thank you very much for watching.


Hi everyone, it is Crypto Grounds here and welcome back to another tutorial. In this tutorial I'm going to be briefly going over texture atlases or sprite sheets as another name for them. I will be showing you all how to use them in text mesh pro. Additionally, I will be showing you how to automatically import them into your game as a sprite array, which can be done in code. So here's an example of a sprite sheet I will be using for this video. These are all of my completed achievements that I am using for the idle research achievement system and I also have another one that looks just like this. So here is our very basic file structure. You have a resources folder and inside of that is a subfolder and the completed tube achievements, which is just a PNG and inside of the subfolder is another PNG and that's going to be called the completed Flask achievements. So we have two different ones and I will be showing you how to import both of these into a sprite array. So let's start with that first. In order to import these as sprite arrays we need to mess with them settings real quick. So let's head to our completed Flask achievements and in the inspector you should see all of these settings. So head down to sprite mode and click single and change it to multiple and then hit apply. After you hit apply click on sprite editor and this window should pull up. Hit the slice button and hit type and make sheet change the automatic to grid by cell size and you should type in the pixel size based on whatever square size everything is. If we were to do automatic it wouldn't really work properly. So you just it's just one giant box around this entire thing. So we have to type in a grid size manually. So in our case it's just 250 by 250 because all of these are 250 by 250 squares hit the slice button and everything should be great. So you can click on each individual box. And now you have a little mini sprite for each one of these little boxes. So when you're done with that hit apply and if we were to go back to our resources folder in the assets and you hit that drop down right next to it. You can see you have all of the all of the sprites for each individual ones. And it looks like some of them are bit off like this one's a little funky. I think that's just the picture I messed up something. But anyways, if you were to check them all out everything should look great. You'll be doing this for any picture you have that looks somewhat like mine. I have another one. So I'm going to do that real quick. And sometimes you may have extra boxes that you don't need. Now you can just hit delete. I'm going to create two things one a canvas. So UI canvas and then I'm going to create an image. OK, next I'm going to create an empty game object and just throw that outside of the canvas just whatever I'm just going to call this. I'm going to call this this will be where our script is going to go. So just name it whatever you want. So I called mine sprite sheet manager, but yours may be different for your purpose and open that up. All right. So now we need to create two sprite arrays because I have two pictures and you can do that however you'd like. You may have more than one. You may only have one sprite sheet, but that's up to you. All right. So first I want to load in this completed flask achievement sprite sheet. So just a note, this is inside of a sub folder. I can easily move this out and just keep it like this. But I want to show an example of how to load how to load in a sprite if it's within a folder. All right. So in our start method, we want to load in these sprites and we only want to do it once and that is in the start method. So that is just right before everything happens. We could put it in our wake method, but I'm just going to put it in the start method for simplistic purposes. So we want to assign our sprite array, our completed flask achievement sprites equal to resources that load all and make sure you include the care so you can determine what type of asset we are importing in our case, it's sprite. And then we're going to put the directory inside of these parentheses. And for the flask one, it is inside of the sub folder. So we got to include that. So it's sub folder folder slash completed flask achievements. And that's all we need to do for this. So resources is a class that includes a method called load all. And this will load every single sprite within this completed flask achievements. So it's not going to load in this big guy. It's going to load in every single one of these little sprites into a sprite array. So we're going to do the same thing for our completed two achievements. And this one will be more simple because it's not inside of another folder. So in my case, it looks just like this. So let's save it and let's give it a run. And as you can see in our specter, we have all of our sprites in here. So there's no need for us to drag these manually one by one over and over again. It just does this automatically and it's very wonderful. And it happens once so we don't need to constantly import our sprites, that would be a little silly. And then they're there and done. So now let's grab a random sprite and try to sign it to this picture right here. So in our script, we're going to create an image object. Make sure it's within the unity engine dot UI namespace. And we'll just call this sample achievement. I don't know, just just because I'm going to put this in the update method. I'm going to create another variable, which is going to be an end. And we'll just call this ID. So we're going to be we're going to be able to change this within the editor so we can see whatever achievement we want. So we're going to set the sprite of our image equal to completed flask achievement sprites at index ID. So by default, it's going to show the very first icon because ID will be set to zero. But we're going to adjust that within our inspector. So let's unpause this, let it load in and then hit play. So yeah, no reference. Don't forget to assign your image because that's that's not good. All right, so as you can see, this is the very first image in our completed flask achievements. And let's just move this ID around and it should change. Oh, yeah, it's going crazy. And don't go out of bounds because then you'll get this index out of range exception, but yeah, so you can change this ID and cycling through all of the different sprites within the sprite sheet. Cool. So now you know how to import tons of sprites within just a few lines of code. Now let's find another way to use these because these can be very powerful. So in your project, if you haven't already imported text mesh pro, I would highly recommend you do that. I would not suggest using the default text here because it's very outdated, it's not good. I've had issues with higher resolutions such as like 4k or even 1440p. Text would just not render pop properly. I would highly recommend you not to use the legacy text anymore. Otherwise, we're just going to import all of our essential resources for text mesh pro and which can be found in the window text mesh pro and then the import button. And you want to make sure you import all of these if you haven't already. All right, so we're going to be using something called a text mesh pro sprite sheet. So so what we're going to be doing with this is taking the sprite sheet here and making it accessible for text. So if you have a bunch of icons you want to access through your game within a text like currencies and stuff like that, you'll be able to use this with text mesh pro, unlike the legacy text. So first thing, let's create a text within text mesh pro and just give it some random text and stuff. OK, so we're going to be creating our sprite assets for text mesh pro. Also, I've probably been calling these sprite sheets, but so we have sprite sheet or texture atlases, which is what this guy is. And then we have a sprite asset, which will be used for our text mesh pro. So we so we are creating a text mesh pro sprite asset right now. So do that. You need to right click on a picture that is on multiple sprite mode.  So automatically create one and you can see the character table and all that. And you'll be able to adjust all these funny numbers. So and you're going to do that in order to position your sprites correctly. But anyways, we have created this sprite asset. Let's do the same thing for the other achievements. In order to use these, we need to go to our text and use the sprite tag. So it looks something like sprite equals. And then we have our quotes and we'll put our name in here. And then index equals whatever we want. So we want the access. The first achievement will use index equals zero. And it's the same thing as the ID system we have here. But this is not going to work even if we type in the name of this actual sprite asset, see, it would just look like this. So this is no bueno. It's because these sprite assets are not in the correct location. What we need to do is create a folder inside resources called sprite assets. So let's do that. And then you need to move both of these there. Hit save and you might need to refresh it a bit and it should eventually show up. Oh, it never moved. Silly me. There we go. All right, so just try to remain them and oh, there we go. So now it should look like this, which is kind of not looking good. So what we need to do now is move these. Oh, and it looks like I moved the actual sprites instead. My bad. Anyways, what we need to do is go to our sprite asset and adjust our global offsets and scale so you can just mess with this number. Generally, the X position is just fine. You can set that to zero, but the Y you're going to need to mess with. So yeah, you just move it up and down. Find a good position, which I think like 200 is good here.  You can change the index. I want one, ten, sixteen, twenty nine, forty five. You know, you can change the index and you'll get a different sprite. And it looks like that, which is cool. But let's do this in code now. So let's create a text public TMP text and make sure you import the TMPro namespace and we'll just call this the sample text. And inside an update, we're going to set the text equal to achievements. And then we need to do the same sprite tag. And to get the quotation marks, you need to put backslash then the quote like that and make sure you set the equal. And then you want the name of the sprite asset and then index. We're going to set it to ID. So what I just did here is called string interpolation, which is where we put the curly braces around a variable inside of our text. However, in order to get to work, we need to add a dollar sign at the beginning of the string. So now so now our text should change based on whatever our ID is. So let's go take a look and we need to assign our text to our script. All right, so something's wrong. What's so we forgot the final threat, the care at the end. So if something looks like this, then you most likely did something wrong. Either the name is wrong, the index is off or your sprite are in the right location. OK, cool. So let's change this ID. And as you can see, both of these are now changing. This looks kind of funny, but that is pretty much it. I use Sprite assets all the time in idle research. If you haven't checked out my game, make sure you do that. It's on Steam and you'll probably see similar text with like an energy icon or flash just on the text. And yeah, it's it's definitely a lifesaver. It makes your game look much better. And yeah, I love TechSmash Pro and Sprite assets. But anyways, that is all I'm going to be showing you all for this video. I think these two skills are very crucial. And that is all you need to know to do a lot with Sprite assets. Obviously, you can do probably much more than this, but I hope it was helpful. And if you learned something new and if it was helpful, leave a like, subscribe to my channel if you are new around here and turn on the bell if you want to be notified for whenever I upload and hit the thanks button if you want to support my channel. One final note, it's been a very long time since I've like sat down at my desk and recorded a video and for previous subscribers who used to watch my videos, I'm probably in a different location as you may notice, but I just want to say thank you for waiting. Thank you for being patient. It's finally summer break. I am out of freshman year and I'm doing my best to make videos. So I think the plan is record a video one day, edit the video the next day, and then switch off so I don't get burnt out. And believe it or not, I feel like I forgot how to talk because I like stutter, merge words and all that. So if some of y'all noticed that throughout the video, that's pretty much it. So I'm very sorry about that. I'm doing my absolute best to talk like a normal human being.  And thank you very much for watching. See you later. Peace. I'll show you magic. We born in different.


Live from Barcelona, Spain, it's theCUBE, covering KubeCon CloudNativeCon Europe 2019. Brought to you by Red Hat, the CloudNative Computing Foundation and ecosystem partners. Welcome back to the FIRA here in Barcelona, Spain. This is theCUBE's coverage of KubeCon CloudNativeCon 2019. I'm Stu Miniman, my co-host for two days of coverage is Corey Quinn, and we're excited to have on the program a first-time guest, but a company that we've known for quite a while, Daniel Lopez-Ridrejo, who's the CEO and co-founder of Bitnami. Just announced recently that Bitnami is being acquired by VMware. Daniel, thanks so much for joining us, and congratulations to you and the team on the exit, as it were. Thank you very much, gracias. It's an honor to be here.  Back then, I was trying to figure out exactly what Bitnami was and where it fit in this whole world. Maybe you can just bring us up to speed for those that maybe don't know, and there's all these people in the enterprise space that might not know your community that the dev space knows real well, as to bring us back the who and the why of Bitnami. Yeah, Erika is my co-founder, and we have been building this together over the year. It has been quite a fair ride, and we started Bitnami as an offshoot for a previous company called BitRock, in which we made software easy to install, and then we realized that a lot of what people wanted to make easy to install on Linux was open-source software. So we started working with companies like MySQL and Suga CRAM, Splunk really early on, where there were only like four or five people, and over time, we decided to do the same thing as an open-source project for all those other tools and projects that didn't have a way to make them easy to install. We started as Bitnami.org, we wanted to emphasize that it was an open-source project we're never going to be a company, and it didn't turn out to be that way. All right, so we got a lot of things to cover, but help us connect the dots as to those early, dot org, it wasn't a company, to a company having the dev space too, was starting down the path towards the enterprise, which seemed to be a natural fit as to what happened today. Yeah, so going back to your real question of why we wanted to make, we've always been driven, there is all these marvelous open-source software out there that is super difficult to use for a great majority of people and we just wanted to lower the barrier to make it easy to use, and that's what got it to start, that we never expected the success, it turns out that we went from a hundred to a thousand to 10,000 to hundreds of thousands of downloads, and we're super popular with developers, we have literally millions of developers using Bitnami, and as part of that evolution, we started working with the cloud providers. We drive a significant percentage of usage for Amazon, for Google, for Microsoft, that's what makes it valuable to those cloud vendors, and as the next stage of the company, we wanted to go directly to the enterprises in which we already have a lot of developers in those same enterprises, but when you go and move to production, you know there's a lot of red tape, a lot of gates that you have to go about, compliance and security, and that's what we're taking the company into. Yeah, nine, 10 years ago, I stumbled over your company or project at that time, and it was the second best way I ever found to run WordPress. The first, of course, is don't run WordPress. I'm very serious, don't run WordPress, and I'm curious now with the acquisition of Bitnami, what is the longer-term vision for how this fits into a more cloud-native landscape? Is it continuing to just be the, not just, but is it continuing to be the application that you get from a catalog and it's up and running? Is there a containerized story? Is there something else I'm not seeing? No, that's the core of Bitnami, and that we will continue to do that. What has evolved over time is initially you could download and install it and run it on your Mac, and then we were one of the first early adopters of AWS, so we created all the same eyes, and when people were thinking that we're crazy that Amazon was a company that sold books, but what were we doing? We kind of saw that where it was going early on, and then as Kubernetes came along, we were really, really early there as well, and we were one of the early partners of days around Helm. We provide a lot of the Helm charts right now. We may have double a little bit on serverless, so whatever comes next, we will be there, and Orgo will continue to be the same team, which is to make awesome software available to everyone. So, in definitely of the underlying platform, that's what we are focusing. So, the core mission is not changing. We're just augmenting that and going after the enterprise, more Red Hat Enterprise Linux, more Open Shift, more multi-tier, high availability, more production features. All right, so you talk about all those pieces. You talk about Linux and everything there, and while I want you to help connect, how does that tie into VMware and what you see them doing today, because sure, Linux has been something that could live on the hypervisor for a long time, but in many ways there's been struggles in competition between VMware and the Linux community in the past, but starting to see some of that change and maybe this helps accelerate some of that. Yeah, I think there is a couple of companies, Microsoft and VMware, that were completely different from other companies than five years ago, and probably decision will have been different for us, like five years ago versus what the company is today and where they're going. For us, VMware is, the holy grail of acquisition is two plus two equals five, and that's hardly the, there's a lot of acquisitions that don't go that way. For us, it was a very thought out decision, and it was, I think it was clear for us in the sense that we have a very big footprint with developers, their own enterprise IT. We wanted to go to the enterprise, they wanted to go into developers, they understand open source, understand distributed teams, yeah. Yeah, maybe, I'd love to hear your insight as to that developer community, because when I walk around the show floor, you know, there was that struggle between the enterprise and the developers, and now, you know, the storage world, you know, we need to get, you know, CICD and all these things, and they're like, we don't know how to get there. And over the last few years, it seems there's been a blurring of the lines, and more enterprises embracing it, you know, open source is a big piece of that, so is it just, as you said, five years ago this wouldn't have happened, but you know, now it feels like we're ready for that next step of the curve. Correct, and all of that is because of the standardization that Kubernetes is allowing. You can standardize best practices, and you're seeing a consolidation, the CICD, you know, wall, and it's just like, things that used to be very exotic now is, you know, business as usual, and it's a parallel, you know, I started using Linux in 93, when there was not even the concept of a Linux distribution, you have to do all these things to just get a prompt.  I think something similar is going to happen, we just meet way there, in which you will not have KubeCon because, you know, Kubernetes will be something transparent that is boring. So, we're not there yet, but at some point Kubernetes will be boring, and there will be layers on top of that where all the action is, or will be. With, from my perspective, coming from a small startup background, it seemed to me that VMware was always one of those stodgy, boring companies I didn't have much time for. And lately there have been a series of high-profile acquisitions, Heptio, Wavefront, Cloudfront, and now Bit and AMI. And it's really changing almost without me noticing my entire perception of their place in the modern evolving cloud ecosystem. I think so, and that's one of the things that attracted us.  For us it was very important. And again, one thing that we haven't mentioned, and we have been for the most part, we have been bootstrapped, you know, we have been profitable. We only took a little money from White Combinator when we were already profitable. So we have choices. Sometimes our BC funded peers don't have that choice. So it was a very meditative decision. And for me, for this kind of acquisitions with a much bigger company, you know, joins forces with a smaller company, the strategies need to be aligned. And to me, VMware realized that the wall is, you know, a few years ago, that the wall is going to be multi-cloud. The wall is going to go towards Kubernetes and containers. And the acquisition of Heptio, the acquisition of Cloud Health, told us that they're serious about that. And that we can, you know, fit right in and take advantage of that transformation that they're going at. And so far, it's working really, really, really well. And that's part of what made us decide to go in this direction. Yeah, Daniel, what can you tell us about what things, once this actually does close, what will that mean for the brand?  You know, how does all of that line up? So with Heptio and other units, like the marketplace, other groups, we are, we're already working with them before the acquisition. With Heptio with case on it and a bunch of other initiatives. And we're just going to double down on that. And they want to keep Bitnami. They want to keep the brand. They want to keep the team. If anything, we're going to get more resources.  They just, you know, we have been partners for, I think, seven or eight years. We have gotten to know each other over that time and build that trust that is needed. And, you know, it's, in a way, nothing is going to change. Is we're going to, the same team, doing the same things. We're just going to have more access to their, you know, user base, which is what we're going to do. Like we started down this path because we were, you know, raising money to build an enterprise sales force. And at some point we decided, okay, this doesn't make sense. We're going to go, you know, give away all this chunk of the company. To get access to the enterprise or to build a sales force to get access to the enterprise when, you know, we can be part of VMware and, you know, get that for free. You mentioned a fair bit about what's going to change as far as you getting exposure to new customers, effectively broadening into additional markets. What does this mean for your existing customers who are, in some cases, whenever you're in a customer of a small-ish company and there's an acquisition, it sometimes is now to be a little concerned do I need to find a new vendor? Do I need to find a new provider?  No, that's a really good question. For us, what is a little bit unique is we have millions of users, but we only have a handful of customers. So our customers, AWS, Google, Microsoft, Oracle. So it was very important. VMware is already a vendor to all of this. And so far, you know, everybody's going to stay and we're going to continue and deepen the relationship. And it does one of the things that made this attractive. So for customers, nothing is going to change and we're just going to continue to deeper, deepen those relationships. And that, again, that was important. Have we gone through some of the other options? There will be a lot of very awkward conversations to have and that's not the case. Yeah, Daniel, how about the developer community itself? As you said, millions of downloads out there. We understand how some of the reaction could be. It's being where it's going to be. The evil company is going to touch that. And I think so far, the feedback has been extremely positive, including even Hacker News, right? And those people don't like anything. I mean, I've been Hacker News since the very beginning and it's going to be hard. So it's something that was monitoring how people, and so far it's been very, very positive. And that's only not a testament how much people like Bnami, but also, again, like being where a choir helped you and everything's great. Like we talked to a lot of the people that helped you. Hey, how are things going? How has it been, right? And I really loved it there. So for us, it was a very, something that gave us a lot of reassurance that all these other open source companies with a lot of open source DNA were being successful there and gave us reassurance. Time will tell. We'll see you one year from now where we are. But so far, I've talked to, all the conversation has been great. So Daniel, you have a very interesting viewpoint on this whole ecosystem. We work with all the cloud providers. Any commentary you'd give of kind of, you talked about kind of midway point of the maturity. Where do you see things today? Where do you see them going? What do we need to fix as an industry? It's very difficult to predict where things are going. I just think that at this point, it's very safe to say that it's going to be a multicloud wall. That was not like three, four years ago. It seemed that it could be like a repeat of the 90s in which Microsoft owned 90, something percent of the market share. And there's a lot of things that didn't make sense. Right now, at least Amazon plus a bunch of other clouds are very viable and if anything, they are growing. So a lot of companies like HashiCorp, like VMware, companies that support this multicloud environment, not all of them, but all of them are very well positioned to try because it's not going to change anytime soon. The other thing that I think is safely to assume is we're going to have more artifacts than ever. So companies like, Artifactory, I think they will do well as any companies have to do with security. We're going to have more security issues, not less, but that's in the long term as much as I can predict. All right, well, Daniel, thank you so much. Congratulations again. We look forward to seeing you at VMworld, where we'll have theCUBE. There'll actually be our 10th year doing this at VMworld, so we're excited and always happy to talk to us, especially the startups having some great news here. For Corey Quinn, I'm Stu Miniman. Thanks as always for watching theCUBE.