I know how engineers get excited about standards compliance, and I'm worried about how they'll respond to this script. It's making me kind of antsy. After years of drought, New Year's Eve brought a record-breaking downpour to the San Francisco area. The city was immersed in 140 millimeters of water in a single day, resulting not just in the flooding of homes and businesses, but cascading failures of other important civic systems. Transit, highway and road closures, electrical grid faults, emergency shelters packed to capacity with evacuees. It wasn't exactly Katrina, but it wasn't pretty. Catastrophes draw our attention to the many interlocking, complicated, and sometimes fragile technologies that make it possible for us to have a normal day. The San Francisco sewer system is, happily, out of sight and out of mind for most of the city's residents most of the time. But watching coursing rivers of rainwater pooling into streets, we start to wonder about things like, how big are those underground pipes? What sort of downpour is the wastewater system designed to handle? What other systems are built assuming it's continued operation, and do they have contingency plans for when those pipes get overloaded? The word infrastructure is a good catch-all term for these sorts of essential civic services, but its definition isn't extraordinarily precise. Infrastructure is the basic physical and organizational structures and facilities needed for the operation of a society or enterprise. Yes, that describes sewers, roads, and power plants as you'd expect. But considered more broadly, there are other things that fit that definition that you might not think of off the top of your head. Like there are radio waves that are essential to the operation of San Francisco. A solar flare that briefly interrupted cellular service would result in a fair amount of chaos and a breakdown of other facilities, as many essential repair and maintenance technicians are dispatched via cell phone. Examples and algorithms, like air traffic control procedures, can cause incredible damage and disorder if they break down. Even something as simple as the cultural preference for driving on one side of the road versus the other is, technically speaking, an organizational structure necessary for the continued operation of society. None of this is to say that the dictionary definition requires us to pedantically include these things when we're talking about infrastructure, but in the context of a disaster or catastrophe where we're forced to take a hard look at all the stuff that has to keep working for society to keep working, it can be helpful to conceive of infrastructure more broadly than is the power still on. Standards and testing form an important part of that extended infrastructure, the maintenance schedule of your sewer system, the chemical treatment specification for your tap water, and the legally mandated width of your roads are just as necessary as the physical structures themselves. Some of those standards are set by government bodies, some are set by professional organizations, some are set by standards agencies, organizations that are dedicated to creating rules to provide a common technical basis for various global industries. The International Organization for Standardization, or ISO, the letters are iOS, they're ISO, don't worry about it, it's very silly, is the international authority that defines the official protocols and specifications for an incredible diversity of stuff, from JPEG compression, ISO 18181, to freight shipping containers, ISO 668, to paper sizes, ISO 216, and tens of thousands of other indispensable technologies at every level of your society. ISO crafts these standards to ensure that wherever you are in the world, any new implementations of that tech satisfy certain requirements, things like safety, functionality, and reliability, that are compatible with other existing tech, so your multi-million dollar public works, work with your other works. But ISO is a private organization, non-profit, but private, they charge fees for access to the vast majority of their standards, sometimes up to thousands of dollars, and many previously free standards have been locked behind their store's paywall. Nations that don't want to or can't afford to pay ISO membership fees are no less subject to those rules, at least if they want to sell their goods to nations that require standards compliance, which means their economy, their industry, and their future is kind of at the mercy of whoever's writing them. ISO's membership manual explicitly states, if you are not a full and active member of ISO, you are letting others decide how standards are set and under what conditions your country participates in international trade. The paywall model also causes problems for businesses. Many laws require companies and their products to conform to ISO standards, but do not supply access to those standards. This can lead to the bizarre situation where your company might be violating the law, but you can't be totally sure unless you pay ISO to see what legal requirements you might not be satisfying. Of course, these documents can be incredibly useful for coordinating industries, and take a great deal of time and effort to produce and validate. One might argue that requiring people to pay for access helps to support the efforts of standardization, to get even more of the world on the same page. There are three problems with this argument. First, although some of the money goes towards keeping ISO running and paying their staff, the technical experts who actually write the standards do so on an unpaid volunteer basis. Someone might spend years exhaustively researching and thinking through all the necessary specifications for their field of expertise for the good of all, only to turn around and have to hand ISO a few hundred bucks for a licensed copy of the completed version. A number of previous contributors to ISO's library have started a petition to remove the paywall, asserting that it's in both the public's and the organization's best interests to dispense with the paid model. Second, many standards, even the legally mandatory kind, are of questionable value. ISO 9000 is by far the organization's number one seller, a set of management techniques ostensibly designed to ensure and improve quality. ISO 9000's certification is a long and expensive process that has to be re-upped every three years by an approved accreditation consultancy. But if you want to participate in certain EU trade agreements, it's requisite. So what's in this very expensive document that's so important that millions of companies worldwide pay for both the standard and regular audits? Documentation of, and adherence to, a decision making process. If you think that sounds underwhelming, you're in good company. Many critics have accused ISO 9000 of being a sort of cool kids club for companies that can afford it rather than a meaningful mechanism for industry coordination or quality assurance. There's no compelling evidence that adhering to the standard has any appreciable effect on a company's performance or the quality of its products, but the roster of certified companies grows every year. What choice do they have if they want to do business? Third, because ISO standards are written by people, there are certain inevitable cultural, political, and societal values that are bound up in their authorship, and because they get embedded in infrastructure all over the world, sometimes those values can be reproduced in harmful ways, on a scale that can hamper, undermine, or even rot entire societies. In Confessions of a Recovering Engineer, civil engineer Chuck Morone notes how the specifications for road construction in the U.S., a set of metrics and guidelines ostensibly justified on grounds of safety, actually result in a great deal of unnecessary danger for Americans who have to use those roads. The standards implicitly prioritize the safe speed that vehicles can travel and mandate certain features on roads to maximize that value, large shoulders, wide lanes, unobtrusive pedestrian crossings, time traffic lights, and so on. That sounds reasonable, Ray. The committee that originally composed the standards wanted drivers to get where they're going quickly and safely, and built their civil engineering Bible around that principle. Who could argue with that? But if you start to interrogate those requirements and what they actually do, they start to look less like a virtuous mandate and more like a set of expensive trade-offs. High vehicle speeds are considerably less safe for pedestrians and cyclists who have to share those roads with drivers. Prioritizing unobstructed flow of automotive traffic makes walking or cycling very inconvenient as a means of getting from one place to another. Worse yet, there's evidence that building roads to minimize distractions and interruptions from going fast in a straight line simply results in less attentive, faster driving, which is actually more dangerous for motorists. There was a steep spike in vehicular fatalities during COVID restrictions in the US, despite there being fewer cars on the road. Barone suggests that without traffic congestion to get drivers to slow down and pay attention to their surroundings, the designs optimize for faster car traffic coaxed otherwise safe drivers into a false sense of security at high speeds with predictable results. Also, traffic lights increase maximum speed but reduce average speed and freeway metering doesn't work. Please read the book so I'm not the only one ranting about this to my friends and family. Barone's observations highlight how even standards that are built to achieve commendable goals must carry an implicit set of values and A DNA replicated over and over in every new bit of construction, along with all its shortcomings and unintended consequences. Nobody would argue that getting drivers where they're going safely is a bad thing, but the ways you define and implement that objective say a lot about what you care about and what you don't care about quite so much. ISO standards aren't exempt from those implicit value judgments. Although ISO 9000 has some allowances for employee feedback, so long as there's some well documented internal process that's rigorously followed and checked, there's nothing in the requirements that forbid a business from treating its employees like garbage. ISO 14001 is a standard for environmental management, helping organizations identify, manage, monitor, and control their environmental issues in a holistic manner. I'm sure you'll be relieved to know that ExxonMobil is ISO 14001 certified. To combat the problem of civil engineering specifications that either don't address or actively undermine the needs of the people affected by them, Morone recommends that civil engineers take a less active role in prescribing what sorts of civic improvements should be built in communities, behaving more as facilitators of the community's stated goals than dictators of the one true path. Rather than looking at a city plan, consulting the tables in the civil engineer's handbook and saying, you need bigger shoulders on your roads, Morone suggests actively listening to the problems the individuals in the community face and addressing those problems directly. If someone complains that they have to cross a busy road every day to get to the bus stop, figure out a way to manage traffic to give them better access. If bikers feel unsafe at a particular intersection, build them a bike path away from the road, or make the intersection friendlier for bikes. These sorts of fixes don't just alleviate the minor concerns of the individuals who need to use this sort of infrastructure every day. They create new channels for access and movement, contextualized by the actual values and needs of the people who live there, making the whole town a nicer place to live. Obviously there will be conflicts of those values that need to be resolved, but Morone argues that the starting point for policy should be the explicit needs of the users, not some arbitrary, abstract, a priori good as dictated by civil engineers who have never seen the city they are improving. From this perspective, the ISO requirements that govern our cities and infrastructure have some important limitations. Although ISO makes some allowance for public commentary channeled through national representatives, the universality of their application kind of prohibits any sort of consideration for the specific circumstances in which they appear and function, let alone the diverse values of all the people they might conceivably affect. That's not to say that ISO requirements are a bad thing by any stretch of the imagination. I'm an engineer for God's sake. More than most people, I'm sensitive to the fact that in order for anything to work with anything else, there has to be some external pressure for uniformity. Without organizations like ISO, DIN, ANSI, and so on for prescribing and throwing their weight behind standards, many important technologies would be impossible. But there's something troubling about the way impartial paywalled ISO requirements are baked into the most fundamental operations of our towns and cities, with their unstated implicit values carried along for the ride. The power of standards to compel certain outcomes isn't always subtle. Corporate interests have put their thumbs on the scale more and more deliberately in recent years. Strong arming ISO committees to carve out advantages for their business by flooding them with partisan volunteers. The tactic former ISO governor, Martin Bryan, has called standardization by corporation. Microsoft recently engaged in this practice to fast track the approval of ISO 29500, the standard linked to Microsoft's proprietary open XML format, forcing the work of other technical committees working on things like nuclear waste disposal and textile manufacturing onto the back burner, to get open XML codified as quickly as possible. After all, once it's part of the standard, the industry will be pressured to migrate to open XML, and pay Microsoft to use it. In his resignation letter, Bryan suggested that standardization by corporation is becoming impossible to combat, and it's anyone's guess how long ISO will be able to keep those efforts at bay. As climate change promises to pound infrastructure around the world with worsening weather-fueled catastrophes, it's worth reflecting on the role that standards agencies will play in dictating the protocols and requirements of that infrastructure. Whether the unstated values and strategic omissions are fostering positive outcomes for the people who are most affected by them, or if they're just synchronizing industrial activities in a way that prioritizes conformity, conflict aversion, and control over welfare. Standards do a lot of good stuff. I'm glad that there were passionate nerds dedicated to fostering interoperability, safety, and some sort of baseline functionality for the stuff I use every day, from cameras to cars. But if their work remains inaccessible for anyone who doesn't want to or can't pay for it, if it's only representative of the values of the authors and whoever can wield influence over them, I don't think it's doing as much good as it could. Do you think ISO standards should be made freely available to anyone who wants to use them? Do you think pressure for universal design principles should be balanced against the specific needs of the people who live under them? Please leave a comment below and let me know what you think. Thank you very much for watching. Don't forget to blow up a subscribe while I share, and don't stop thunkin'.


