The radical, fundamental principles of freedom, rational self-interest, and individual rights. This is The Iran Brookshow. All right everybody, welcome to Iran Brookshow on this 23rd of January. January is starting to wind down. Hope everybody had a fantastic weekend, ready for an exciting week. And we are back with the daily Iran Brookshow news roundups. I'll be doing them as often as I can this week. I will be traveling. I will be in Austin leaving on Wednesday, so Wednesday, Thursday, Friday, Saturday, Sunday. I'll be in Austin. I'll try to do as many shows from Austin as I can. Probably early in the morning, 8 o'clock central time will probably be the time we'll see. How many of those I can get done, but we will try to do them on as many days as possible. Also, on Thursday night, Thursday night, my show, instead of a show, will be live streaming my talk from the University of Texas, on the Salem Center at the University of Texas, my talk on freedom in the world with the focus on Iran and China. So stay tuned for that. It'll be on my channel as well as the Salem Center channel. All right, let's jump in. No, no, Lex interview. And somebody's asking about my essay on Skeptic Magazine with Elon. It was published. The problem is to see it, you have to have a subscription. The essay will be published by the Ironman Institute in the next few weeks. So you will be able to see the essay. But the essay in Skeptic Magazine, you have to have a subscription for Skeptic Magazine. Yes, so thank you for the support. Really appreciate it. All right, let's jump in. I want to talk about tanks. We haven't talked about tanks in a long time. Let's talk about tanks. The Ukrainians desperately asking for tanks to be supplied to them by the Europeans or the Americans. But I think primarily the Europeans, the Germans, the British have already committed to giving the Ukrainians some challenger tanks, some of the British tanks. But what the Ukrainians really want and what is most easy to supply them with are the Leopard 2 German tanks, easily the top five tanks in the world, maybe top two or three tanks in the world. They've also asked for Abrams tanks in the United States. Abrams tanks in the United States is going to be a hard sell, I think primarily, because the Abrams tanks is not ideal for the terrain in Ukraine. It is a much heavier tank than either the British or the German tank. It's not really built funnily enough for the terrain of Eastern Europe, particularly not with the mud and the freeze. It's heavier, it's a robust tank, it's a fast tank, it's maybe the best tank in the world. But it is not ideal plus. Very few NATO countries have Abrams. So maintenance, training, parts, all going to be very difficult to supply. They'd have to be supplied from the United States or from the Middle East. Much more difficult to supply all that. Israel has Abrams tanks. Israel, indeed, has a lot of the supplies the United States is providing to the Ukrainians. It's coming from storage facilities the U.S. has in Israel and they're moving from Israel. So, you know, I expect, so the advantage of the Leopard tank is, the German tank, is that the tank is available throughout NATO countries, throughout Eastern Europe. It is primarily the Poles have quite a few Leopard tanks. It is the main tank, if you will, in the front line with Russia. It is a tank that's going to be easy to supply. Supply chains from Germany or from Poland are short. It is a tank that is going to be easy to train Ukrainians on because, again, it's close. All the countries that use it, the prevalence of it is used. It's right there, everything is close by. So the Leopard tank is the tank that the Ukrainians, I think, prefer and would like. They were hoping to get the United States to agree to supply Ibram's tanks and that would put pressure on the Germans to supply the Leopard tank, but the Leopard tank is really the one they actually want. It is going to be, the United States has turned down the request to provide the Ibram's for the reasons I think I stated, just a logistical nightmare that's involved and the fact that it's not ideal for the Ukrainians. The Germans so far have turned down the Ukrainians for the delivery of tanks. The Poles want to give the Ukrainians the Leopard tank, but they need permission, since they bought it from the Germans, they need permission from the Germans in order to do that because part of their purchase agreement is that they do not supply it to a third party. They don't supply it to a third party unless they get permission from Germany. So now it looks like over the weekend, it looks like the Germans will be providing the Poles with permission. So it does look like Ukraine will get Leopard tanks, they're also going to get some challenging tanks from the UK. Let me just be clear, the Russians don't have, well, we'll get to what the Russians have, but these tanks are far, far, far superior to anything the Russians are deploying in the field. They're far superior to the T-72s, the T-80s, and the T-90s that the Russians have in Ukraine. They're faster, they are more powerful, and importantly, if you're a soldier, they protect the crew much, much better than anything the Russians, the Russians are known for not protecting their own crews. These tanks, to a large extent, game changes. Those who believe the tanks are irrelevant in a modern matter field don't know what they're talking about. Tanks are the ones that open up paths of advance, the infantry comes in afterwards. You need this kind of heavy artillery, heavy weaponry in order to take land and to dominate a field. These tanks, again, protect their crews against anti-tank missiles, but they also, because they're fast, because they were protected, and because they have such immense firepower, they're going to be hard to hit and they're going to be hard to deal with. The Russians do not have the same anti-tank capabilities that the Ukrainians had at the beginning of the war, because they were using Western technology. The Russians just don't have technology that matches Western technology when it comes to armaments. So Western tanks, in the hands of Ukraine, will make a massive difference come spring or late winter when I expect the Russians to try to do a push of the Ukrainians to initiate a significant push into land occupied by the Russians. There is one other angle to this story, and that other angle to the story is the missing Russian tank. The Russians in 2015 unveiled a brand new next generation tank called the T-14. The T-14 Armada was supposed to be a tank that matches anything the West has. It was filled with technology. It was super advanced. It actually had all the kind of shielding for crews, for crew survivability. It was a tank that was supposed to match up with the Abrams, with the Israeli Makava, with the German Leopard and the British Challenger. And it was unveiled in 2015, and one of the surprises, I guess for many, was the fact that it has not made an appearance yet in Ukraine. It has not shown up, and the question is why? Where the hell is this tank, next generation tank that could make a big difference for the Russians in Ukraine? Well, it turns out that the tank, the T-14, I mean, it doesn't really exist. There are probably 20 of them in existence in the world. Who knows exactly the number? The technology has never really worked. They are still in development. The advanced technology within the tank, the tank that makes them the equal of the Western tanks, requires advanced chips. Microprocessors, you remember those microprocessors? Microprocessors that the Russians cannot and do not know how to produce. Microprocessors that they would need to buy from the West, and the West is embargoing them. This is a tank that is great to bring out during military marches on May 1 celebrations. It is a tank that is great for Russia files to claim that the Russians have as good a technology advance as the United States and Western Europe. But it is a tank that is missing in action when it comes to an actual war. Or just like, in a sense, the Su-57, the most advanced Russian plane that is just not in the skies of Ukraine. You know, Russian technology is just not up to speed. Russian manufacturing is not what it used to do, what it used to be. It is much easier for the Russians to be manufacturing old tanks right now than this T-14, this modern new tank. Electronics don't work and electronics require Western chips, which they don't have. I thought that was an interesting aspect of this. Again, emphasizing this idea that Russia has been in big trouble, Russia does not, in terms of conventional weapons systems, does not present a threat at all to the West. It's a different story when it comes to nukes. But in terms of conventional, the Russians present no threat to the West. Indeed, if they can't beat Ukraine, NATO would have a field day with them and could crush them in days. You know, another reason, I mentioned the Su-57s and not wanting to bring them out partially because they didn't want any of them down. It would be very difficult then to sell them or to claim to have a fifth generation airplane. I think to some extent they haven't got even the one or two T-14s that might be serviceable because, you know, they'd hate to see one of those in fire and flames. Who are they going to sell them to in the future if that happens? You know, the only people buying Russian equipment right now are countries that can't buy it from anybody else. My guess would be the North Koreans. We know Iran is trying to get Su-57s they want. Or maybe they already have S-400 anti-airplane missiles and they're probably in line to get the tanks. Syria, countries that can't buy weapons from anybody else. Those are the countries buying weapons from the Russians. It's all they got. Alright, so tanks still can be a game-changer in this war. But if they are, it's probably on the western side where the Ukrainians haven't deployed. Ukrainians, by the way, have been fighting this war with the same tanks the Russians have been fighting this war. T-62s, T-72s, maybe they've captured some T-80s, T-90s that they've been fighting with. But the Ukrainians have no advanced tanks. They have the same tanks as the Russians do. Once they get western tanks, they outmatch the Russians even though they have fewer tanks. Each one of these western tanks is so much better than anything the Russians can deploy to the field that it is, to some extent, no context. Is the picture a little crooked? Let me know if you think the picture's a little crooked. I think the camera's a little crooked. I'm going to have to work on that. Just to remind you, we are doing these daily shows on the assumption that you value them and on the assumption that they pay for themselves. 250 is the target for each one of these morning shows. We've hit almost all shows, but I'm just reminding you for those of you. So again, if everybody puts in chips in, $2.50 right now, we're easily there. So everybody watching live right now and people are coming in and out. All right. Document gate. I don't know what this will be called in the end. But every time somebody goes wandering into one of President Biden's offices or homes, they find more classified documents. It's really pretty amazing. There's supposed to be rules and regulations that prescribe what documents you can have and what documents you can't. Clearly, Trump and Biden walked away from the White House, Biden when he was Vice President, Trump when he was President, with a stash of documents that they had no authority, right? Legitimacy and taking. They're all over the place, it turns out. And with Trump repeated requests to deliver them to National Archives failed, you know, he handed over some, didn't hand over others. With Biden, it's just like almost like become a joke every time accidentally. They go into some way, they find more. The Justice Department went into his home this last time. He is cooperating. I don't see what choice he has. So the FBI didn't get a warrant and stormed the place, but they did go in and they spent something like 13 hours in his home digging through everything and they found more documents. I wonder, I wonder what if, you know, I wonder if there's a little fire going, the fireplace is going strong in Obama's home and in the Bush home. And document burning is going on because anybody want to bet that if we actually went into Obama or Bush's homes, we'd find more classified documents? I mean, think about it.  These are the bastards that have find American banks. I'm just giving this example because it's an example top of my mind, but we could use a million examples like this. These are the bastards. They find some of the America's largest banks, most successful banks, hundreds of millions of dollars. Why? Because staff at the bank was using their private messaging to communicate with one another when they were supposed to use only corporate email or Slack or teams or whatever it is that they're using, which by the way, the company has by law supposed to preserve all communications, I don't know, for five years or whatever, so the regulators can come in at any time and scan them. Now, it's not that in the personal messaging that the people communicating about business did. It's not that anything they said was wrong. It's not like they conspired to do something wrong. It's not like they were committing fraud. It's not like they violated anything. It's just that they were using the wrong messaging app according to the regulators and as a consequence, the company had to pay hundreds of millions of dollars. How many people in jail because they filled out the wrong regulatory forms or did it wrong? How many millions and millions and millions of dollars of people paid the IRS because they have not filled out their tax forms right? And these guys, like everybody else, there's so many rules and regulations, there's so many classified documents, there's so many nonsense that they took some documents home. And nothing's gonna happen to them, but if we get caught, if we get caught with anything, the whole weight of the US government falls upon us. I mean, it's just outrageous the things that politicians get away with that nobody seems to care. I mean, the thing about it at the end of the day is, I mean, the media cares a lot about this primarily because they feel like they were betrayed by Biden because they went all out to attack Trump. And now they feel like they're betrayed by Biden because Biden was doing the same thing. But nobody cares. Do you think anybody cares about this stuff?  No, the Democrats care that Biden had? No, not at the end of the day. Nobody cares. And what is the punishment gonna be? Slap on the wrist?  But you beware if you misread, you know, a paragraph in the thousand page regulatory regime governing a particular activity within your particular business, and you're in big trouble. This is the problem in this country. We have too many rules, too many regulations, too many controls, too much ability of the regulators and the powers to be to decide which ones to enforce and which ones not, which people to go after and which people not to go after. Is it surprising our politicians don't play by the rules? No. It's just disgusting the way we as productive members of society, as business people, as people that actually make the world move forward. It's disgusting how we are all treated and the level controlled imposed on us. You know, these documents risked the national security, the fact that they're sitting in these people's homes probably, how big of a risk, who knows. You know, again, most of them shouldn't even be classified. My guess is 90% of classified documents shouldn't be classified. I've told you before, these are our servants. These are not our masters. They shouldn't be keeping secret from us unless there's a clear national security reason to do so. The problem is today, everything the government does is framed, or not everything, but a big portion of what the government does is framed in terms of national security.  TikTok, national security threat to all of you. I mean, those videos of cats and those videos of, I don't know, people jumping off of cliffs or whatever it is that they do on TikTok.  So everything is a national security threat. Everything is a national security threat. And therefore, everything is accessible to government and everything is possible for them to come after us with everything. All right. Debt ceiling, just quickly on the debt ceiling, you know, we're going to be talking about this more because this is going to keep coming up. And we'll keep coming back to this over and over and over and over again, I guess, because it is a story that is going to play out from now until May. So the government has approved to issue a particular amount of debt, a particular number, a dollar amount of bonds that it issues. The problem is that the United States government has since, basically since 2000, been running at the deficit every single year. And the deficits have only grown and they're massive. And what that means is that the government has to borrow every year, it has to borrow more. So the debt has to grow so that the government can finance its own activity. That means that given that there is a, that is by legislation a ceiling on how much they can raise, they have to keep coming back to Congress to ask them to raise the amount of debt they can actually borrow, the amount of bonds they can actually take. Now, a big chunk of the borrowing that the government does on a regular basis is to pay, to pay off the bondholders whose bonds are expiring in any given month and to pay interest on the bonds that are actually outstanding right now. And this is, this is what constitutes default. What constitutes default is when the United States government cannot pay interest anymore on its debt. And the reason it cannot pay interest anymore on its debt is because it has to take on debt in order to pay the interest payments. Now it could instead stop paying social security payments, stop paying Medicare payments, it could stop paying the military, it could stop paying redistributing wealth. It could do a lot of things and continue to pay off the, to pay interest on the debt. But, you know, it's politically disastrous to stop paying social security. It's politically disastrous to shut down the government. They will try and they will try, you know, and if the Republicans don't actually vote to raise the debt limit, then the government might shut down for a period. And when it's shut down, it doesn't pay wages. It doesn't pay other things. And as a consequence, it can't print more because the government doesn't directly print money. The Federal Reserve prints the money. And the only way the government gets the money is by issuing debt that the Federal Reserve buys. And when the Federal, and that is debt that is added to the debt ceiling. So the debt is increasing. So the way we've created the mechanism by which we've created in this country is that the government doesn't directly print money. The government has the Federal Reserve print money and it issues debt, which the Federal Reserve buys, thus giving the government the new money. So still need to raise the debt ceiling in order to make this happen. So Congress, the way the law is written today, Congress keeps having to ratchet up the debt ceiling so that the government can continue to function. Now, the idea is that if the government doesn't function, if we have a shutdown, if the government doesn't send out checks, if the government doesn't pay its employees, if the government doesn't do its thing, then the economy will go into a tailspin and the world will end because we know that our lives depends completely on the government itself. Every time the government shuts down, it doesn't seem like the world ends at all. But it is true that a government default on the debt would make it very difficult for the government in the future to raise debt. People would now not view US government bonds as risk-free. They would actually view them as risky. That would mean they would charge a higher interest rate in order to buy those debts. That means the government would be able to raise less money and the money it raised would be more costly. So there's this dance that happens, I think every year, basically where Congress has to raise the debt ceiling. And the administration has to ask. Now, when Republicans control the House, Senate and White House, they just raise the debt ceiling. No problem. If Trump wants to spend money, cool, raise the debt ceiling and then spend as much money as you want. God forbid we Republicans stop it from doing that. We don't believe the deficits matter anymore. But when a Democrat is in the White House, Republicans suddenly discover that debt is a bad thing. They suddenly discover their fiscal conservatism. They suddenly discover that maybe it's time to restrain government. I often say, I've often often often said that Republicans are much better opposition party than they are a party to govern. And then they use raising the debt ceiling. We'll see what this Congress does. But the idea is with Obama what they did in 2011 I think it was. What they did was they used the debt ceiling raise to get concessions from the administration. And the primary concession was to cut spending, or at least to reduce the growth rate of spending. And that's what Republicans claim that they want to do this time. They want to reduce spending. Now we will see when the rubber hits the road, if that's actually what they're going to assist on, I don't know if they're going to expand this into all the other kind of claims and demands that they have of the Biden administration. But if Republicans can actually get the Biden administration to agree to restrict the growth in spending, in exchange for raising the debt ceiling, that will be a small but significant achievement. It actually has positive impacts on inflation because it suggests that debt is not going to grow quite as high as one would expect it. And it generally will have a positive impact on the economy more broadly. This is counted to Keynesian and the New Keynesians who would like to see the government spend as much money as they can. Or the modern monetary theory is just one government to spend, spend, spend. We've seen the inflation consequence of that. So we can hope that there's enough rationality within the Republican caucus to insist and that the Biden administration will ultimately compromise on some kind of limitation on spending. That'll be truly, that'll be the best outcome possible. So I actually like this idea of the debt ceiling because it forces people to have to raise, it forces Congress to have to raise it. And it gives Congress some power over, you know, since they won't discipline themselves, some, you know, forceful mechanism by which to force the executive branch to be disciplined. We will see, we will see this. It would be ideal, it would be ideal if Republicans when they controlled all houses and executive branch actually restrained spending significantly, reduced spending dramatically, and actually got this budget into surplus. That would be cool. That would be very, very cool. But, you know, chances of that happening or what, one in a million. All right, we got over 100 people watching live right now. Don't forget to like the show before you leave, please. That really helps with the algorithms that helps spending the show and getting it out there. So please do that. Also, we're about $144 short. So if everybody in the chat did a buck 20, a buck 30, a buck 50, we would get to $100. So, to our goal of $250. So please consider supporting the Unbook show with a small contribution on the super chat, $1, $2, $3, $4, $5, $100. All of them make a difference and all of them help us get to our goal. So please use that feature. Okay, last quick item and then we'll go to the super chat questions. You can also ask a question with $1, $2, whatever. So please, please do so. Let's see, tech layoffs. Tech companies are laying off significant numbers of people.  They haven't laid off anybody since really 2001. Google, Facebook, Microsoft. The only big tech company not laying anybody off is Apple. You know, all these stocks have been batted last year in the stock market. All valuations have come down dramatically over the last year from the highs at the end of 2021. You know, it is really, really interesting. Tech companies dominated the 20 teens. The largest companies in the United States. Some of the largest companies in the world were America's big tech companies. These companies basically spent the last 12 years building the Internet as we know it, building our tools to use the Internet as we know it. They have globalized the Internet. They have gotten a vast majority of the world's population onto the Internet in the United States. They have brought Internet to use to above normal. They have built it out. They have created the operating system, Microsoft, Apple. They have created the tools, the iPhone. And they have created the killer apps, the social media, that have made social media and shopping online, which is Amazon, which has made the Internet useful for almost the entire population. This is what has driven up the valuations, which are justified. They have made an enormous amount of money. All of these companies are immensely profitable, with the possible exception of Amazon. They are hugely profitable. They must have, of course, built the infrastructure in terms of cloud computing to make the Internet ubiquitous and everywhere and accessible to everyone, everywhere at all times of day, all times of day in any place in the world, or in almost every place in the world. So these companies benefited enormously by creating the Internet as we know it. But they have reached, in a sense, they have reached some kind of level of saturation. We're already on the Internet. We're already doing the main things one does on the Internet. Growth from here on is a challenge. It's not obvious where growth comes from. And this, I think, is what has really sunk in in the 2022 Internet, or tech kind of correction, as you might call it. Facebook is as big. It could grow somewhat. But how much bigger could it grow? The same with all of these. Everybody's already using Microsoft software. Everybody's using, everybody has an iPhone. Everybody's using Apple. Yes, there's growth potential, but it's restrained. Is there a new killer app? Is there a new killer product? Is Apple going to release something that is going to so increase sales that it'll compete with the iPhone, ultimately, as the dominant? Nobody can see this. Nobody can see this as anything dominating, right? So what you've got is, to a large extent, these large tech companies hitting their capacity. Again, not to say they're not going to be profitable in the future, but it also suggests that scale has its challenges. Growing so big and dominant is challenging. The fact is, over the last 10 years, 12 years, there has been no company that's gone public that has become a dominant player in the Internet with the exception of Facebook. All the other big companies were around before that. But they're all big now. Difficult maybe? More difficult to innovate? More difficult now? They've spent the last 10 years not only innovating to the point that they're able to, but also buying all the innovative companies. What happens to them from now on are these layoffs a sign that maybe there's competition on the horizon? All of Congress's obsession with antitrust and breaking up big tech is VR going to be the next big thing? I'm skeptical about VR's ability. I mean, it'll be profitable, but is it going to be the big thing? I doubt it. Anyway, it's interesting. This is something to watch. Is there going to be a turnover? Are we going to see more money flowing into... I mean, already a huge amount of money is flowing into startups, but are some of these startups going to come out and really challenge any of these companies? So that is, I think, the big question mark. It is interesting. Also, a lot of these software engineers that have been laid off, I don't know if you've seen charts of what software engineers make these days, but opening salaries in Facebook and Amazon and many of these companies start out opening just out of college at close to $200,000. Senior engineers can easily make over a million dollars a year, not just in Amazon, Google, Facebook, in many of these companies. A lot of these people are being laid off. A lot of people staying in these companies now realize they can be laid off. There is that possibility. A lot of these people are going to find jobs. There's no shortage of jobs. There are plenty of jobs. But these jobs are not going to pay as well. The whole industry is going through, I think, a shakeout. I think 2022 started it. 2023 we'll see an acceleration of it. It's going to be really interesting to see what happens in tech in 2024-25 in terms of the dominant players, in terms of the upcoming companies and where many of these engineers land up. Automobile companies, financial institutions, even construction companies all looking for software engineers all trying to gain programmers. They've been priced out of the market so far. Now they'll be able to hire these people at lower wages than these people have had in the past. But still, they'll still be making a lot of money. Don't worry about them. But it's going to be a real shift, I think, in where technology is heading. And I, for one, am curious on where this all ends up. I don't think that the big tech success is just a monetary phenomena. It's just a matter of what a bubble. I don't think these were particularly bubbly stocks. I think the real bubble was in the medium and small technology stocks, Zoom, for example, and others. I think that's where the COVID bubble or the monetary policy bubble was. These companies are real companies that create real products that change lives and that add real value. They will continue to do so in their next decade. But they're not going to be able to grow as fast, partially because of sheer size. And they are not going to be able to be, I think, as profitable in the past and you will see a new generation rising up in the next 10 years to challenge their status. Anyway, it's going to be interesting. It's going to be fun as markets always are. All right. Thank you, Frederick. Thank you, Catherine. Thank you, Rand. Really appreciate that. $50. Thank you, Kevin. And thank you, Vladimir and Alan and Colleen and Iron Mercad. I appreciate you guys' support. Let's see. So we've got Super Chat. We're like 66 bucks short. We have 114 people watching 50 cents, pretty much where everybody gets us over their hurdles. So if some of you put in two bucks, we should be, you know, 30 of you put in two bucks were done. So maybe there are 30 people out of 114 watching who are willing to contribute two bucks, three bucks to the Iran Book Show, two or three bucks to Iran Book Show to get us over the hurdle. All right, Shay, if NATO countries are going to spend so much on Ukraine anyway, wouldn't it be cheaper in dollars and lives to just crush Russia directly? No, because the real worry is if the NATO gets involved directly with Russia, that Russia does launch nuclear weapons. So if Russia feels threatened by all of NATO and if Russian feels like, thinks that it is at war with the West, with the entire West, it might escalate to nukes. Look, the Germans are so afraid right now, they're afraid to sell tanks, to give tanks to Ukrainians because they're afraid of Russian escalation. Now, every step of the way from the beginning, they've been afraid of escalation. Everybody's been afraid of escalation. Oh, we can't give them this. They'll escalate. We can't do this. They'll escalate. We can't support this. They'll escalate. And so far, Russia has not escalated. It's not capable of escalating without using nukes. And I don't think Russia wants to use nukes. I think Russia is afraid of using nukes for a variety of reasons which I've talked about before. But look, in a different world, Russia would have, you know, a robust NATO that actually stood, was willing to stand up to Russia. Russia would have never invaded Ukraine. You know, but that is not the world in which we live. Again, I don't believe the United States should be part of NATO. I think NATO should be a defense organization for Europe. Europe is the one facing the threat, not the United States. A robust European NATO, Russia would have never invaded Ukraine. They would have been too afraid. And if they had, they would have been crushed very quickly. But sure, it's much cheaper for NATO to take care of it as long as they know and can guarantee the Russians won't use nukes. But I don't think the Russians want to use nukes, but they might have to if they feel like they're coming from Moscow. Andrew Tucker Carlson's conspiracy, the establishment wants to replace Biden with Gavin Newsom and is getting him up to take it forward. I don't know, read the documents. The media is unusually critical. A case of broken clock being right once a day. You know, the media is critical, I think, because the media is upset, because they went all out on the Trump documents and they feel betrayed by Biden. Could it be that the, quote, establishment? I don't believe that. You know, the idea that the establishment is this sophisticated, that they would launch attacks against Trump and Biden on the same issue in order. I don't think it's going to work, A, because the American people don't care about it enough. And second, I don't think this is the problem with conspiracy theories. People are not that sophisticated, and when they are, they're not very good executors and they're not very good keeping secrets and they're not very good at doing this stuff. So I think the probability that this is some conspiracy theory is weak. I'm sure there are a lot of Democrats that are happy about this because they don't want Biden to run and to the extent that this can become something that, you know, prevents Biden from running. It prevents Biden from running. I think a lot of Democrats will be very, very happy. But the establishment is too, look at the establishment's trying to discredit Trump in the eyes of Republicans forever. And by the way, the establishment would love Trump to run. I mean, the best thing that can happen to the establishment is if Trump runs, because Trump is likely to lose. They wouldn't try to stop Trump from being the Republican nominee because pretty much every other Republican can beat a Democrat, but Trump can't, so they would actually try to... So, God, conspiracy theories just don't make sense if you actually trace them through. And this one I don't think is right. Joe says, would active commissioning of odd be a viable way to influence cultural change? Objectives seem to tend to classify and criticize already existing art and trends while wealthy leftists pay for and encourage new modern art. I mean, yes, absolutely. I think encouraging the creation of great, romantic art of art that is truly transformative, but this is the point, has to be good art. So I think commissioning good art, don't commission objectivist art, because there's no such thing as objectivist art. But if try to commission good art, if we can commission good art, build good art, if American corporations created, you know, barred great art and filled like the public spaces with good art, if wealthy individuals barred great romantic art and put it out and supported good artists, I think that would change the world. I think that would change the world. So yes, absolutely, we should be commissioning art, good art and displaying it so that the world can see what great romantic art looks like and what a pursuit of values it looks like. All right, guys, we're $46 short. We should be able to make $46. That's basically 30 cents from everybody listening right now. So I hope in the next three minutes we get it because I only have four quick questions. Ian says, do you think Silicon Valley, San Francisco is the new Detroit? No, I don't. Every indication is, for example, in San Francisco, I just read a story this weekend that people are moving back into San Francisco, partially because some of the tech companies are now requiring people to come into the office, partially because San Francisco, in spite of everything, and I keep telling you this about California, is an amazing place to live. Silicon Valley, I don't see property values in Silicon Valley plummeting because they still demand. Silicon Valley is still where the venture capital is. It's still where the network effect exists in terms of tech. It's still where everybody in the tech world at least needs an office, if not a major office. Silicon Valley and San Francisco are not going anywhere. They will take a hit. San Francisco has shrunk quite a bit since COVID, but it's supposedly growing again. It's still true. The immigrants want to go there. The people from other parts of the country want to go there to Silicon Valley, so no. I don't see that. Maybe in 30, 40, 50 years, if you think about how many people the big tech is laying off as compared to how many people they're employing, it's still the numbers are small. And remember, there's a massive shortage of engineers in this country. So those people are all going to find jobs. They will find jobs. They won't find maybe as lucrative of jobs. And they won't find jobs in this particular, you know, in the kind of companies that they have worked with. All right. I guess you guys don't want to help me make the 250 today. All right. Brie, last three questions. Brie, I have to report the comedy flow survey. It is part of the GDP. This is at the bottom of email. Your response is required by law. Yes, absolutely. I mean, there's a million things you have to do that are required by law that if you don't, there are real consequences unless you're somehow in the political class and you can walk away with classified documents and you can take them home and you can show them to your friends and you can show them off to whoever.  Michael says, why have most philosophers in history been anxious and neurotic about existence? I don't know. I really don't know why that is. Maybe it's the fact that they're neurotic and so on that leads them towards a profession like philosophy where they're not as penalized for being neurotic. Maybe the psychological problems lead them in that direction but I don't know. I'd just be speculating. Adam Campbell says, cowboys lose, eagles wins. What a great Monday. Good for you, Adam. I'm glad your team's won. I guess the 49ers won. There's Silicon Valley again. I guess everybody hates the 49ers because of the Silicon Valley company. Yeah, glad you had a good sports weekend. That's always good. All right, with $30 short, Jeffy says, enjoying Fowler season four. Yeah, I am too. Massive holes in the story.   Anyway, that is my main criticism so far but it's still edge of the seat, exciting, thrilling. Fowler is like, no other show you'll watch anyway. It's nonstop action and intensity and it might be a little bit of 24 but in some ways much more realistic, much more real life, much more gritty but as intense and as exciting and as you have to binge watch it, like we're staying up until midnight every night because until we literally fall off our chairs, can't watch any more of it, we keep watching. So I think by the time I go to Austin on Wednesday, I'll have finished season four. But it is, it's very good. I encourage everybody to watch Fowler. There are four seasons now, all on Netflix, great binge watch television. All right, last question with $13 to go. All right, there we go. John has just solved that problem. Top three investing books for the average Joe. God, I've done this before. I don't know. I mean, I highly recommend, even though I don't agree with some of the stuff in it, I definitely agree with the investment recommendations. I highly recommend random walk down Wall Street. What else? I'm trying to look, you know, you guys need to stop asking me these kind of questions because I don't retain them. But you know, I will try to get back to you with some others. God, I can't remember. Yeah, anything by, you know, by the guy who, anything that advocates for the average Joe that you shouldn't day trade. Everything that advocates for buying a well-diversified portfolio and sitting on it. Don't day trade because you can't beat the pros. They're pros for a reason, like I don't go on a basketball court. I try to play with LeBron James. Don't go into the market and try to play with, play with the Warren Buffets of the world and the J.P. Mogans of the Goldman Sachs and the Citadels and the rest of the, kind of the top of the hedge fund industry. You're not going to, you're not going to come out a winner. All right, let's see. John says, my girlfriend recently lost someone close to her and knowing I'm an atheist asked me what's wrong with having an illusion that someday I'll be able to see my loved ones again. I didn't try to argue, but I'm curious on your take. Well, because any illusion is fundamentally corrupting to your commitment to reality, commitment to reason, commitment to logic, commitment to facts. It basically says, when I feel like it, when I feel strongly enough about it, I'm willing to put aside facts, put aside logic, put aside reason and engage in delusion, engage in whim and engage in emotionalism. And if you put your consciousness, if you put your mind on that kind of standard, on that kind of, you know, basically set commandment, if you will, then you will screw up in other parts of your life. You will apply that to other parts of your life to your own detriment. You can't be picky and choosy about these things. You're either committed to reason or you're not. People who are halfway or a little bit become more. And ultimately, ultimately, what happens is that you just don't live as good of a life as you could otherwise. You're giving up, you're destroying your capacity to live. Religion isn't serious, religion is destructive. Religion is something that undermines your ability to be happy, your ability to have self-esteem and your ability to actually take control of your life and make it the best possible life that you can live.  That's just a fact of reality. It's an absolute, not because it's a commandment, it's an absolute because that's the way reality works. All right, everybody, thank you. Have a great rest of your week. I will see you all again tomorrow at the same time, same place. Thank you all for getting us to the goal. Hopefully, we can keep this up. And those of you who would like to support the show on a regular basis, monthly ideally, you can do so by Patreon, subscribe star, or you're on bookshow.com slash support.