Howdy, Mike Morton here, Program Manager on the Visual Studio Team. In this video, I want to show you some features in the Docker extension for VS Code that make it easy to build and deploy containers in Azure. First, I have heard from a number of users, they are not aware the Docker extension can help them easily scaffold the Docker file and optionally a Docker compose YAML file as well. So let's get started. Here I have a very basic .NET Core console app that processes orders. Let's add a Docker file to it and run it as a container locally first. So I'll go ahead and bring up the command prompt, and I will type in Docker add Docker files to Workspace and go ahead and select that. First thing I'll be asked is for my application platform. You can see we support .NET Core, Python, Node, and others. I'll go ahead and choose the .NET Core console, and now I'm asked which operating system I'd like my container to target. I'll choose Linux. This is where I'm asked if I would like to include Docker compose files or not. Docker compose files are real handy if you're going to maybe spin up multiple containers at once with a Docker compose up command, or even if it's just a single container and you have a number of flags for maybe environment variables and volume mounts. For now, I'll go ahead and select no. So now you'll see here we have our Docker file that's been added to our project, and I'm going to go ahead and build that Docker file. Docker file basically gives instructions for how to build the Docker image. So I'm going to go ahead and just right-click on the Docker file and say build image. Then in the terminal window, we'll be able to see the different steps that Docker is going to run to actually build that image. First, it will pull the base image, which is here in this from statement, and then it'll process the other steps as needed. When that's done, I'll go ahead and click over here on the Docker, what I call the Docker whale, or the Docker Explorer, and we'll see in our images that we should have a new image, a new order proc image. Here we can see just a few seconds ago that was created. So now we have a Docker image that's been built and it's stored locally on our machine. Now we want to go and we want to run that. So what I'm going to do is I'm going to right-click on that and just say run. And so that's going to execute this Docker run task, as you can see down here, and it's going to spin up the order proc image. And you can see in the containers panel here that that's been updated, and you can see that that order proc container is running. And now we can do things to investigate, to maybe look at the logs or inspect the container. I can right-click and do a number of options. I can start and stop, some things like that. I'll go ahead and view the logs and we'll see that this order processor is doing its job, it's cranking away, processing orders. Okay, now let's start using Azure to do this. There are times when you want to just try your app running in a container in the cloud to make sure it's going to work like you think it will. So let's do a couple of things here. First, let's build our Docker file again and create that image. But this time, let's use Azure to do that. So I'm going to go ahead and click build image in Azure and it's actually going to use ACR and ACR tasks to build that image. And it's actually going to then tag it and store it into my ACR registry. I'll go ahead and say this is great for the name and the tag of the image. And I choose the ACR that I want to use. ACR is Azure Container Registry. I could create a new one, but I'll go ahead and use the one I have. And again, select the image that I want to build, which in this case is Linux again. So now what's going to happen is my source code and the Docker file is going to be shipped up into ACR and it's going to build a image. And then like I said, it's going to store that image when it's done over here in my ACR registry. All right, so let's go ahead and expand that. And there's our order proc. That's one I built a few months ago. Let's go ahead and wait a couple of seconds for this. Okay, I fast forward 30 seconds or so. And if I come here and refresh on my registries, I should see that we have a new order proc image. We do. It's been labeled CA9, which is just a unique identifier for the tag. And now if I want to go ahead and deploy this to Azure, let's go back over to the terminal. I need to make sure, and I'll go ahead and get rid of that terminal from before. And I'm going to use the Docker login to Azure command. I need to make sure I'm logged into Azure. So here I'll go ahead and give it my credentials. And now you can see that I'm logged into Azure. That's great. I'll go ahead and go back to here and we're logged into Azure. So now what I could do is I could use the command line to interact with the ACI or Azure. And in fact, the way I do that is by using Docker context, which is something that has been around for a while that you can use to talk to remote Docker daemons. But Microsoft and Docker have recently worked together to enable deploying to ACI using these Docker contexts. So we have these new ACI contexts, which are like a type of cloud context. So we'll go ahead and use one of those. And again, I could use the Docker CLI to create that context and do Docker run and so on and so forth. But what I'd like to show you is how the Docker extension has made this easier. So I could manually create a context here if I wanted to, but let's take the shortest path and let's just right click here and deploy this image to Azure container instances and use that new integration that Docker and Microsoft have done. I'll click on that. And the first thing I'm gonna be asked for is to create a new context. So I'll go ahead and do that. And we'll just call this, let's call it my ACI context. Keep it real simple. What I need to do is I need to select a resource group. If you've used Azure much at all, you know, resource groups are really just kind of a grouping to put your resources in to kind of keep track of them and manage them. I'll go ahead and use an existing one. I have this My Containers Resource Group. I'll go ahead and use that. What's gonna happen now is you'll see down here in the context panel, just as if I had clicked the plus sign, a My ACI context was created and it was actually switched to be the current context. You can tell that by the plug. And then you'll also see that the extension has done a Docker run. And it says, hey, I wanna run against, I wanna run this image, which as you can see is that order proc CA9 image right here that we built just a few minutes ago. And so what's happening now is it's spinning up that container right inside of ACI. So I fast forwarded a little bit. Typically these take 25 to 35 seconds. As you can see, this one took just a little bit longer. We can see the containers that are up in that context. Basically, this is a container that's running up in Azure Container Instances. And I can do very similar things that I could locally. I can do things like view the logs again. So let's view those logs again. And here you'll see that we're processing those orders just as we would expect. I can also do things I can inspect that. I can inspect that container and see what's going on. And of course, I can start and stop that container. And just to show you that this really is using the same Docker commands. If I do a Docker PS to list the running processes, you'll see that I see that same distracted Morse, which is this one here, which is running up here, which is the order proc CA9. And so what the extension does is it just makes it so you don't have to know all of those Docker commands. And so I can just right click here and I can say remove that. And what's great about ACI is as soon as I remove that instance or that container that's running, the billing stops, ACI bills by the second. So now I'm not being billed at all. Okay, so that's the basics for using the Docker context, the Docker ACI context. Like I said, I can create multiple contexts. So if I click here on the plus sign, I can create a second context. So this is my second ACI context if I want to and I can choose a different resource group here. I'll just choose my France central resource group. And now I have two different contexts and I can switch between those contexts. So if I switch to this context, you'll see I have no containers running. And of course, I can switch back to my default, which is my local context. And I can say I want to use that context. And when I do that, you'll see that I see the local containers and the local images that are on my local host machine. Well, let's do one more thing. Let's go ahead and go back to our ACI context here. And I'll go ahead and say, I want to use that. So I mentioned that we can use Docker run and that's what was used when I ran this here. You can see that we did a Docker run command. I can also use Docker compose. So now that I have my context set to my ACI context, I can come over here. And even though I didn't add a Docker compose file when I scaffolded the files, I have one in here ready to use. So I could show you this. And here you'll see that not only am I gonna spin up that same, actually, let's change that. Let's change this to what was that CA9. Let's change this to CA9. That's the image I just built. You'll see I have another image that I'm pulling, which is my express app. I'm just using this as a sample. This is actually gonna be a little express app that's gonna open on port 3000. And I'm doing that for a reason so I can show you another neat feature. And so now I can just go here. Again, because I'm pointing to my ACI context, when I do a compose up, it's actually gonna run this Docker compose, the same Docker compose that I would run locally, but it's gonna run that against that ACI context. And what you'll see is I'm actually gonna get a container group that's made up of these two different containers and are gonna be in that same container group. Container group is an ACI context. Every container that you run up in ACI goes into a container group, but you can have more than one. In this case, I'm gonna run both of these containers in that same container group. Very similar to a pod within Kubernetes if you're familiar with Kubernetes. So these containers are getting spun up in ACI and we'll give them a few seconds to finish here. All right, so those containers are now spun up. We'll see that this is the order proc, same order proc as before. And I can view the logs just like we've seen before. There's those logs coming out of Azure down to my machine so I can keep an eye on that and see what's going on. I also can do other things such as with this Express app because it has a web app to it. I can actually open this in the browser. And when I do that, it's actually gonna open up to that public IP that was exposed up in ACI. And here's my Express app running up in Azure. All right, well, thanks so much for listening. I hope this was helpful. Please leave any comments down below and we'll hopefully see you in another video soon.


So if you guys, welcome back to another one. If you are new to the channel, I am GoPony, I do new car truck SUV reviews on YouTube. And today we are in the new 2022 Mitsubishi Mirage courtesy of Younger Mitsubishi in Hagerstown, Maryland. For more information on their inventory, please feel free to check out the link in the description box below. So we are in this one today because this actually has a starting price at under $15,000, which is unheard of these days. And so I recently reviewed this today. I wanted to check out the hatchback now because this one is a little bit less expensive actually. There's several changes for the 2022 model year as well. Not only that, you get America's best warranty being five years, 60,000 mile bumper to bumper, 10 years, 100,000 miles on the powertrain. But not only that, if you were to drive out to Younger Mitsubishi in Hagerstown, you actually get a double powertrain warranty meaning 20 years, 200,000 miles. That is absolutely insane. But ultimately in this video, we will be testing out and going over everything about this one from acceleration to braking, steering wheel ride quality, sound system, exhaust clip, all that fun stuff. So having said all of that, what do you guys say? Let's just go ahead and jump right into it. And as always, let's start with pricing. So as you can imagine, there are several different trim levels for the 2022 Mirage. First one being the ES5 speed manual starting at $14,645 ESCVT, which actually is the one we have today starting at $15,995 LE for $16,595 black edition, which is a new trim level for the 2022 model year starting at $17,195. And lastly, the SE starting at $17,895. But regardless of trim level that you go with, the power plant on the Mirage is going to be the same. Powering the little beast is a 1.2 liter naturally aspirated inline three cylinder engine, putting out 76 horsepower at 6,000 RPM, 74 pound-feet of torque coming in at 4,000 RPM. Power set to the front wheels through either a five-speed manual or a CVT. Zero to 60 time is going to come in at approximately 12 seconds, but we won't be testing that out here in a little bit. MPG numbers though coming in at 33 in the city, 41 on the highway from the manual, 36 in the city, 43 then on the highway for the CVT, taking regular unlit fuel. But now having got all of that out of the way, what do you guys say? Let's go ahead and find us right away. Let's put that acceleration here to the test and let's see how quickly we can get our new 2022 Mitsubishi Mirage here up to speed. All right, here we go. And we're at 40, 50. Five stay alive. We probably would have gotten to 60 eventually there, but yeah, it's not the quickest thing in the world, but I don't know. It's kind of as expected for the price range, for the miles per gallon that you get are also incredible, but yeah, it's definitely not the quickest thing in the world, I'll say that. But anyways, to go along with that acceleration as always, braking is equally important. So you will find front disc rear drum brakes coming standard for all-term levels across the board, nine-inch ventilated front disc to be specific, seven-inch rear drum brakes then. 60 is your stopping distance comes in at 127 feet and still it's not the best. I gotta say even for a small car, it's not the best. Having said that, braking feel is definitely on the softer side, so wouldn't have minded if they firmed up the brakes a little bit.  As far as ride quality goes, we do tend to feel a little bit more of the road, really in any subcompact car, including the Mirage, so that's definitely to be expected. Having said that, it's not too bad in my short test drive here today so far, but then again, Hagerstown roads are usually pretty darn good, so definitely having the issues so far. As far as steering feel goes, it's pretty much as expected, it's normal, it's not on the heavy side, it's definitely not on the loose side either, it's pretty much par for the course, what I would expect the Mirage to handle like. As far as cabin noise goes, you do get a decent amount of wind noise when you definitely get a good bit of engine noise when you really lay on the gas here, so good bit of noise coming into the cabin without a doubt.  That tells you about visibility, I can see perfectly fine out the back, you're 100% not gonna have any issues there either, but that about wraps up the performance segment of this review, you guys. Let's now go ahead and take a look at the exterior of our brand new 2022, Missabishi Mirage. All right, so here she is you guys, the new 2022 Missabishi Mirage, finished in white diamond. In case anybody was curious of our exterior color name, let's go ahead and get started with what's new regarding the exterior of the 2022 Mirage. Revised front and rear facials to start with, also the headlights and taillights have been updated slightly as well. Not a huge change, but just a slight little change there. Black Edition also is going to obviously add black accents along with some red horizontal accents on the front grille as opposed to the chrome ones that we currently have here today. Essentially all other trims are going to get those chrome accents on the front grille. Halogen headlights are going to come standard on all trims, but the SE, because the SE is actually going to give you full LED headlights, meaning both low beam and high beam. That is a luxury feature, you guys, but it is on the Mirage SE, so that's pretty cool. As far as the automatic feature goes, that can be had on two trim levels, being the black edition and the SE trims. Then looking down, you will see some cutouts for the fog lights on our ES, but if you actually did want to add fog lights, they're going to come standard on the black edition and SE trims as well. But pretty much rounds out the front end. I do like the slight revision. I think it still looks good, just like I said in last year's review, so definitely a good looking front end, but let's now go ahead and make our way to the side of the Mirage. So now since we are around to the side of this one, black windows surrounds do come standard body colored door handles for all trim levels. I like to mention that because sometimes on less expensive cars, you will get matte black door handles, so I do like that they're body colored. When it comes to the side mirrors, they are body colored folding side mirrors for all trim levels and they actually will get integrated turn signals for the SE trim level only, although you don't really need them quite honestly. I like the look. They actually put the turn signal indicators on the front fenders. It's a JDM look. JDM cars have done that for such a long time now. I prefer that quite honestly. I think that's a pretty cool look. But anyways, when it comes to the wheel configurations, 14 inch steel wheels with covers for the ES. That's of course what you guys are looking at right now. 14 inch alloys for the LE. 15 inch black alloys for the black edition. And then 15 inch silver alloys for the SE trim level. But pretty much rounds out the side profile here. Let's now go ahead and make our way to the back of the Mirage. All right, so now since we are around to the back of this one, this is the best look on this one of my personal opinion. You do have a black antenna all the way to the top there on the roof. Just below that body colored rear spoiler with an integrated brake light definitely looks very good on the Mirage. Just below that rear window wiper, but my very favorite part of this one, LED tail lights coming standard for every single trim level across the board. That is huge, especially in smaller vehicles. You want people to be able to see you from behind because you don't want to get rear ended, of course. So LED tail lights are amazing and they look dang good on the back of the Mirage in my personal opinion. Going down to the very bottom there, you will find a body color rear diffuser. That looks pretty darn good back there as well. There is a single exhaust outlet tucked away towards the bottom there. But as always, here is that exhaust clip. All right, so now since we are around to the back of the Mirage, when it comes to opening the rear hatch, it is a manual lift gate. So simply just left up on the handle, on the hatch itself. But once opened up, cargo capacity comes in at 17.1 cubic feet. If that was not enough space, there's a receipt to actually do fold down. So there's then a good bit of added extra cargo space there if you needed it. There is a cargo light obviously in that area. If you lift up underneath of the cargo floor, you will find a spare tire, which is always nice as well. And there's actually a cargo cover that comes standard on the hatchback at least as well. So that's pretty nice. Then make our way up to the rear legroom. That is going to come in at 34.2 inches. So for reference, I'm an even six feet tall. This is how much space I had in that second row there. Then there is no center armrest. There's no charging ports or ventilation or anything like that. Going honestly in the size of the vehicle, you probably don't need any of that anyways. Then make our way to the front seats. Manually adjustable claw seating does come standard for all trim levels across the board. However, I will say the SE trim level is not only going to give you a cloth leatherette finish, but it's also going to give you heated front seats then as well. So overall when it comes to seat comfort, it's okay. Not the most comfortable seats obviously because there's no real power lumbar support or anything like that. They're enough to get by basically. But then take a look at the steering wheel. It is tilt. It is not telescoping. It is wrapped in urethane for all trim levels but the SE because the SE is actually going to give you a leather wrap steering wheel which is pretty nice. Then make our way to the startup. Let me first start by showing you guys the key here.  Then when you flip it over lock and unlock. So a pretty basic key there. But we'll say with the SE trim level, it is a push button start actually. But we don't have that today unfortunately. So all I'm going to do here is simply put them up in the break and turn the key. But so then when it comes to the gauge cluster tachometers all the way to your left speedometer is front and center.  Like how much gas you have left, trip A, trip B, things like that. But all of your indicator lights are going to then be on the right side of everything there. Then make our way to overall interior quality. There is a front passenger vanity mirror which is newly standard for the 2022 model year. That wasn't there last year. So wanted to mention that. That's basically the new feature when it comes to the inside of the Mirage. Didn't want to say that when it comes to the SE trim that's going to add a good bit when it comes to interior quality including a leather wrap shift knob, some carbon pattern window switch panels, gloss black shift panel then as well. However, all trims are going to get automatic climate control meaning you just set a temperature and the Mirage is automatically going to take you to that temperature. So that's pretty cool. Just in front of the shifter you have a USB charging port, a little slot where you can put your cell phone. There are dual cup holders behind all of that. And then you have a manual emergency break just behind the shifter then as well. But overall interior quality is pretty basic, pretty to the point. So nothing crazy when it comes to that. Then make your awaited infotainment screen, seven inch color touchscreen display is going to come standard on all trim levels across the board. Bluetooth and audio streaming also coming standard but Android Auto Apple CarPlay also coming standard meaning if you have a smartphone simply hook it up via USB cable to the Mirage and you have free navigation displayed up on the infotainment screen. And the reason I'm emphasizing this so much is because this is a very inexpensive car and at this price range you actually still don't always get that. So that is pretty darn cold. But anyways, you can check out your radio information up there as well. By the way, when it comes to the sound system there is one of them and that is four speakers for every trim level across the board. So having said that, what do you guys say? Let's go ahead and turn on the radio see what we got playing today. And let's test out the clarity of this one.  I know it's four speakers you guys. It's definitely not the most exciting sound system out there. It should get the job done for the size of this vehicle but definitely not my favorite sound system I've ever tested. But last thing I wanted to mention to you guys on the infotainment screen is when you do put the Mirage in reverse you won't find a rear view camera taking up the entire screen which you don't always get letting you know who or what is behind you which is always is going to lead us into safety. So front side side curtain airbags do come standard drivers knee airbag up front as well. In the back you're gonna have latch AKA lower anchors and tethers and children for the rear car seats, rear tire door locks tire pressure monitoring system but also coming standard will include a forward collision mitigation system with pedestrian detection then hill start assist as well. Then if you were to go with the SE trim you were also going to get lean departure warning done as well. Overall, when it comes to my final thoughts here of the Mirage, this is an excellent price quite possibly the most inexpensive vehicle available at least here in the US. As of right now, you get America's best warranty not only that if you get a younger Mitsubishi here in Hagerstown you get double powertrain warranty which you can use anywhere in the US by the way you could drive all the way from New York and still get that double powertrain warranty which is gonna be honored wherever you're at. Android Auto Apple CarPlay coming standard is wonderful as well. As far as room for improvement goes of course it's extremely slow. Seats are definitely not the most comfortable seats in the world and the sound system is pretty poor quite honestly. But anyways, let me know what you guys think of the Mirage hatchback in the comments section below. That is about it for this one. You guys thank you so much for watching. Feel free to follow me on social media if you wanted to see what's coming next on the channel before it actually gets to YouTube. Be sure to hit the subscribe and the bell notification button if you're into new car reviews. That is what we do here on this channel after all. Do appreciate you guys watching more than you know. I will see you guys all in the next video. Stay Gold.