Hello, this is Laptop Media, and today, we will show you how to open the AMD version of the Huawei Matebook 13 2020 and what's inside of it. Okay, Huawei, we haven't played this game with you before, but there is a first time for everything, right? Like HP loves to do, there are four hidden Philips head screws, in addition to the six Torx screws. In order to find them, grab your plastic pry tool and remove all four rubber feet. After you undo all of the screws, just pry the panel away. Please remember, it would be of great help to us if you just hit the like button and subscribe to our channel. That would motivate us to make even more and better videos for you. If we have to be honest, we are very pleasantly surprised by Huawei's approach to cooling so far. This notebook features two pretty thick heat pipes, as well as two fans, blowing all of the heat away. Sadly, but unsurprisingly, you won't be able to upgrade your memory. All you can do is pick the largest 16GB version upon purchase. On the other side, you have one M.2 PCI-EX4 slot. Since there is not much space left inside, Huawei only managed to put a 41.8Wh battery. If you'd like to see more disassembly videos of the latest notebooks we would highly appreciate if you hit the like button and subscribe to the channel.


Good morning, ladies and gentlemen. How's everyone doing today? My name is Ryan Yomoto. I'm thrilled to be here with you today. I am the noon and 5 p.m. anchor here at Channel 5. I started in January. A bit of a homecoming for me. I was working in Seattle before, but got to come home here.