Welcome in to the Toddy Korba show. I'm Sam Murray joined with women's soccer head coach Toddy Korba and coach a One-in-one week for you this week a one-nothing loss at Catholic then you follow that up with your fourth shutout of the season To nothing at Frostburg State. What did you take away from those two games? Well, I think you know, we're we're still figuring a lot of stuff out and obviously we've got a large roster and You know have a select a game list that we're bringing to each game and then even within that There's just a lot of different options of different kinds of players and things that we can do. So I think it was a really it was an interesting week for us and that we were able to try some different combinations of people which really brought out some different styles in terms of how we play and what we're able to do and whether we're a little bit more creative or whether we're destroying things a little bit more or You know kind of whether we're trying to be a little bit more possession oriented or a little bit more direct So I think we really found out this week We have the ability to do all of those things based on kind of who we have on the field at certain times So I think it was it was a really positive week for us. I mean a frustrating loss to To Catholic and certainly a game where we didn't finish our chances And and we had some chances to at least tie up that game But you know a good overall effort against Frostburg Defensively you only allowed three goals this year. I'm gonna say you probably know this two of those three goals are on set Pieces on corner kicks. What do you have to do defensively to kind of clean up those those? Mistakes or not allow goals on those set pieces. It's just I mean really I you know We've always said it's just a mentality really, you know, I think Corners neither goal knock on wood neither goal has has gone in directly off a corner But it's been the rebounds and I think that's just staying tuned in staying focused You know man marking and being a little bit tougher and and being a little bit more aware of of ball and runners and So it's stuff that we have been been cleaning up and The team is well aware of the fact that that we've given up You know, those are those are two goals that really shouldn't shouldn't happen And so we've been working to make sure we clean that up Offensively a really cool story happened in that win against Frostburg seen or what you're Lauren Spivey senior senior Yeah Scored in that game a year to the day after she tore her ACL Which she happened to tear against Frostburg. Well, that's just an incredible I mean, this is what sports is kind of about sometimes right right and you know And I think Obviously, I didn't know Lauren Last year, but she has been working really hard I know coming back from the ACL and she actually wasn't even really cleared to play full contact until like the day before preseason so she's you know a month today kind of back playing and Yeah, got some got some good minutes Against Frostburg went in made it immediate impact and really grabbed hold of the ball and grabbed hold of the game for us and Pressured, you know the goalkeeper to really create the first goal from Ali Arter's and then got the second goal herself so it was she was a game changer and I thought it was You know to find out afterwards we didn't know I think Lauren kind of kept that to herself But to find out afterwards that it was the one-year anniversary and that she really went in and made a huge impact against Frostburg was awesome Yeah Looking ahead you're in the middle of your six-game road trip It doesn't get any easier as you travel to Shenandoah into sales to somewhat lengthy road trips What are you looking for from your team in those games? You know 90 minutes, I think that's been a big thing for us again something we're gonna focus on in training But we've put together three-quarters of a game that we've liked But that's you know, we've given away minutes and we've given a few soft goals So I think just tightening up mentally figuring out Who we're gonna play and where and you know how we're gonna try and dictate the game instead of responding to the game I think is another one, but I think just everybody continuing to To buy in to commit at a deeper level to give a little bit more And to get like continue to improve upon the things that you know that we're talking about in training That we know we need to to make better. Oh, we wish you the best of luck in both of those games She's Toddy Korba. I'm Sam Murray and you've been watching the Toddy Korba show


SiliconANGLE.com's continuous coverage of HP Discover 2011. SiliconANGLE.com is the site for reference point for tech innovation. We have news every day. SiliconANGLE.tv is where we take video out to the audiences and stood theCUBE as our flagship telecast. We go out to events and we explore knowledge and share with you and let ideas grow. And we're on our summer tour 2011 and we're here with Cornell Medical. Welcome to theCUBE. Thank you again. Okay, Eric, Dave, what do you think about the customers that are here?  At VMworld, we did a lot of customer interviews. Before we get into some of it, what's your assessment? We talk about proof points. Well, my quick assessment is HP customers have always been very loyal. HP has always scored high on things like customer satisfaction.  Now, you may be an HP customer as well. We are HP as well. So we have a lot of C class blade chassis, blades and blade chassis. And we were originally a three-part customer we've since moved over with the acquisition of HP and three-part. So tell us a little bit more about your role, your organization, what the IT organization looks like. Can we set it up? Sure. We have a lot of different responsibilities as I'm sure you hear a lot these days and we're trying to do more with less. And what we deal with is we have a lot of different people are throwing a lot of different requirements at us. Things like our clinical systems, exchange, virtualization. And one of the things that we were having problems originally with our storage is we were an EMC customer and their model at the time, and I'm sure it's still the same, is we were building purpose-built arrays. So we had one for email, we had an array for clinical systems and then moved that on and on. And we built out six or seven arrays and we realized that wasn't a sustainable model. Why? Because the infrastructure wasn't fungible across the application portfolio? We didn't have, we're in Manhattan. We have limited space. We have limited power.  So we're trying to get the most out of what we have with the limited resources and the ease of management for things like the C-class blades and for 3-par has been a huge benefit for us because you don't need that many people to actually manage what's going on anymore. So what was the symptom of that? Just there was people, it was... Gapx, Opx, Cooling. It was power, space, cooling and the management aspects of it. So we can consolidate all that down which is what we did into two arrays. We took those six arrays and we consolidated them down into two. And now we basically have two people who manage the fiber channel infrastructure and also the center arrays. So you're supporting all those applications that you mentioned, you mentioned Exchange, Clinical. Are you doing Exchange 2010 yet? We're in the middle of doing a migration so we're on...  We just have Microsoft on, yeah, I'm supposed to do that. No, it just depends on who you're talking to within Microsoft. It depends on who you talk to. I've heard them say that you can do Direct Attach. I don't see a lot of people doing that. You know, I coined a blog a while back that said Microsoft has its head up its dash. Pretty funny. And they were just on the cube but they leave the area? Well, no, so the inside baseball there, John, is that Microsoft's Exchange group doesn't want you using sand on Exchange. They want to simplify. But in reality, we know if you can share that infrastructure across multiple applications, especially for a mid to larger size organization that's much less expensive, right? How many seats do you have on Exchange? We actually have about 30,000. Yeah, so we found that the crossover point was about 750 seats. And I think that shifted a little bit. It may have gone up with Exchange 2010. It might be up to 1,500, 2,000, but 30,000, no brainer from a cost standpoint, isn't it? It's absolutely no brainer. So you sand, I mean. Yeah, and the large requirements that we have for our mailbox users, I mean, we have people who have very large mailboxes, 20, 25 gig, 30 gig mailboxes. And to put that on Direct Attach is just not doable for us, you know. We have a lot of people who would complain pretty quickly if we started using that. So one of the things with three parts is you're able to leverage the virtualization of all the disks. So to spread the IO out across the pool of disks that we have, and that's just not something you can do with DAZ. So that's one of the big benefits for us. And not only do we have Exchange running on there, Exchange is virtualized and running on the same disks that we have our mailbox databases running on. When did you bring in three-par? Four, right? Three and a half years, we've had three-par, so. So, Eric, I have a question for you and I don't know if you can answer this because I talk to a lot of IT practitioners and they know their space really well and they know their products really well. They tend not to know other vendors necessarily really well because they don't have hands-on experience. But, but you saw sort of traditional storage. Now, you've seen that morph to add what we're called by some people, feature capabilities like thin provisioning. Right. To their products, does that tick the box? Does it do the equivalent or is three-par really that different is what I'm trying to get to in your estimation? Absolutely, three-par is different. I mean, in the mid-range, which is where we are, I mean, we're not an organization that's going to be able to make a huge investment in something like a DMX from EMC. The space requirements, the power requirements, just the monetary requirements were just too high for us. So, we graduated a little bit from where we were with EMC's CX500s and we wanted something, we wanted to reach for something a little bit more and we couldn't go for a DMX. So, three-par fit that model for us very well and thin provisioning was one of the huge, huge benefits that we saw right away because we're presenting out terabytes and terabytes out to our host and realizing that they're not actually using that data. Somebody comes to you and says, I want to buy 10 terabytes of storage but in reality, they're probably only using one terabyte or maybe even less than that and they just want to have it just because they want to feel good and they bought it and they want to make sure that they have it. So, what we did with thin provisioning is we provisioned out all that space to them and it looks like they have that space but they don't need it. So, we can use that for other things and sort of build that around our budgeting cycle. What's your organization look like, your IT organization and how does it report up into the broader organization? So, we have different groups who are basically spread across the different technologies that we have in database, email, virtualization and so then we have the CIO up at the top and he'll come down and talk to you anytime the day or he'll send you emails anytime at the night and he'll just come down and talk to somebody like me who is at sort of the mid-level. Just a regular guy. Just a regular guy doing my thing. Who's the CIO report to? He reports to the dean of the college. So, is the dean kind of like the CEO of sorts, right? So, a lot of CEOs that I know just want to outsource everything to the cloud. Is your dean the same way? Like just outsource them. No, not at all. It's very difficult for us to outsource things, try to put things out in the public cloud because of all the regulatory requirements that we have and nobody feels comfortable with putting our data out in the cloud when we have things like HIPAA requirements to deal with and who's responsible for that data if something does happen to it, gets lost, stolen, somebody hacks into the system. So, traditionally we don't sort of fit into a lot of the molds of some other organizations fit into where they're just very willing to put things out there. We're very protective of our data and our PHI. Health information of patients is very near and dear to us and we like to hold on to it and we want to be in control of it. So, what we've done instead is tried to build sort of a private cloud and without even saying that we're building a private cloud, we've tried to do that with Repar and HP and VMware and put all those things together and really leverage the infrastructure that we have and be able to be very agile and adept at what we do with all the requirements that are being thrown on us all the time. Yeah, so a lot of people don't like that term cloud. A lot of IT people that I talk to sort of look down on that, right? Right, I really call it outsourcing. It's really outsourcing. Yeah, so the public cloud is a form of outsourcing. It sounds nicer then. But it's good marketing, right? IT people don't really usually market themselves. They're actually quite humble, even though they know they're solving some of the world's hardest problems. But we could talk generically about cloud, public cloud, private cloud, hybrid. Do you, so you're building your own sort of private cloud or IT as a service, is that sort of a direction that you're going toward? I mean, I think that resonates better with most IT people. Yeah, absolutely. We're trying to build a very, building block approach and be agile in the sense that when somebody comes at you with an application that they want to run, that it takes a very short amount of time to build the components for that application and get it up and running and stand it up. And so we're trying to do that quickly, efficiently, effectively and at a good cost point. So, three part uses this notion of utility. I mean, does that resonate with you?  Absolutely. Just plug it in? Absolutely, we plug it in and it just works because a lot of people have been very skeptical about putting all those different workloads onto the three part. And we've had no problems, no service level problems with any of our customers. Like I said, we have a lot of different applications and we're looking to add more all the time. Is the skepticism because you don't have a lot of knobs and dials and bells and whistles to turn and tune? A little bit of is that, a little bit is the old way of thinking about storage and how it was provisioned in the past and the limitation of you have 10 spindles to work with, 10 discs to work with and being able to pool all that storage is a huge benefit for us in the three part model. So, people have been sort of the idea of showing me, show me how it works, show me, let's put a couple applications on there and let's see how that works and then okay, we'll add another application, let's see how that works and we've built it up over time and it's worked out really, really well for us. So, Eric, how long have you been in IT? Longer than I'd like to say. So, what's your favorite product ever? I mean, you could say, you know, could be an iPhone, could be, could be, I mean, what's the best product out there that you've ever had an experience with? Besides my Atari 2600? Oh, okay, that's cool. I love it. Wow, would you start in IT when you were 13 or? No, no, no, no. Everybody had an Atari 2600 here growing up, right? That's awesome. Besides that, I'd have to say right now, it's absolutely the three part. Absolutely, hands down. And maybe- That was not a setup question, right? I mean, we didn't talk about that beforehand. And maybe just slightly below that is our blades, our HP blades, so because- Really, you get excited about blades? I do actually, I love talking about this stuff because it works really well for us. It solved a lot of problems that the blades did and HP is very responsive to us as customers whereas some of the other organizations like IBM and Dell were not as responsive. They were responsive maybe in different areas. So I've talked to a lot of three part customers in my day. I get the same thing. Yeah, yeah, it's great, it works, we set it, we forget it. Is there something though that you wished they'd do better?  You know, I think like a lot of organizations integrating their software products with things like Exchange and VMware and SQL, I'd like to see a lot more development in those areas and making them work a lot better, making them work sort of in the three part model where there's not a lot of hand-holding you have to do. Absolutely is one of the things I would like to say. So application integration. Yes. Would be top on your list. Absolutely. Because that's what's driving the quote-unquote business for you guys, right? Absolutely. Yeah, so talk a little bit about that dynamic between the application folks, the infrastructure people, CIO, CIO, you know, a lot of CIOs I talk to, they care about risk. Right. You guys care about cost and efficiency. Yes. Application people, what do they care about? They just want their application to run well. They don't care about your cost, do they? They don't care about the cost at all. They just don't want to get a call from, you know, the customer, the end user saying, hey, this is a horrible experience. You know, I think that is where I come from sort of marrying the two things together, the back end infrastructure and the application as a service is, I want the same things. I mean, I don't want people calling me and saying, hey, you know, we're having problems with this. So, and that's the perfect scenario for three par because some of the things under the hood that it can do that if you are having, you know, maybe some areas where applications not performing as well as you thought it would with the setup that you put together is that you can change that on the fly. You know, you can optimize your storage, the way that you need it for a particular application. Like, you know, Oracle Rack, you're doing that or SQL or our cache database that we run for our clinical systems. What's the thing that you're most proud of thinking about specifically from the IT organization that you guys have accomplished in the last, you know, five, seven, 10 years? Two things, virtualization. I think we've done a really, really good job with virtualization. I think we've done a good job in explaining it and helping our customers understand what it is and what it can do. The density of virtualization as far as server-side virtualization, we've been able to get some really, really good densities using the HP, you know, C-class blades and using three-par storage. The other thing is this migration that we've done and we're still in the midst of doing it from our legacy email system to Exchange. But I think the three-par is definitely one of the things that, you know, I took a lot of heat for and it was one of those things that you can sort of kill your career. You know, if it doesn't work out. You stuck your neck out. I did. I did. And, you know, one of my coworkers helped me and stuck his neck out as well and we brought a lot of people over, you know, to the believers side of the equation and there was a lot of naysayers in the very beginning. They didn't know who three-par was. So it was unknown. It was the whole workload, mixed workload issue. Yeah, is this really gonna work for us? The magic juju of the three-par box, spreading data all over the place. Exactly. You know, I can see why people were concerned about it.   And if we lose our clinical database, you know, that's huge, you know.  But, you know, from a practical standpoint, it may take you a long time to recover from something like that. So that's not something that we can necessarily afford to do.  What got you interested in three-par? Just read about it, or did they call on you, or did that go down? We had seen, I had seen a demo about a year and a half before we started really talking to them seriously about it. And the technology was just different at the time. I mean, the model was different.  It was, you know, we have this big pool of storage of all these disks that are running. And, you know, yeah, if you need to change it, you know, you need to go from RAID 10 to RAID 5 or vice versa, yeah, just go ahead and do it. I mean, there's a few commands that need to be run, but it's very easy to do. And being able to do the mixed workloads where, you know, we started throwing three, four workloads at an EMC and you realize you have a lot of hot spots all of a sudden, you have IO problems, you know, and from the node perspective on the three-par side, it's much more scalable. So when you run out of capabilities, if you run out of cache, for instance, in EMC, you have to buy another array. You know, if you run out of cache, which I haven't seen in the three-par, you buy another node pair, right? You just build it out. So, you know, from the front-end standpoint, you have a lot more connectivity on the three-par side. You can connect hosts up in multiple channels, multiple pathways that you couldn't necessarily do with EMC. So you saw that, the light bulb went off, and you said, all right, I'll take a chance. Absolutely. And it's worked out pretty well. What do you make of this whole converged storage? I mean, you know, the three-par iBricks thing is there.  Right. Is that something that you want to see three-par do? Do you see advantages of that convergence, or is that more sort of marketing to you? It's not marketing. I think, you know, with the organization, the way that we're built, and, you know, like I said, the amount of resources that we have, it really helps us to have a single platform, software platform, that we can actually manage that with as few people as possible. So the three-par platform really works well for us in that sense. You know, I would love for us to maybe get into some of the X9000 things like that, but it's not as practical for us. You know, there has to be a little bit more compelling reason for us to jump into yet another platform, which brings a whole lot of other things. So, you know, we're also front-ending our NetApp with three-par as well. So it gets complicated really quick. All right, Eric Krueger, we're here with Eric at HP Discover, an IT practitioner, talking about three-par, your adoption of three-par, the chance that you took, it worked out really well. I'm glad. It worked out. We've always been very impressed with three-par and was kind of a catalyst toward simplicity in the data center. So, well done. Thanks for coming on theCUBE. It was great to have you. Thanks for having me.  Thank you.