And for my Ethiopian Prime Minister and the Board of the Chair of the Alliance for Green Revolution in Africa, A.G.R.A., Halle Miriam Dal Desalene has arrived in Nigeria on a four-day visit to engage leaders in conversations around systems transformation. He will meet ex-President Toulou Chacon Bastignon, the Minister of Finance Zainab Ahmed, Minister of Agriculture and Rural Development Mohamed Nanunu and Kaduna State Governor Nasser El-Rufai. The A.G.R.A. Board Chair is also expected to use the opportunity to formally invite Nigeria to the 2021 summit, which takes place in Nairobi, Kenya on September 7. Before leaving Nigeria, he would also meet with key officials of the A.G.R.A.'s partner organizations to further and, of course, discuss on how to support the government's strategic goals, including those of hunger and increasing incomes in the country's smallholder farming households. The Strip to Nigeria proceeds the United Nations food systems to be held in New York in September. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


ॐ ू T ौ T ौN ौ T ॉ T ौ T ौ T ौ T ौ T ौ T ौ T ौ T T T T T T T T T T T T T ौT ौT ौT ौT ौT ौT ौT ौT ौT ौT ौT so ौT so ौT so ौT ौT ौT ौT BOOT, regardless ौT ौ T ौ Tgef ौT ौT ौT ौT BOOT, I continue to等 with this quote from many books i try to put a simple Cheers ौal । । । । । । । m8 । । m8 ।  wars toon ,  oppress my channel уд 黑balam Julius                         ,         , , , . , , ,   , , ,  , , , , , , ,, , ,, . ,   ,   ,  ,  ,  ,    , , , , て ,     ,   , , , , , , , , to ,  , , , , , , ,, , , , , , , , , . ڏ Broever, ڈeneเราudoaste kachakal. bestimm ABS Definitely Wanted to invite ڈene  Ain As', ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene ڈene In attain industry ఇంది ది ఆతూuem కోయ povo ళ్పాాబ్నుతి. dress నోలినూతి. ఈ్త deityని ahlake భఁ.  భంమ నట ね. బ� Recently two ay two gaurda and wild Dalini to Gu cra Fa ar Ṭἅ朋友 mea kaipang, Ṭἅ house side kaipang soupa that going with him in Caroelada when he doesn't help themLEO in Faridakottuga neither one or any one everybody explained that they love me Ṭἅ new business for the second time and whether to ∠ nogm Breakers coming in and more ṭ paired that with Prince, ṭ the KShánw晍 The KShāhna was uploading with them Ṭ gSH Editor But there was comments including some people from ṭher  fragrht thatidabih android rokhand koseshki thi rhin... poonakisana 800 principal hettoان nene wajesh ikisana ng bir.. houses levels hanger jans. s Mem نСТregierung größten fluor Astronomal ndalningen ndana haq  Gefühl  духов  isz shadow   right believe all right  voices inall al rams ivaige target ....  않았  idea Me itikon  intermediate gunt Defrents لیکن разработ लब यह यह आपी उली सअम्योंगे


I simply cannot fight the urge anymore. Oh, I am so excited about this. I am just literally dyeing my hair red. Yes! Now let's go! Your hair's so long. And she's using X-MODO. It was super red. Hell yeah. I was pretty startled by the color. Not gonna lie, it's a lot brighter than I thought it would be. Yeah it is, it's super red.  It's gonna look so good. I'm so-


Hi, this is exciting.  My name is Jeff Chowen. This is an introduction to operating systems. I'm super excited to be here today with you guys. This room's a good size for this class. Hopefully it'll be this full every day. Can people in the back hear me? Awesome, OK. So if you can't hear me later and my lips are moving, just shout, and I'll try to speak up a little bit. But I don't want to use a mic in this room. So today we're going to get started. I hope you guys will have a great semester. I love teaching this class. I love exposing people to this material. I think we have a fantastic semester ahead of you. Today is not particularly interesting. We're going to talk about boring stuff. We're going to talk about administrative trivia. We're going to talk about a general overview of the class and some course policies. The most important thing that we're going to do today, however, is introduce the staff. So that's coming right up. But before we get there, let me tell you a little bit about why I'm here. We'll find out while you guys are here in a minute. The reason I'm teaching this class is essentially because I took this class. So about, I don't know, I didn't count the years this year. I'm getting old enough where that's starting to get slightly depressing. So at some point in the past, I took this class. It wasn't called 421, 520. It was called something else. But it was these assignments. It was at a different place, a different time. And this is what really got me hooked on computer systems. It got me hooked on computer operating systems. At that point, I was studying physics. That was a mistake. And this course really helped me steer to the right path. And I discovered through doing these assignments that I really loved building computer systems. And that was the fatal blow that set me on this particular course. So you guys should think about this right now because this class can be transformative and really change your life. It changed my life. And if you don't want to end up like me, you might want to think twice about taking this class. So people who have taken this class have gone on to do other things. And we'll talk a little bit about those people later. But so this class is the reason I'm teaching this class. And that makes me really happy. So OK, so why are people taking this course? We have a big group this year. Somebody volunteer. I know for undergraduates, it's a requirement. It's not required that you take it in the spring of your senior year, though, which you may have mixed feelings about. So for the master's students, undergraduates who are here, why are you taking this class? What do you hope to get out of it? Anybody? Yeah? Learn how an operating system works. Learn how an operating system works. OK, that's good. Someone has read the course description carefully. And we will do that, definitely. I hope that this class is more than that, but we're definitely going to talk about how an operating system works. What else? How about a master's student? There are 80 master's students in this room. Why are you taking this course? Anybody? Apparently, there are 80 shy master's students in this room. I will happily pick on somebody. You're not a master's student. Let's see. Who is a master's student? Raise your hand. There we go. Why are you taking this class? You've heard good reviews. OK, some of those are probably exaggerated. And I just want to warn you that everything we've been doing for the last four years in terms of some of how this course works, we destroyed this year and we're starting over from scratch, so I'll get to that later. But the material is the same. The methods are new. They're going to be better. They may be a little delayed, but we'll get there. Anyway, so OK. So let me introduce you to the course staff because, like I said, this is by far the most important part of today's class. So every year, I feel like the course staff for this class gets better and better and better. And this year is no exception. So we have an awesome group of people. These are people that I think a lot of you guys will develop relationships with during the course of taking this class because they are going to help you. They will guide you. They will commiserate with you. A lot of them have taken the class over the past couple of years. So they have deep, personal, painful, potential wounds from this course that you may reopen. And that may cause them to really stick in there and help you guys out. So essentially, you can divide the course staff roughly into two groups. So we have actual teaching assistants, official teaching assistants. So Jerry's in the back there. Raise your hand, Jerry. Actually, why don't you guys just? Well, I'll have you guys come down later and answer questions. So Jerry's one of our official TAs. Ali is another. Ali, stand up. And Zhu, I don't know if he's here. He was just added. OK. So these are our three official teaching assistants. And these guys are going to teach recitations. And they are going to grade things. They will also help open office hours. But this is sort of their primary responsibility. Happily, we have two other groups of course staff. One are the unofficial teaching assistants. That includes Ye Hong, who's in the back there. Scott, Hasley, Carl, Guru, and Jinghao. So in various capacities, these guys, these are all sort of members of my research group. My group takes teaching this course really seriously. A lot of the people who work with me now as PhD students, I met and sort of developed an interest in computer systems through taking this class. So they're all involved through different capacities. They'll probably see them in office hours. And they're also actively involved in building some of the new shiny tools that we're going to have you guys use this year as part of the course. Everybody took this class in this group. And most of them in the last couple of years, well, I guess everyone took it in the last couple of years because I've only taught it four times. So these guys, again, I mean, they are great. They will be really helpful in terms of understanding the assignments and giving you guys help with that. Finally, last but not least, we have what we refer to as ninjas. So the ninjas here are all undergraduates who took the class last year. And at the risk of violating some sort of the FERPA, or some sort of rule, I'm going to reveal my algorithm for choosing ninjas for this course, which is that I get out the grade book from last year and I sort it by grade and I start at the top and I send emails until I get as many ninjas as I want. And so here are the people we have this year. Dan is Dan here. Sweet. Dan Conway, Gaila. Gaila's right here. Isaac. Ben. I saw Ben, there he is. Mark. And last but not least, Yusuf. They're in alphabetical order. So Yusuf is always in the bottom. So this group is going to be primarily helping out with office hours. They're also, again, helping us with some of the hacking that we're doing this year to improve the course infrastructure. And they will be super helpful. So let's give an early but not premature round of applause to the course staff for all the help. You guys are going to get this semester. Okay, so let's talk about the material in this class a little bit. So an operating system is a computer program. That's the first thing that I want you guys to realize because a lot of what I try to do in this class and in general, I think a great way to approach computer science is just to try to demystify things. So there's nothing special about an operating system. It's a computer program like other computer programs you guys have written before. It consists of instructions that the computer executes. Now it's a special computer program in a lot of ways. It has special responsibilities and you notice a little bit more when things go wrong but it's just a computer program. You're going to be writing computer code this semester that's going to compile down to a binary consisting of execute. Executions that are executed by a processor. So there's nothing special about it but it has a couple of key responsibilities that have a lot to do with how an individual machine performs. So one of the things that it's in charge of doing is multiplexing hardware resources. Does anyone want to take a guess at what that means? Multiplexing hardware resources. Yeah. Okay, so that's a great answer. It's not quite correct though. So we have the idea of multiplexing where, what's your name? Sean has pointed out that multiple hardware devices frequently have to actually contend for other hardware devices, in this case a bus. And I think to some degree at a low level, software that's usually included as part of the operating system is responsible for this. But an operating system when it talks about multiplexing resources, usually means sharing them between multiple programs that are running on the computer that all want to use them and making sure that this can happen safely. So your computer has one, probably a small number of hard drives, only a limited amount of memory, and a small number of processing units, and making the machine go fast and making everything sort of seem to happen smoothly involves making sure that these resources get allocated effectively to all the different things that are running on your computer. The second thing that operating system does, it's not entirely overlapping with the first, is it implements useful abstractions. So a lot of operating system code is dedicated to hiding or somehow improving on the low level hardware realities. So for example, file systems, which we're gonna talk about in the future, are designed to provide an abstraction that you can just make a file grow bigger and smaller as much as you want. When at the end of the day, what's actually being allocated and deallocated are contiguous blocks on disk. So making those look like it's this thing that can grow and shrink and it has a nice name that you can find and things like that. Those are really all abstractions that are not provided by hardware. All the hardware disk does is store chunks of, just store chunks of bytes, that's it. Everything else that you associate with how files work is something that's implemented in software traditionally as part of the operating system. Okay, so I got as I pointed out some of the fact that these are the operating system's responsibilities means that despite the fact that it is just a computer program, it is also important. And the degree to which these things are done well really has a lot to do with how well the machine works. So let's step back a minute here and ask ourselves who cares, right? So this is a course on computer operating systems. Why would we study computer operating systems? So how many of you guys have ever written a line of code that appears in some operating system? Raise your hands. Okay, so that doesn't make the course seem very useful, right? And actually I would also point out if I asked the alumni from this class, I think the number of hands that went up would be about the same actually. So it's not that you guys aren't ready. How many of you regularly in programming languages that use operating system abstractions directly? So how many of you guys have made something that you were actually aware of was a system call? Okay, I've got like three hands up. How many people have even know what a system call is? Okay, still a few of you. Now, here's the thing, that's awesome. The fact that there's so few hands up and so many computer programmers in this room is a sign of progress.  Your life is too short, stop writing C code, okay? Like write in Python or Go or something better. There's so many better languages out there. C is terrible, right? And you're gonna write it all semester awesome, right? So I'm serious, like when you guys are doing things on your own, please don't misunderstand the point of using C in this class. C in this class is appropriate for what we're doing. C is a language that's appropriate for almost nothing anymore, okay? Just stop using it. Again, computers are so, so powerful and we've made so much progress in designing better languages. Stop using these languages, okay? So why are we studying operating systems, right? Why is this course required for the undergraduates and why are so many graduate students willfully subjecting themselves to this completely sort of pointless material, right? You can go your entire life as a computer programmer and not understand exactly how an operating system works and write code that changes the world, solves important problems, makes a lot of money, whatever it is that you wanna do, okay? So here are my reasons, right? The first reason is that on some level, this is truth. This is how the world works. This is how the computers that you guys use work at a low level. And so from a scientific perspective, isn't it interesting to know how things actually work? There's a pleasure to finding out how things work, for real. Despite the fact that that might not actually change how you write your Python code, right? The second reason is that operating systems are everywhere and to some degree, at some point, when you are trying to save the world or make your million dollars or get your startup off the ground or whatever, you may run into limitations of computer systems and the material in this course may come in handy. But this is my favorite reason. My favorite reason is simple, which is that operating systems are examples of mature, elegant, beautiful systems that have been designed and implemented and redesigned and re-implemented and rethought, uh-oh, lights are going off, over decades. So this is kind of the equivalent of studying like the great masters of painting or something like that, right? These are extremely well thought out systems and you can learn a lot about how to build anything from studying really, really good examples of how things are built, right? Okay, so now I've motivated at least the reason why we're gonna study this stuff but a lot of what you're gonna do this semester is actually programming a small instructional operating system, so why bother with that? That's a pain in the neck. You guys are gonna find that out.  Just to satisfy me of all people, right? So the, and I think the reason is, well, I mean, you're gonna learn something from this, trust me, right? These, the operating systems are hard to get right. They stress the value of design. That's one of my favorite things about this class. If you're the type of programmer who just likes to plunge in and let's just create some bugs and then we'll just fix those bugs and that's how I build things. I just, you know, and I, hey, I'm not, don't put that past me. I do that all the time, right? But you have to know when it doesn't work and it doesn't work here, right? If you start off without a plan, you will regret it. And it basically, what you'll end up doing is coming all the way back to the beginning and then making a plan because it's very hard to make forward progress on a big complex system like this without having some idea what you're doing, right? Debugging with printfs is not going to work or not gonna work well. The other reason is these are hard. I'm gonna give you a huge blob of code that you have to, at least to some degree, understand pieces of, augment, and get to do certain things. And this is, to some degree, I think, at least in our program and a lot of computer science programs, not a common thing. You guys are probably used to starting with little bits of skeleton code that some professor gave you and maybe there's 50 lines there and you have to add 10 lines to those 50 lines and then, you know, it works, right? I'm gonna give you like 10,000 lines and you have to add 100 lines in the exact right places in order to get things to work. Actually, you might have to add several thousand lines. So this is kinda fun. Debugging, right? Invariably, the first, you know, the first D, your design phase, is not going to work and you are gonna find strange, unforeseen things that are happening and you're gonna have to find out what's happening and fix them. And that is incredibly hard on an operating system because, to some degree, when you guys have been debugging code in your previous classes, you've been relying on features that the operating system is providing you. Now you're trying to debug the actual operating system, okay, and that introduces a bunch of new complications. Okay, so how the course works. We talk about concepts in class and in recitation, recitation is kind of the meeting point where the conceptual material that we talk about in class, I don't do code in class, right? I don't show you how to do the assignments, we don't go over code together, whatever, right? In the class, we talk about how things are built and why they're built that way and you guys get a chance to build these things yourself and recitations is kind of, again, a mixing ground where those sort of the practical realities of what we're asking you to do come face to face with sort of the concepts that I'm gonna talk about in class, okay? And then you're gonna write a lot of code, right? So my objective is for you, when you're done with this class, this is, again, I'm sorry, this is kind of dull, but I just want you guys to know sort of what my goals are, right? You're gonna understand the abstractions that are provided by modern operating systems. You'll be able to talk about and explain how operating systems multiplex resources because this is the real interesting thing. This is the, these are the ideas that are really, you're gonna carry forward that are gonna help you write better code in the future. You'll be able to have some perspective about how operating systems have evolved in particularly with their relationship to hardware, which is a really neat story.  So that's one half of the class, maybe half, maybe a little less than half. Okay, so I'm not gonna go over this in detail, eventually this will be online, but we're gonna talk, essentially the course is organized around sort of the three big units are on the three big parts of the computer that the operating system is in charge of multiplexing. So that's the CPU, memory, and the disk. This year my goal is to actually do a lot less on storage, which I've always thought is not, well, I don't know, it's grown on me over time. And more on virtualization. So I think virtualization is both really cool and super important, right? If you look at what's going on in Silicon Valley and other places, there's an enormous amount of energy around virtualization and new virtualization techniques. So I'd like to do more of that this year. So we'll probably do that at the expense of the storage unit. Okay, so again, how do you learn the concepts? Come to class, I try to start right at 205, ask questions. I don't have a strict roadmap for how much we do during class. If there's an interesting discussion that starts up, or if people are confused, or if I'm doing a particularly bad job at explaining something on a particular day and you're happy to point that out, we'll spend as much time on the material as we need to on a day-to-day basis, right? I don't really care where we end up. It's not gonna vary that much. But when you guys are, here's the thing, right?  I have no idea what's going on up here, okay? Let me get some smiling, you're nodding or whatever, and I'm trying to figure out like, maybe they're having a good memory, right? Maybe they're going to their happy place, right? Maybe their eyes are about to close, right? They're having a really happy memory, and they're just gonna, so I don't know. And you guys really have to help me. And again, just please raise your hand, speak up, just blurt out things. How things work in here is very informed, okay? I don't assign a textbook for the class. There are a couple of books that you can, if you want to get your hands on and look at. I don't assign reading from them. I think there's plenty of work in this class already, so I'm not gonna, you know, layer on something else. Modern operating systems is kind of the canonical text on computer operating systems, and certainly is highly complementary to what we do. And the C programming language, I mean, Kernighan and Richie, a classic. Is it actually in its third edition? Now it might be, right? Or maybe it's still in its second edition. Two editions in like 60 years, right? I mean, that's a modern classic. It's also a sign of how little C has evolved in 60 years, right? Which is another reason. Don't use C. But you will probably find this helpful, particularly if you're not familiar with C or have a difficult time with some of the concepts there. But one thing I want to point out is that lectures are the source that I use for exams and anything else. I will never quiz you or ask you on an exam to cover something that was not covered in lecture. Okay? All right, so any questions up to this point? I'm gonna try to get through this so we have time for some questions at the end. I don't know how I'm doing. There's of course no clock in this room that's useful for me. Ah, there we go, okay. Questions at this point? Yeah? What do you make available online in terms of lecture material? Everything, eventually, okay? So look, this slide deck, this is actually a webpage I'm just serving for my local computer, okay? So I'll get to that later. Last year, everything was online. All the slides, both in slide and outline format, there are four years of lecture videos on YouTube that are already up there. We post lecture videos pretty much immediately after class as soon as I get done with sort of transcoating them and uploading them, so they're all there. You can decide if I've gained weight since 2011 or whatever, I don't know. You can see as we move through a progression of equally dim and ugly classrooms. Anyway, yeah, so as much as possible, right? We're not trying to hold things back. I have, eventually, we'll get the old exams back online and everything, so really, we try to just dump everything onto the website. Yeah, it's a great question. Question down here? Yeah, so. So does the YouTube video still be that kind of flow? Yeah, yeah, let me come back to that and I'll be more clear about it, but the material's not different, the code base is not different. What's different is, anyway, we'll have some story time later and I can tell you about the four years of sadness and regret that followed my initial development of the tool chain for this course. And then finally, this year, it's over. I feel free and nothing works, right? But whatever, well, it will. And I'm a better person now. I feel like a great weight has been lifted, honestly. I don't know why that just went, oh, this is one of those things I always forget on day one. Turn on, turn on caffeine. Okay, yeah, let me come back to that. The class is essentially the same. How you submit things and how they're graded and things like that, and I think some of the grading we do in the assignments may change, but the assignments are the same, the instructional operating system is the same, the materials are the same, the lecture slides are the same. And so yeah, this is essentially the same course, right? We're just trying to fix some of the issues that we've had in the past that were the result of doing things in an incredibly dumb way. Okay, so now let's talk about the programming objectives. So when you guys are done with the course, I want you to be able to design and implement well-structured system software. And this is broader than just operating systems. This should be any large computer system, okay? Utilize appropriate synchronization primitives. This is something that we get to push on really hard in this class because the operating system is inherently an extremely high concurrency multi-threaded beast. And so in order to get things to work properly, we'll have to learn how to do this. How many people have done any multi-threaded programming? My hopes for the future are that like five years from now, everybody's hand will go up, right? If I was in charge of doing the intro class, you would, but anyway. Because it's not like computers have multiple processors or anything. Okay, so yeah, we're gonna do this. And then debugging. So identifying correct bugs and complex multi-threaded systems. We're not gonna give you any bugs to identify. We don't need to. You're gonna produce plenty all by yourselves, right? And finally, and this actually, this year I think we're gonna do more at. So we've always talked about performance. We've never really had a good way to evaluate performance. This year we're building a new tool chain that will allow us to evaluate performance. And I think there's a group of people in this class. Some of you know who you are already and some of you are going to be surprised to find out that you are this person who are gonna get extremely competitive about how your operating system performs. And we are gonna feed that, right? We're gonna feed that with a website, with a big list of everybody's kernel and how fast it ran.  I already have 100 out of 100 on the assignment. Why am I still working on it, right? And it's because you're in second place. You're in second place. Anyway, so yeah, we're gonna do that. That's one of my goals this year. And that's one of the reasons we're moving to some of these new tools. This, again, we're gonna give you these online testing resources. Please use them. And the programming assignments are how we test for mastery in this class. So let's talk about those programming assignments. How many people have heard about the programming assignments in the class? All right, good. Now these due dates right now are tentative. These are not, and this will somewhat depend on how quickly we can get some of this stuff for you guys to get going, okay? Assignment zero is really easy. In fact, I'm thinking maybe it won't be worth any points this year because it's almost too easy. Just getting comfortable with the tool chain, getting things set up, building your first kernel and running it in the simulator. Assignment one, last year what we did is we had these do it together just because of how easy assignment zero is. Assignment one, we're gonna start introducing you to synchronization primitives and have you implement some of them in your kernel and then use them to solve some toy synchronization problems. Those are probably, actually probably, those are the only time in this semester that we will ask you to write code that's not going to be part of a later assignment.  So this will take us sort of into mid February and my goal is to get these out there. My goal is to get assignment zero at least posted by the end of the week so that you guys can see what you're up for and get started because there's a lot of setup to do and stuff like that. Anyway, it's all really well documented. Okay, so this is time for a video break. You didn't think it was gonna be that easy for a second there? Yeah, I kind of did. Yeah, so it's not quite that easy, right? There's a lot more. This is just sort of a warm up, right?  Anyway, it's a really violent movie. I don't know why I have a slide about it, but it's a great movie. So then what we do is we go on into the two big and really exciting assignments, right? So assignment two, you get to implement the system call interface for this kernel that you're building, and then for assignment three, you get to implement virtual memory. And assignment three is really the crucible of the class and it is by far the most fun assignment. Again, if there was one thing about this class that really got me started down this road, it was assignment three, right? The rest of them are fun. Assignment three is a chance for you to really design a very large piece of software with a lot of internal interfaces and a lot of complexity. There's an enormous amount of design decisions to make and it is super fun when you get it to work. It's just an incredible sense of satisfaction. Okay, I probably should have had this slide earlier. So the instructional framework that we use for this class is an instructional operating system that's called OS 161. So this has been developed at Harvard now for over a decade by a guy named David Holland. Operating systems courses kind of have this balance that they need to strike. So for example, I could have you hack on Linux. The learning curve for Linux is like a rock wall. It's like El Capitan, right? I mean, it's just too hard to get anything done in Linux. Linux is like a billion lines of code. And here's the other problem with Linux. It already works. So I can't ask you to go implement virtual memory in Linux, that's already done.  On the other hand, there were also these existing operations and frameworks that weren't quite realistic enough. So OS 161 is extremely nice. It's a small kernel, it's heavily layout is really based on BSD. David Holland is a big contributor to various BSD releases. And it runs in a simulator. So that's the other thing. Now that we have better virtualization techniques, we might have been able to do some fun stuff using that, but back when this was being developed, the idea of running this in a simulator is very attractive. So you build a kernel, we give you a working simulator that will boot that kernel, and you're now in charge of implementing all these features. So the kernel we give you does not have virtual memory working, it does not have the system call interface implemented. So it really doesn't do anything yet.  But one of the things you're gonna do in assignment two is actually get to the point where it can run user programs, and you can actually run a shell. So you get it to the point that the real operating system would start out with, where it's gonna boot a user program, and then everything's gonna start from there. And sys161 just makes it a lot easier to debug the kernel, and it provides a really consistent environment for you guys to use. Okay. So where people tend to spend time in this class is on the hacking, right? Getting things to work, working on the programming assignments, and I wish I could say that it was easy. It's not easy. I'm not entirely not proud of these scores, I have to say, I always put them up every year. So one of the categories in the course values should used to be appropriate workload, right? I always thought that was a little weird. Appropriate to what, right? I mean appropriate to not having to do any work, right? So the score, we typically get pretty bad ratings on whatever sort of appropriate workload score that people give us, but the class gets awesome ratings overall, right? So I just wanna give you guys some context. The reviews in general are very good, right? You wanna see this guy, the crying guy? Crying man, Google it. So this is feedback from 2013. I think students in general really appreciate the class, let me also just say something upfront, which is that we have done our best, I have done my best to try to limit the workload for the course to the greatest degree possible without sacrificing the learning objectives. So in the past there were some sections in these assignments that we've got rid of that I kind of thought were a little bit more like busy work, those are gone. So there's a lot of work in the class, I'm not gonna apologize for that, but I'm not giving you work just for the sake of doing work. I'm giving you work that I think is going to help you improve as a programmer, learn what we're trying to learn in the class, and et cetera. All right, any questions about the course content before we go on to the even more exciting policy section of day one? Any questions? Okay, the website, last year I was so proud of this slide. It was like the website's ready, it's never been ready before, it's all up and then this year it's over. Okay, so essentially there were things about, so when I started, let me just tell you a little story. So when I started teaching this class four years ago, I was like, I'm gonna set up a website. I had no idea what I was doing and I built this terrible website. It did 20 things, it did zero of them well. And it was just this stinking pile of code that every year I would kind of poke it and it would kind of struggle to life again and then people would report the same problems they had the year before and I'd be like, you know what? I'm not fixing that because I don't know how it works. There's no way, if I try to change something, one character change might have completely ruined the whole class because nothing would have worked again. So after four years of sort of putting up with that, I finally just put the torch to it this year. So we are not gonna use that old tool chain. Now here's the great thing. A lot of the things that that website was doing, we don't need to do anymore because they're done by other software packages. So for example, this year, we're gonna have you guys use a GitLab instance that we host to store your Git source code. GitLab is awesome, it has all these features that were built by other people that work and therefore I don't have to worry about that anymore. It just works, it's awesome. So that's gonna be most of it. We're gonna figure out how to do some of the other pieces but I am confident that what's gonna come out of this is gonna be way better, okay? The other thing that we're doing is we're, and Scott and I have been working on this and some of the other TAs are gonna get involved as well. We're building a brand new testing tool that's going to allow you guys to do a lot more local testing before you submit things. So my goal is modulo you trying to cheat and game our grading system. You should pretty much be able to know exactly what your score is going to be on an assignment before you submit your code to the online grader because you're gonna have essentially the same toolkit that we're gonna use online for running tests, processing the output and figuring out if things work, okay? So that's gonna be new. I think that's gonna be pretty cool and that's gonna be useful, okay? Yeah? So let's submit more and more. Of course, yeah. So that's, yeah, let me, ooh, unhappy. So, yeah, let me come back to that. Okay, sorry, I'll get to that in a sec. Okay, so again, if this interferes with the deadlines, we'll adjust the deadlines. I'm certainly not gonna penalize you guys for our own ability, you know, sort of our own inability to get things out on time. But my goal is to have assignment zero again out by the end of the week so you guys can start, right? Some of the other tools will not be ready by then, but they'll come, they'll follow and you'll have them by the time you need them and they'll certainly have them by the time we expect you to need. Okay, so quick breakdown of grading. Half and half, half conceptual, half programming. Those are how the assignments break down right now. So on Wednesday, we do this thing every year that's called the preterm exam. It's about 15 minutes of your time usually, although some people get really competitive about it and decide to take the whole hour. Essentially, what we're trying to do is figure out what you guys already know. So we'll do that on Wednesday. During class time, you know, it's five free points, percentage points basically. So if you come and you do a little concept battery to allow us to sort of understand what people know when they start the class. Other than that, this is, I think, sort of pretty standard. Okay, so as, what is your name? I know your name and I've forgotten it. Zach? Yeah, so what Zach asked is, what about can I submit things multiple times? Of course you can submit things multiple times, right? Anything where the grading is automated, you can submit multiple times and that's the bulk of the points on most assignments. So essentially how it works is that we're gonna build a tool for you guys to use at the command line. When you want to, you can use that tool to submit things to our online grader. That'll run all the tests in an environment that we trust. It'll give you a score. If you've submitted one minute before the deadline, that's the score that you live with. However, if you've submitted a day before the deadline or a week before the deadline, you can say, hey, I like that score, I'm just gonna stop right there. Or you can say, and there's a few more points I saw at the table, I'm gonna keep going. So again, there's no reason for us not to do this. This is how, it helps you guys learn. And again, now what I'm hoping to is that you guys will see your performance numbers. You're gonna be like, my kernels dog slow, I should fix that and go back and work on that as well. But essentially, the grading for this class, we try to be as transparent as possible. You should know the grade that you're getting on each assignment. That also tends to cut down a lot on arguments about grades. The hand graded parts of the assignment this year, I'm not exactly sure what we're gonna do about that, but we'll let you know. In the past, the policy has been that those could be only submitted once because we actually have to have a human being grade them. But we'll see you this year. We may try to automate some of that as well. Assignments in this class are done in pairs. That's probably one of your to-do items for this week, is to find a partner. Your partner in this class, that's a pretty critical decision. You need to find someone who, one of the conversations to have with your partner is, how well in the course do you want to do? Because if you want to do well and your partner doesn't, that can be a source of conflict. Working alone is not something that we're gonna allow you to do unless, extremely, there's been a couple cases where this has happened and I won't divulge them in hopes of not giving anyone any ideas. But I want to work alone is not one of the unusual cases that we represent. The other thing about the class is that the assignments are cumulative. So this is something to keep in mind. If your assignment two doesn't work, your assignment three is not going to work. If your synchronization parameters don't work for assignment one, it's gonna be really hard to do the other two assignments. We have been distributing solution sets in the past. However, we are going to take more points from you than you're gonna be happy about. The goal here is to encourage you guys to do the assignments, to do them well. And so that's the source of this policy, right? And so particularly when we get to the assignment two deadline, I always tell students you have two choices. You can fix your assignment two bugs now and you can get points for them or you can fix them later for assignment three and get no points for them on assignment two, right? So that's kind of how it works. All right, we're gonna have a mass email list. We're also gonna try not piazza this year. I'm kind of tired of piazza. There's things about piazza I find incredibly irritating. And so we're gonna, we have a discourse bulletin board set up that you guys will have accounts for. And one of the things I don't like about piazza for this class is that in a lot of cases there aren't right answers about how to approach some of these problems. And I think piazza tends to encourage people to take those one answer to the question. I mean, that was true when you were five, but now that you're writing the sort of systems code it's not. Okay. Let me just breeze through this quickly. There is a course staff email list. Please don't send us email if it's something that you can find some other way. And particularly once we have the website and the forum up please use those, don't contact us. The course staff works really hard. They're gonna be in office hours for four, five, six hours a week. They're gonna be doing a lot of work behind the scenes to build some of the things you guys are gonna be using. The more we have to answer repetitive questions, the less of that other stuff we get done. Same thing for me, right? So if you email me please be very certain that this is something that really needs my attention and can't go to the staff email list because there is one of me in 14 TAs and ninjas and so your likelihood of getting a response for me is lower. Okay. So Ali and Jerry will be doing the recitations. We're gonna start those next week. Those will be on the calendar that we're gonna post. As I pointed out, they cover a mix to the sort of conceptual and the assignment driven material. And this year we'll probably try to do some screencast. We've been recording the recitations last year. I think for the last two years. So if you wanna watch Jing House recitations from last year, you're certainly welcome to do that. Those are all online. Okay, office hours. So office hours is really the place where we try to provide you as much help. So my contract for the class with you guys is I'm gonna give you a lot of work to do but I'm also trying to give you as much help as possible. That's why all the students in my group are involved. That's why I've pulled favors from all these awesome ninjas and had them come back and help you guys out. So we're trying to give you as much help as possible. I don't want you guys to feel like you can't do the assignments because you didn't get enough help. So last year I think we had about 40 hours of office hours a week. It might have been like 40 person hours or something but it was a lot. So there's definitely a lot of time for you guys to come in and get help. And my suggestion is just do the assignments in office hours. Just like come hang out, you can hang out in my lab, you can hang out in the hallway, you can hang out in that tiny little room that we have. And just work there. You don't need to have a question. You'll have a question once you get started. You'll get stuck and then you're in the right spot. And even if you're not stuck, it's fun to be around other people who are doing the same stuff. You'll hear some things that will be useful to you or whatever. So just when you're working on the assignments, come to the location where we're having office hours. It's always the same place. I just hang out there, right? Okay, partners are jointly responsible for joint work. If any part has plagiarized, both of you guys fail. Let me just point that out again. If you have concerns about something that your partner has submitted, please approach us right away. The longer the time goes by, the more we assume that you were somehow complicit, okay? I've got like two minutes and let me do, and the assignments are very clear. So each assignment has a section that says, here are things that we encourage you to do collaboratively. Here are things that don't encourage you to do, but they're not cheating. And then here are ways to cheat on this assignment, right? And these are the things that you do. If you do those things, that concept is cheating. So there's no gray area here, okay? If you think you've found one, come talk to us and I'll add a clarification, right? This has happened in the past, but I think at this point, we've sorted it all out, okay? On the other hand, please don't be shy about helping each other on the forums, in office hours. You know, the general approach here is that when people in this class work together with each other, they do really well, right?  As long as you're not sharing code, as long as you haven't cut and pasted your code and sent it to someone or you're allowing them to like look over and memorize it. I've had people tell me when they got taught cheating that they memorized something that they saw over someone else's shoulder, I'm like, yeah, right. You know, I mean, maybe you're like Rain Man or something, but I don't know why you're taking this class then. Okay, so this is the rule about collaboration. If you share code, you're cheating. If you're talking about a problem, you're not, right? Unless you're talking with your partner. We take cheating very seriously. Every year I end up failing a couple of people because of cheating, I hate it, but I will do it mercilessly because there are people in this class who are gonna do their best and work their butts off and they're gonna get like an okay, great. And if you think you're better than those people for some reason and you should just get a free pass, then I disagree, right? And I'm like that guy, okay? I'm gonna find you and when I find you, I'm gonna be like her, all right? I'm gonna be mad. I have, this is the best thing after teaching this course for four years, I have the world's largest library of assignments that have been submitted for this class, right? I have hundreds of them, okay? If you think you found something that I didn't, just think, think about it for a minute, right? Just think about it for a minute. I look everywhere, right? And we use Moz, the same tool everybody else uses. We have tools in place for doing this on a really large scale. We'll test everything you guys give us. Just don't cheat, please. I am begging you. I would love to have a course one year where no one cheated. That would make me so happy. It hasn't happened yet. Maybe this will be the year. Okay. So, see, this guy, he got an F. This is the policy about cheating, okay? The most interesting man in the world? I don't care, also failed, right? This cute cat, yeah, she's unhappy because she got an F in the class. Tom Brady didn't cheat on the football field, but got an F for cheating in this class, okay? Mother Teresa, come on, not really. Mother Teresa didn't cheat in the class, right? This guy didn't cheat, now owns own business, right? So, that's your choice, right? But again, I am begging you, please don't cheat. All right, any questions about this? Okay, inclement, whether bubble schools are closed or wanna have class, yeah. Are you allowed to use snippets of C code that you found? If you find something online and you wanna use it, talk to us. In general, the answer will be no. Yeah. It's not just like single line, like C hacks, where is it? We don't, yeah, we don't catch that stuff. What are we doing? Yeah, yeah, we're looking at hundreds of lines here. If there's inclement, whether you don't have to be here, but Yee Hong will be here. I just wanna point that out. Yee Hong has never missed office hours. Okay, so, buh buh buh. All right, so sit tight for more details. On Wednesday, two o'clock, preterm exam, this room, five free percentage points. Yeah.