So, just to note, a session that is on the printed schedule for this room in this slot won't be happening, so if anybody came for that session, you're in the wrong room. If you are here for this session, then you are in the right room. Okay, do you know if there's a lot of people still coming from lunch, or? Okay. Hello, everybody. Welcome to a session about the progress of media initiative for Drupal 8. My name is Giannis. My handle in all various Internet things and Drupal.org and Twitter and all that is rsm. First I owe you an apology. I had a last minute problem with my slides, so I'm not used the completely up to date version. I pulled down things that was on GitHub, because we are storing these slides publicly, because mostly Dave and myself are working together on them and then giving this same talk on various events. But more or less everything except my presentation and my name should be on it, so I hope you will apologize me. I am a software engineer from Slovenia. It's a small country next to Italy and under Austria to give you an idea. I work at examiner.com. Examiner is one of the biggest Drupal websites. We do fun stuff. We handle a lot of traffic. We create a lot of content. We use Mongo, which is probably not very common in our community. We also recently started to share our content with various different destinations inside our mother corporation. To solve that problem properly, we started to work on publishing platform that will feed all these sites with content. We decided to go with Drupal 8. So a lot of stuff that I've been doing related to media is during my work time at examiner because we need these two, so just like a small note and thank you to my employer to allow me to do that. Sometimes I work on things that are not strictly necessary for what we need. So first thing, our slides about Drupal 7, what we have in Drupal 7 at the moment. We have file fields and image fields. You're probably all familiar with that and there are a lot of limitations. Files are limited to fields. You cannot reuse files. Drupal will automatically delete files for you if you delete a note that this file was uploaded to. You cannot make files fieldable, et cetera, but then we have a few contrib modules that improve that. We have file entity that which brings you possibility to add fields to files, which allows you to add metadata. Then we have file lock, which will prevent files from being automatically deleted because if you install one of the modules like media that extends core files with possibility to reuse them, then you certainly don't want files to be gone arbitrarily. Then we have a few extension modules that allow you to embed remote media. We have integration with CK editor and back port of entity embed, which I will tell more about later. There is also Scald module and a few other modules that basically do the same job by re-implementing everything from scratch. Scald could be compared to media and solutions around media feature-wise, but it doesn't share any code. This is one of the problems that we have in Drupal 7. We have a lot of competing solutions that don't cooperate. It's impossible to mix them, to integrate them. In my view, this is a huge waste of resources. Let's see what we have in Drupal 8 core. We finally have embedding in WYSIWYG because you will probably know that we have WYSIWYG in Drupal core by default now. One of the features that come with core WYSIWYG is embedding of images in the WYSIWYG area. It works quite nice. You can also add captions. You can define alignment. If you move this image around, caption follows you. It doesn't stay where the image was initially positioned. So that's a pretty good job. The only limitation that we have is that we cannot reuse files that are already in the system. We have to upload a file every time when we do this. It will also track file usage. If you try to delete the file and you are embedding it somewhere in some WYSIWYG area, Drupal won't allow you to do that because it will know that it's used somewhere and it will also tell you where, which is nice. This is something that competing solutions, which we often compare us with, don't have as far as I know. Then we have very basic file listing. You will see all the files that are in the system that were uploaded using file or image fields. You get basic information. You can filter this. It's a view, so you can modify it. But it's not a media library as you would expect it. You can't use it to organize files, to change them or anything like that. It's just a listing. We also have this, another view, which will list all the usages of a file to solve exactly that problem that I explained earlier with WYSIWYG. If a file is used in a WYSIWYG field somewhere, you will see it there. We also made the automatic cleanup configurable, so now it's much easier to override that because in Drupal 7 we needed another module. We had to fight that. Now in Drupal 8 we just have a simple configuration value, which we can set and either make this period after which files will be deleted longer or completely disabled. We fixed file deletion. We have WYSIWYG. We can embed images in WYSIWYG, but we can't embed anything else. We still cannot reuse files. We cannot field files. We cannot make them fieldable. It's hard for us to handle metadata. It's still limited to fields. We don't have media library or anything like that. Files are entities, but they're not full-featured entities as you would expect. And you will say, only that? It's like, what have you been doing all five years? And it's partly true. We spent a lot of time at the beginning of the release cycle with planning and also arguing a bit. But at New York Camp 2014 we came together. Organizers did a very good job of bringing everybody there on site and they locked us in a room and said, sit down and stay in there until you come with a solution. Which actually happened. We came with a plan. And the most important thing that we decided there, which maybe sounds like something minor, but conceptually is completely different than what we had before, it's creation of smaller independent components that are reusable and pluggable. Which means now we can have different competing media solutions that will be reusing same smaller pieces, which means collaboration, which means less waste of resources, less waste of our time. And that was the main achievement. Like instead of heavy media and scald, we decided to have smaller components oriented at very specific tasks like storing files, embedding files in WYSIWYG, picking files to be reused somewhere. So these are all smaller problems that are currently in the seven solved in big pieces and in the eight we're solving them in smaller modules that can be reused among different competing solutions. And another attribution to nice camp organizers this year, one year after this first meeting, they did a very good job of inviting us everyone to New York again where we had a sprint for a week, which helped us push forward a lot of things. And here we are, first independent component, which I already mentioned with the seven, it's entity embed. It's a module that solves embedding just any entity, not just file entities into WYSIWYG. It's currently in quite good shape. You can use it. We still have to improve UX. We still have plans how to abstract it. And it was also partly back ported to Drupal 7, so you can also use it there. We still have to integrate it with entity browser, which is another component I will explain later. And it looks like this. You configure different embed buttons. Each button is responsible for one entity type. In this case, we configured button for files. Are you able to see this? So at the top it says file, and then from the drop-down, you basically picked which entity type your button will be responsible to. And this is most important at this point. Then you can also define which icon will be used with this button when you actually see it in the WYSIWYG toolbar and which four matters can be used with it and things like that. The most important part is you define a button and define which entity type this button works with. And then when you click on this button when working with the WYSIWYG editor, you get this page. And this is basically the autocomplete field that you are familiar with from, let's say, tagging with taxonomy terms. It will search for an entity, in this case, for this file, for this gif file. And then you will be able to define which formators, which formator to use for display and configuration for that formator. And then you also can define how to align it, like everything that you know from course image embedding. And here it is. And then you can edit it again. You can move it around. So it works very similar to course image embed except it supports just any entity. You can embed taxonomy terms into nodes or nodes into nodes.  And it also works in a very clean way. It's just one HTML attribute, it's custom Drupal's attribute with few data arguments that define which entity type is that, which entity type, which entity UUID is it, and configuration for formator. And then when rendering your content, text filter takes this and transforms it into a rendered version of your entity. So it won't persist, look and feel of the entity that you embedded in here. If you change the template later, it will respect that new template, which is very important.  This solution, it will also follow you when you do redesigns. We are also working on embed API. It's abstraction of the entity embed module. It's module that will provide foundation for various embed modules. One of them is entity embed, which I just showed to you. But then we also have URL embed, which works with URLs If you want to embed, let's say, a YouTube video, you can just use URL of that video and URL embed with some plugins should be able to handle that for you. And we're also planning to work on shortcode embed, which is something similar like in some forms you had some short codes, which would then translate into some kind of larger markup, would allow you to pre-define different pieces that you can reuse and things like that. Then next component is entity browser, which I already mentioned before. Entity browser is responsible for creating, displaying, and selecting content that you need to reuse in some other place. Let's say when we integrate this with the embedding solution, instead of having that ugly autocomplete field, we put entity browser in there and then entity browser allows you to open a model or something similar where you get lists of files that are in your system. And when you pick those files, entity browser takes care about communicating information about these files to the embedding solution, which then knows how to use them. Of course, we want to use views inside it, because views essentially provide all sorts of listings, and media library for example is just another listing, but it's not limited to that. Like you can have totally custom uploader solution where you just drag and drop images and system uploads them and creates file entities for you or anything else. We also integrated with inline entity form, so you can open an entity browser and then the inline entity form will appear, so you can actually create another entity in the same window, in the same field in touch. It's quite a complex solution, but we hope that when it's done, it will allow us to do very interesting things. Yeah, but it's kind of usable at the moment. We are using it in our PAP tool. The main constraint that we have at the moment is that there is no configuration UI, so if you know what you're doing, you can hack YAML files, which are basically configuration for entity browsers, and if you know how to do that, you can actually achieve a lot of things. If you don't know how to do that, then there is no UI that will help you, but we're always happy if you want to experiment with it, you can ping us and we will try to help. There is also a module that comes with some example configurations, which you can use as a starting point. It's called entity browser example, and it lives in the same repository. Let's see how it works. We have a very basic node here with title and one entity reference field. When we click on this button, we open the entity browser, and we have two so-called widgets in this browser. One is uploader and the other one is library. We currently uploaded a few images using the RobZone.js library, which allows to do drag and drop things and nice, fancy experiences like that. And then in the other widget, we have a view, which displays existing images in the system, and we created our, let's say, slideshow in two steps. We uploaded a few images and then we went into entity browser again and used a few other images that were already in the system. So this is perfectly possible to do. We are using this on our project. There are, of course, a lot of bugs and a lot of things that need to be improved, but I think it's a very good start. Okay, then we have another module, which is called inline entity form. But what's that? Isn't inline entity form Drupal Commerce stuff? Of course it is, but we said that we want to collaborate and we are not limiting ourselves just to modules that are created as part of media initiative, but we're also looking around and trying to identify modules that will work for us too. And inline entity form is an example of a module that was created for Drupal Commerce, but it's done in a very general way, which allows you to use it in a lot of other situations. And this is exactly what we want to do with our components. We are not limiting our components just to media use cases. You can use embed solution or entity browser solution for any other problem. You can use entity browser to search for related content that you want to link to the content that you are currently working on or things like that. Together with maintainers of inline entity form, we spend a lot of time to port it and it's very usable at the moment. It has entity browser integration, which means if you are familiar with inline entity form, you know that you have this possibility to create entities inline or to reference existing entities. And where you reference existing entities, they display an autocomplete field. We now swap this and display entity browser instead of that. So you can use entity browser to reference existing entities for inline entity form. It still needs some code cleanup I guess and we would like to have more tests in it, but it's very usable. So if you have use cases where this comes useful, you should really take a look at it. This will be a similar example than what I showed previously. Instead of having these very basic list of files, we swapped that with the inline entity form, which makes it even nicer. So we can create a photo media entity with inline entity form and then we see this familiar table that we also had in D7. And then here below you can see that we opened the entity browser. It's this entity browser that swapped the autocomplete field and now we are uploading few more files and we should probably scroll this up a little bit. And when files are uploaded, upload widget creates media entities for you and you get them in this table. And now you can reorder them or edit them which we'll use inline entity form. So it gets very interesting. Like you can mix all these different modules from Drupal ecosystem to achieve very interesting experiences. Then we have file entity. File entity is we call it storage component. It's one of the ways how to store your media, how to store your files. Currently there is an unofficial port. There is some planning going on how to approach this for DE8. Maintainers want to change its approach a little bit from D7 but they don't agree on it entirely. But if you want to use it on existing Drupal site you can use unofficial port. This unofficial port is already used on live websites as far as I know. So if there will be a radical change when port becomes official I guess there will be some kind of migration path. But disclaimer don't use it in production. But listen to me. Then media from Drupal 7. Media will be just one of the, this full featured providers of media experience or I tend to call it. It will basically just glue all the components together. It will depend to other smaller modules and come with some basic configuration. And of course this can be done when components or at least majority of components are finished. So we don't have any news about that. But you don't have to wait for media to be finished. Like you can start playing with these smaller components and there is quite big possibility that for at least some use cases that you might have will be enough. You just have to play with configuration and try to put it together in a way that works for you. I see these modules like media that provide, just basically provide configuration and dependencies more like an example modules in D8. You will be able to use them but you could only use them as a reference to see how they do it and then you could do it in a slightly different way. Like I usually compare this to Drupal Commerce which comes with a lot of modules. It's huge ecosystem. And you have two ways of approaching it. You can use commerce kickstart distribution which brings everything together gives you a lot of defaults configuration. So you have better feeling of what is possible but you can certainly pick just individual modules from the commerce ecosystem and build your own solution without touching commerce kickstart at all. And I see modules like media like kind of equivalent of commerce kickstart in our case. Then we have media entity module. It is alternative storage solution like kind of competing with file entity. It stores your media in a slightly different way. It takes slightly different approach. It creates a new entity type from scratch and then uses standard Drupal Field API to do everything else. It's very usable at the moment. We have basic UI. We have an API to handle metadata. Let's say if you create a reference to a YouTube video in your system and you want this module to pull metadata from YouTube and store it in local fields, it allows you to do that. And we already have a lot of providers. You can use it with YouTube, with local files, with Twitter, with tweets. You can treat your tweets as your media. It integrates with Instagram and some guys are currently working on audio plugin for it. And it comes with very basic media library too. We still have to integrate media library with entity browser, which will make library usable inside of entity browser's views, which will then give you nicer experience when searching the existing media items in your system. Like video that I showed earlier had a simple table with thumbnails and checkboxes. So this is kind of improvement on top of that. We also missed some configuration UI with this module too. We have some, but not everything can be done in UI. So if you really have to want to play with it, you will have to hack YAML files at the moment. And we don't handle any rendering at the moment, but since this is very standard Drupal entity with reusing standard Drupal files fields, like file field or image fields, and you can configure your rendering to some extent with just with stuff that comes with core. And it also comes with like validation API that will let's say if you want to create a piece of media, in our case, the tweet, and you copy URL or an embed code of a tweet that you want to use. And then if you do a typo when copying this, let's do a typo, validation will kick in and it won't allow you to save that because it will detect that this isn't actually a reference to an existing tweet, even if it looks like one. But when we fix that typo, we save it and then you will see that we have two other fields called tweet content and retweet count, which is now filled in automatically for you because I define mapping and told media entity to fetch this information from Twitter's API and to save it in a field for me so I can use it locally. And we also have media PINCHI module, which is not a disease. And it's like first let's say usable example of a full featured solution. It's a module that depends on media entity and comes with some basic configuration and if you want to play with media entity, you can just download this, install it and you will get a lot of default configuration which you can use to explore. And learn. And then we also have crop API. It's a very basic module that tries to provide very basic APIs for cropping tools. It gives you storage, which is using entity API. It's not using custom tables like solutions in D7 date. We have entities now and it is designed in a way that can handle both of most common approaches that we have in cropping world. One being defining an area which you want to crop and the other one being just defining a focal point. So this storage mechanism is able to store both of them and then it also comes with few basic image effects which you can use then to define your image styles that will be using this crop information. There is no UI yet and we won't be adding any UIs to this module. What we're hoping is that people will be using this storage component when they will start working on their UIs and the biggest benefits we see here is UI is a very subjective thing. I like one solution and somebody else likes another solution and it may also happen that you start with something and then you don't like it anymore and you want to switch to something else that looks a little bit differently. If all the crop UIs will be reusing this same storage component, you can just swap them because the data that is stored underneath stays the same and we also save some work because not every crop solution will have to re-implement storage and image effects over and over again. And there are already some people working on UI parts of it so we are seeing some traction there which makes me very happy. Then we have Drop Zone JS integration. Drop Zone JS is the drag and drop uploader tool that you saw in one of the screencasts, actually in two of the screencasts. It is using Drop Zone JS library and our integration module initially provides form element which means you can use Drop Zone for any form if you have a completely custom form for whatever use case you have. You can use Drop Zone there and then we have entity browser integration on top of that which is what you saw in action previously. We still have to integrate it with core image and file fields and we're hoping that we'll be able to do this sooner rather than later. One of our members is already working on this. And then we need to do some cleanup and tests and I think this will be everything that this module will provide but since it gives you a very basic form element you will be able to do a lot of interesting things with it. This is Drop Zone's webpage and you already seen how it works. It creates an area where you can drop files and it will upload them asynchronously or if you don't like drag and drop you can just click on this area and it will open file browser for you. And I hope that this will be replacement for Plopload module in the eighth because Plopload comes with a lot of extra weight. It has different back ends. It comes with HTML5 back end with flash back end with silver light back end and I think we are in the times where we hopefully don't need that anymore. This is purely HTML5 so it's much cleaner, it's much nicer to work with. Then we also have full back formatter which is basically a field formatter that allows you to create priority list of formatters that might be usable for your field and then first of them which will return useful content will be used. One usage for this would be a field where you reference videos and you have few videos from YouTube, few videos from Vimeo, few local ones and you can't use one formatter for everything. So you would use full back formatter and then tell full back formatter that you want to use either YouTube formatter, Vimeo or local video one and then full back formatter will be able to determine which one of them should be used for a specific item that you uploaded or created. Then we also, I think this module already exists for the seven, it's been in planning for the eight I believe and it's basically reusing of formatters for image fields, file fields and entity reference fields. Like currently in Drupal Core you have special formatter for file fields and special formatter for image field and sometimes you would like to reuse them for whatever reason, because both fields essentially store files, reference to a file and this module will allow you to mix that. Then also file download module which will be responsible for downloading files, serving files, sorry, and logging that. And so where are we? We stayed with the plan that we will stick to smaller components and especially the example of inline entity form shows how successful this is. Like if we wouldn't go down that route we could never use inline entity form for media cases, but now we can and we've seen that it works. We built momentum to some extent, we would still love to see more momentum. I did notice that recently when Drupal 8 itself is approaching state where people will have courage to use it, more and more people started to send emails to Ping on IRC, asking questions, trying to play with components and we've been trying to mentor all these people and to guide them. So I think that momentum is actually building. It's just maybe we wished that it would happen faster, but sometimes you can't speed things up until they are ready. We struggle with communication a little bit. We don't communicate enough with the community. Like we have these kind of sessions, but I don't think that's enough because there are like tens of thousands of members of the community and they are not all in there. We'll see how that continues. We try to, if everyone that approaches us and asks for mentoring, reviews, suggestions, we try to answer. At least I can speak for myself. Sometimes it takes me like a few days more that I would like, but we all have other things to do in our lives. I am not sure what will happen if momentum grows rapidly because it's already sometimes too much of people asking things, so we will have to figure out how to solve that. And we are still looking for funding. We had few Google Summer of Code projects in the past. We had one this year too, which is essentially funded by Google, so it's kind of funding. And as I already said, Examiner allows me and some of my colleagues to work part of our time on things that benefit the entire community, but other than that, I'm not aware that anyone else would be doing media on non-voluntarily basis. We need help. That's the bottom line. If you noticed with every component, I also added very rough estimation, how much work is needed to complete it, which is very, very rough. I might be completely wrong, but I was just curious, because we never did that before, and I was just curious if we just do very rough estimations for every component and sum everything together to see what the actual figure will be. And when I summed up everything from previous slides, it came to around 20, 24 developer months, which is a lot of work. And we can probably predict that it will be even more, because if we have very defragmented community, when people can just spend an hour a month, we spend a lot of time with communications, so this might even go up. This doesn't mean that media in the eight won't be usable before that. Like as you've seen, you can solve a lot of problems already, but there will certainly be things that you have to work around until we invest at least this amount of time. And as I said, don't hold me on that. I was just curious. It was interesting to see a number. This is a list of our contributors. We are seeing more and more of them, and there's more than one frame for pictures of all of you. If you want to get involved, we have Drupalmedia.org page. We have weekly scroll meetings on our IRC channel. We have a group on groups.drupal.org. And I would say if you follow our group, it's probably the best single point source of information. We store our code on GitHub group, but we sync all our repos to project pages on Drupal.org. So if you either go on GitHub or look for these projects that I explained on d.o., you should find the latest version of code. And we are also using issue queues, Drupal.org issue queues for development. Just instead of patches, we use pull requests on GitHub because it's easier to review, but all the pull requests should be linked from the issues. So you should have references around. And if you are shy and you don't want to expose yourself in public like in IRC or on our group, you can ping Dave or myself directly if you have any questions or concerns, suggestions, ideas. We're always happy to listen and help. Very happy to help. We also started a Drupal 8 media guide which is on GitHub too. It's basically a GitHub repository. There is not a lot of useful information in there yet, but it's improving and we want this to be the main source of information for Drupal 8 media in general. We have a sprint on Friday. We're also sprinting to some extent during the week. And we will have a sprint at Batcamp. So if you want to help, come to me on Friday or if you are in Berkeley, end of next month, you're also invited to join us. I will also like to mention Aaron. He was a very, very important Drupal media contributor. We always succeed standing on giant shoulders and he was our giant. He was diagnosed with ALS and he passed away this year, but now we have this yearly Aaron Wimburn award to respect his memory. Thank you, Aaron. And thank you. And if you have any questions, there's a microphone. Because all the sessions are recorded, you have to speak into it. Hi there. So I see that you were typing in different languages and how, do you know if anybody is using this on a multilingual, any bold site yet? With this meaning like the group of media tools? I suspect there are, but I don't have any firsthand information. Company called MD Systems from Zurich, they, I think they have quite a big website, media website on D8. I'm not sure, but I suspect since it's Switzerland and they have three languages, it might be that it's multilingual, but I'm not sure. You can ask Berdir, I think Sasha Berdir, he's in Barcelona, so I can ask him. Great, thank you. Great, and whoever, I'll talk to both of you guys then because I'm writing a Drupal 8 multilingual book and I was waiting on the status of media to tie that in. So this is perfect, thank you. So it probably comes down to the individual components. I'm not sure about file entity because I didn't use it much yet, but media entity basically does everything that should be done to be multilingual friendly. So you should have multilingual media entities and it's probably the same with file entity. So anything else? Okay, then thank you everyone and enjoy. Do you want to ask a question? Yeah, sure. With the framework as you've got it at the moment, is there any kind of way that on an instance basis you can kind of override metadata for media, so you've got say an image and you've got out and title tags as metadata and that gets reused every time you reuse that image. But then you want to say in this one place, I want to use that same image, but with different metadata, is that, does that kind of work within the new framework? So we don't have any special solution for that, but one way you could approach this already is let's say when you have media entity, which represents a local file, local image, it basically uses an image field on the media entity, which essentially means that you are referencing to a file, core file, which if you enable file entity module will be fieldable. So you could let's say add this metadata on this deepest level of a file and then create new instance of media entity every time when you use it and override metadata there. So that could be possible. And I think for this kind of use case, you probably need an intermediate entity every time because otherwise I didn't see any solution that would give you this capability without that at least something that would be implemented in a sensible way. And also we have entity API in core and it's very, very powerful, so we should be using it. So yeah, I think have an intermediate entity, whether it being media entity or anything else, you could also do a two step file entity too probably. So something like that. You have tools that can be used to build that, there is not a one click enable solution for that, definitely. I heard talk once about a migration path from Skald to Drupal 8 Media, what's the status on that? There's none. At least that I would know about, yeah. Okay, so no plans? There are plans to implement that certainly but there is nobody working on this at the moment as far as I know. But like people behind Skald, like open web solutions from Paris, they were represented on this discussion at NICE camp last year. So all these plan, how to approach media in the eighth was also based on feedback that they provided based on their experience with Skald. So, and media entity is actually inspired by Skald. Like it works in a very similar way than ATOM entities in Skald do. It's just extracted and lives in a separate module. So I would say that at some point, when somebody will need it, will write migration path from ATOM entities in the seven to media entity in the eight. And like it really comes down to the, everyone works on things that they need. So I can focus on things that my company needs for their own product and other people can focus on things that they need. There are some people that do something just purely out of passion but that won't sustain development of solution of that scale forever. So it comes down to if you need something and it's not there yet, you probably have to implement it. Or if you're lucky, you find one or two other people that need roughly the same thing and then you have to contribute it back. We don't have one big commercial entity behind media initiative. Like we have commerce guys behind triple commerce. So we don't have somebody who is funding development. So I guess this is the only way. And that's why I think communication is one of the most important thing for our initiative because if we won't be communicating enough, people won't be following like common plan when working or on their own solutions. That's why I think this will become even more important when a lot of new D8 projects will appear. Okay, you deserve your coffee. Thank you.