You sponsor because everybody in the Kubernetes ecosystem that matters is here.  And I know I'm going to meet people I can hire, I can sell to or potential partners all in one place every single time. We are excited to be sponsoring KubeCon because it's a great way to meet the people in our target market and make some connections and bring some business back at the end of the day. As a sponsor, this event is pretty amazing because it brings together people from all over the world, different backgrounds, different technology.  If you go to your traditional corporate sponsored events, it is a very similar type of persona that shows up. Here at CNCF events, you have a diverse group of not just your corporate sponsors that show up, but you also have the important developers that are there. As you follow up post conference, you are able to talk to a multitude of decision makers as they look to evaluate your product to see what is the best fit for them. We're trying to bring all of our previous customers, our current customers and our new customers together. And being a sponsor was the best way to get in front of a lot of people. But secondly, also to start to figure out how to engage with the community to contribute towards advancing this community. You've got to be a sponsor. As KubeCon sponsors, we find very qualified leads. We're talking to the people that are using our projects directly and having direct feedback from them, and that's super special. As a sponsor, we love building relationships with our community. As a sponsor, we're here to network with technologists and recruit and hire for our open jobs. As a sponsor, it's so much fun being here, learning about all the different open-source technologies, and we're hoping to find some really great people here to make our products better. J-Frog is a proud sponsor of the CNCF. KubeCon is our favorite show of the year. It's the biggest show of the year. For us, we hit the right audience, the right attendees, the right community. It's all about open-source and sharing and community. And we wouldn't be here if it wasn't for CNCF.