Dear students, now we are going to see the topic government regulation of the media. What is regulation? With regard to mass media, laws and guidelines that influence the way media companies produce, distribute or exhibit materials for audience are called regulations. So when we talk about the regulations of the media, there are different approaches. Those who compare media systems around the world describe four different approaches to government regulations of the media. These approaches describe the amount of control government should have over the media from high levels of control to low levels of control. So basically in these approaches, they talk about what kind of control government should have on the media. The first approach in this regard is the authoritarian approach. Authoritarian approach to media regulations are aimed at controlling what the population sees, reads and hears through the media outlet. These approaches are typically adopted by dictators who want to keep themselves and the elite class that support them in a direct control over society. So the authoritarian approach to control the media is basically then adopted when countries where there is a dictatorship, where there are monopolies, and where there is a lot of control of the state institutions. These approaches are followed by whatever is shown, according to the state policy, and whatever is the ruler of the state, it will be shown with the perspective of it. Authoritarian rules often claim that they are re-secuing their people from evils that the society may have experienced in the past. These authoritarian rulers believe that they are rescuing and many mis-apps have been ending them in the past, so the media should support them. They justify controlling the media and other aspects of life by saying that these activities are necessary in order to unify the public. They believe that if we don't do this, we can't unite the nation, we can't unite people, and that's why it is necessary to control the media and media should only show their perspective. Communist approaches to the government regulation believe that the government should determine what the population sees, reads, hears, and experiences through media outlets. They depart from authoritarian approaches, however, in the way they justify this control. So, in communist governments, they believe that media should carry the philosophy of communism and socialism, and they present only those news that are according to their ideologies and according to their beliefs. The third approach is a libertarian approach. Individuals are capable of making sound decisions of themselves, and that government should intervene only in those or clear circumstances where society cannot be served by people going about their own businesses. So, this libertarian approach, this is a liberal approach. In this, it is believed that the role of the government should be very limited in controlling the media, and the media should be controlled by the government, which are very important issues, and there should be an independent body for the control of the media, which should have a limited influence on media related matters. Social responsibility approaches. Supporters of social responsibility approaches believe that the real competition of ideas that libertarian seeks will never happen without government action to encourage companies to be socially responsible by offering a diversity of vices and ideas. So, it is a mixed kind or hybrid kind of approach in which they believe that media should be free, media should be independent, but media should be independent with some kind of social responsibility. And in order to ensure that responsibility, government should develop such kind of mechanism through which they can monitor the performance of the media organizations and media outlets.


Greetings from the National Archives Building in Washington, D.C. I'm David Ferriero, Archivist of the United States and head of the National Archives and Records Administration. Fourth of July is a special occasion here at the National Archives. We're the home to the original 1776 Declaration of Independence. We like to say that July 4th starts here. And for the past 50 years we've had a ceremony here in this building to honor the Declaration of Independence. But this year is different. Because of COVID-19, we had to find a new way to celebrate. So we are doing our first virtual Declaration of Independence reading. You'll see highlights of past Fourth of July celebrations at the National Archives during this program. Even though we can't be together this year, we can focus on the future. In 2026, six short years from now, we will be celebrating America's 250th. 250 years since our founding fathers signed the Declaration of Independence, jeopardizing their lives, committing treason, and risking everything for American independence. We have the signers to thank for the freedoms we enjoy today. Even though this year's celebration will not look like our usual Fourth of July festivities, we can look forward to marking the 250th anniversary of the United States as a healthier, stronger, and more perfect union. Before we start, I would like to thank you for joining our virtual ceremony. I hope to see you in person at the National Archives in the near future. Have a safe, healthy, and enjoyable Independence Day. When in the course of human events, it becomes necessary for one people. This phrase is where it began more than 240 years ago. The desires of one people to unite together, forming a new nation to break free from the tyranny of a king, a nation based on the principles that all men are created equal and have the unalienable rights of life, liberty, and the pursuit of happiness. This radical notion shook the world and became a compelling testament to the strength and spirit of what it means to be united and free. This is our Declaration of Independence. If the Constitution is the roadmap for democracy, the Declaration of Independence is the road on which we all travel. Abraham Lincoln called it a rebuke and a stumbling block to tyranny and oppression. It declares our liberation from dictatorship, our foundations for democracy, and our formal pledge to abide by these terms at any cost. Over the centuries, the powerful ideas of this document continue to inspire not only our country, but countries around the world to fight for freedom, justice, and equality. It sounds like a dream. And in a way, it is. It's the American dream. We are the only country with the word dream attached to it. It is a dream in which people from all over the world arrive as immigrants and create the mosaic that makes us stronger. In America, you can start with nothing and build an industry. In America, you can turn a spark of an idea into a lasting legacy. This is more than just a dream. It is our way of life. At our best, we embrace our differences and allow all to flourish. When we fail to include all, we find the courage to face our shortcomings and work together to continue building a more perfect union. It took Thomas Jefferson three weeks to pen the Declaration of Independence with the hope that his words would serve as an expression of the American mind. We still stand by those words today. The permanent home of the Declaration of Independence is in the National Archives, right here in our nation's capital. The Archives preserves and protects all sides of the American story. And like the principal idea in our country's proclamation, the information it contains is free, accessible to all who seek it. A walk through its main rotunda is to exalt in the story of America. It is, as journalist Koki Roberts once described, America's Cathedral to Democracy. For 50 years, the National Archives has held a July 4 celebration of the Declaration of Independence on its grand front steps. It is the traditional kickoff event for all of the patriotic activities in our nation's capital. Circumstances have made it difficult for all who wish to celebrate with us in Washington, D.C. to do so this year. But that should not mute our collective spirit to celebrate our independence. So wherever you are and whomever you are with, please wave your flags and join us in our celebration of the Declaration of Independence at the National Archives. July 4 begins here. We begin our celebration with the presentation of the colors by the 3rd United States Infantry Old Guard Continental Color Guard and the singing of the National Anthem by retired Army Master Sergeant Caleb Green. What so proud at the twilight's last gleaming Whose broad stripes and bright stars through the perilous fight O'er the ramparts we watched were so gallantly streaming And that our flag was still oh say does that star-spangled banner yet wave Circumstance artifacts, photographs and films in the holdings of the National Archives tell the story of America. And the mission of the National Archives is to protect, preserve and make these documents available to you, the American people. Here now is the person to whom our nation has entrusted the care of our documented history. Vietnam veteran and 10th Archivist of the United States, David Ferriero. Good morning, thanks to all of you for joining us in this 241st celebration of the signing of the Declaration of Independence. And greetings to the folks in 10 of our Presidential Libraries who are live streaming this ceremony this morning. I'm originally from Beverly, Massachusetts, the birthplace of the American Navy. In Beverly, the 4th of July meant a real bonfire built of kerosene-soaked barrels, fireworks at West Beach or a trip to Boston for the Boston Pops on the Esplanade, performing the 1812 overture and fireworks over the Charles River. And you all have your own 4th of July commemorations, a time for friends and family to gather and celebrate summer. My own view of this day changed when I became Archivist of the United States. I realized that we own this day. The 4th of July starts here, here at the National Archives building. We are the keeper of the original Declaration of Independence. This seminal document signed by our founding fathers. It is enshrined in the rotunda of the National Archives behind me. Just think of the courage it took to sign the Declaration and how important independence from England meant for them to risk their lives. It was an act of treason for those who signed. They became wanted men, traitors to the King. By the end of the Revolutionary War, more than half of the signers suffered direct personal consequences for their support of American independence. We have the signers to thank for the freedom and celebrations we enjoy today. The Declaration of Independence has had an amazing journey since it was signed on August 2nd, 1776. During the Revolutionary War, the Declaration was rolled up and moved from city to city as Congress moved to avoid capture by the British. When the British were burning Washington during the War of 1812, Secretary of State James Monroe directed State Department clerks to gather up the important documents and get them out of town. They wrapped the Declaration and other precious documents in bags of linen, commandeered wagons on the street, and in the dead of night, headed for Virginia with the records of the country. First, they hid the Declaration in an unused grist mill near Chain Bridge in Virginia, then in a private home in Leesburg until the war was over. During the 1800s, the Declaration was on exhibit for long periods at several locations in Washington where it was exposed to sunlight, fluctuating temperatures and humidity, all of which took their toll on the document. Finally, officials took note of these effects of aging and wrapped the Declaration and stored it flat at the State Department where it joined the Constitution until 1921 when President Harding signed in order to transfer both of these documents to the Library of Congress. Just before Pearl Harbor and the U.S. entrance into World War II, the Library sent the Declaration and the Constitution to Fort Knox for safekeeping, where they remained until September 1944 when they came back to the Library of Congress. Finally, the documents came to their rightful home here at the National Archives. The transfer occurred on December 13, 1952 with great pomp and circumstance and security as the newly encased Declaration of Independence was carried up these steps with a military procession into the Rotunda. And the Declaration of Independence was safe until 2004 when a good treasure hunter, Nicholas Cage, cleverly stole it during a party in this building to protect it from an evil treasure hunter. And our national treasure was miraculously and circuitously restored to its rightful place and now poses the most often question in the Rotunda, can we see the back? And I can tell you for certain that the only thing on the back of the Declaration are the words original Declaration of Independence dated 4 July 1776. So thanks for coming out today. The National Archives is home of the Declaration of Independence and July 4th starts here. Now let's take a trip back to the era of our independence with the colonial uniforms and music of the 3rd United States Infantry Old Guard Fife and Drum Corps. Good morning, ladies and gentlemen, the United States Army Military District of Washington under the command of Brigadier General Omar Jones is proud to present the United States Army Old Guard Fife and Drum Corps. The 3rd United States Infantry Regiment, the Old Guard traces its lineage back to George Washington's original Continental Army and today serves as the Army's official escort to the President of the United States. In 1960, the Fife and Drum Corps was organized to participate in official ceremonies and to revive our country's musical heritage. From the days of the American Revolution through the 19th century, fives, drums, and bugles were vital to military order and discipline. Field musicians were used to issue commands during battle and to regulate the duty day, signaling when to rise, when to eat, and when the day ends. This morning's show paints a series of pictures from the life of a Continental soldier musician. We open at the beginning of the duty day with a training scene. In the 18th century, signals like a tension and breakfast call would have sent the soldiers into action. Here, we begin with those signals and accompany their daily training with marching tunes including drums and guns and simple jasha. Declaration of Independence was our first act of unity as a nation. With a vision for a better way of life, we persevered against an unimaginable force at the threat of personal peril and impossible odds of success. That unifying moment established the two pillars of our national character, service and sacrifice. Over time, our character has been tested in many ways, from hurricanes and tornadoes to wildfires and floods. We have weathered the fiercest of natural disasters to help our communities heal and get back on their feet. During two world wars and several regional conflicts, we helped our allies on foreign fronts while we rolled up our sleeves, rationed, and sacrificed at home. We lifted ourselves from the depths of the Great Depression with the tenacity of public works programs, Social Security, and Medicare to ensure every American gets help when they need it. We fought back and stood strong against acts and threats of terrorism. And we continue to take strides towards creating a more perfect union and equality for all by seeking to right wrongs and provide justice to the oppressed. Americans respond in times of crisis, and we do not stop until the work is done. With service and sacrifice, we have overcome the monumental challenges of our past. And as was set forth so many years ago in the Declaration of Independence, it is these principles upon which we will persevere against the challenges we face now and in the future. This is who we are. This is America. The soldiers of the United States Army Old Guard Fife and Drum Corps wear uniforms patterned after those of General Washington's Continental Army. In order to be easily identified, military musicians wore the reverse colors of the regiment to which they were assigned. At that time, American infantry soldiers wore blue coats with red facings. Thus the musicians wore red coats with blue facings. At the end of the day, troops would often gather around the campfire to relax, and the musicians would provide entertainment. Picture yourselves in such a setting now as we feature the Fife and Bugle groups in a scene reminiscent of the soldier's respite following a challenging day. National Archives tradition for over 50 years. Join us now for a reading of the Declaration of Independence by our distinguished group of guests. General George Washington, Mr. John Hancock, and Mrs. Abigail Adams. In Congress, July 4th, 1776, the unanimous declaration of the 13 United States of America. When in the course of human events, it becomes necessary for one people to dissolve the political bands which have connected them with another, and to assume among the powers of the earth the separate and equal station to which the laws of nature and of nature's God entitle them. A decent respect to the opinions of mankind requires that they should declare the causes which impel them to the separation. We hold these truths to be self-evident that all men are created equal, that they are endowed by their creator with certain unalienable rights, and that among these are life, liberty, and the pursuit of happiness. That to secure these rights, governments are instituted among men, deriving their just powers from the consent of the governed. And that whenever any form of government becomes destructive of these ends, it is the right of the people to alter or abolish it, and to institute new government, laying its foundation on such principles and organizing its powers in such form as to them shall seem most likely to affect their safety and happiness. Prudence indeed will dictate that governments long established should not be changed for light and transient causes, and accordingly all experience hath soon that mankind are more disposed to suffer. While evils are sufferable, then to write themselves by abolishing the forms to which they are accustomed. But, when a long train of abuses and usurpations pursuing invariably the same object and visions are designed to reduce them under absolute despotism, it is their right, it is their duty to throw off government and to provide new guards for their future security. Such has been the patient's sufferance of these colonies and such is now the necessity which constrains them to alter their former systems of government. The history of the present king of Great Britain is a history of repeated injuries and usurpations. All having indirect object the establishment of an absolute tyranny over these states. To prove this, let facts be submitted to a candid world. Now to read the grievances against King George III, we have three of the leaders of the Second Continental Congress. Mr. Thomas Jefferson, Mr. John Adams and Dr. Benjamin Franklin. These gentlemen know the words of the declaration better than anyone else. All three served on the committee to draft the declaration. And Mr. Jefferson was the primary author. He has refused his assent to laws the most wholesome and necessary for the public good. He has forbidden his governors to pass laws of immediate and pressing importance unless suspended in their operations till his assent should be obtained. And when so suspended he has utterly neglected to attend to them. He has refused to pass other laws for the accommodation of large districts of people unless those people would relinquish the right of representation in the legislature. A right inestimable to them and formidable to tyrants only. He has called together legislative bodies at places unusual, uncomfortable and distant from the depository of their public records for the sole purpose of fatiguing them into compliance with his measures. He has repeatedly dissolved representative houses for opposing with manly firmness his invasions on the rights of the people. He has refused for a long time after such dissolutions to cause others to be elected whereby the legislative powers incapable of annihilation have returned to the people at large for their exercise. The state remaining in the meantime exposed to all the dangers of invasion from without and confusions within. He has endeavored to prevent the population of these states for that purpose obstructing the laws for naturalization of foreigners refusing to pass others to encourage their migrations hither and raising the conditions of new appropriations of lands. He has obstructed the administration of justice by refusing his assent to laws for establishing judiciary powers. The judge is dependent on his will alone for the tenure of their offices and the amount and payment of their salaries. He has erected a multitude of new offices and sent hither swarms of officers to harass our people and eat out their substance. He has kept among us in times of peace standing armies without the consent of our legislatures. He has affected to Randa the military independent of and superior to the civil power. He has combined with others to subject us to a jurisdiction foreign to our constitution and unacknowledged by our laws giving his assent to their acts of pretended legislation for quartering large bodies of armed troops among us for protecting them by a mock trial from punishment for any murders which they should commit on the inhabitants of these states for cutting off our trade with all parts of the world for imposing taxes on us without our consent for depriving us in many cases of the benefits of trial by jury for transporting us beyond seas to be tried for pretended offenses for abolishing the free system of English laws in a neighboring province establishing there in an arbitrary government and enlarging its boundaries so as to render it at once an example and fit instrument for introducing the same absolute rule into these colonies for taking away our charges, abolishing our most valuable laws and altering fundamentally the forms of our governments for suspending our legislatures and declaring themselves invested with the power to legislate for us in all cases whatsoever He has abdicated government here by declaring us out of his protection and waging war against us He has plundered our seas ravaged our coasts He is at this time transporting large armies of foreign mercenaries to complete the works of death, desolation and tyranny already begun with circumstances of cruelty and perfidy scarcely paralleled in the most barbarous ages and totally unworthy the head of a civilized nation He has constrained our fellow citizens taken captive on the high seas to bear arms against their country to become the executioners of their friends and brethren or to fall themselves by their hands He has excited domestic insurrections amongst us and has endeavored to bring on the inhabitants of our frontiers the merciless Indian savages whose known rule of warfare is an undistinguished destruction of all ages, sexes and conditions Mr. Adams In every stage of these oppressions we have petitioned for redress in the most humble terms Our repeated petitions have been answered only by repeated injury A prince whose character is thus marked by every act which may define a tyrant is unfit to be the ruler of a free people Nor have we been wanting in our attentions to our British brethren We have warned them from time to time of attempt by their legislature to extend an unwarrantable jurisdiction over us We have reminded them of their circumstances of emigration and settlement here We have appealed to their native justice and magnanimity and we have conjured them by the ties of our common kindred to disavow these usurpations which would inevitably interrupt our connections and our correspondence They too have been deaf to the voice of justice and consanguinity We must therefore acquiesce in the necessity which denounces our separation and as we hold the rest of mankind enemies in war in peace, friends We, therefore, the representatives of the United States of America and General Congress assembled appealing to the supreme judge of the world for the rectitude of our intentions due in the name and by the authority of the good people of these colonies solemnly publish and declare that these united colonies are and have right ought to be free and independent states Allegiance to the British Crown political connection between them and the state of Great Britain is and ought to be totally and that as free and independent states they have full power to levy war, conclude peace, contract alliances, establish commerce and to do all other acts and things which independent states may of right do And for the support of this declaration with a firm reliance on the protection of divine providence we humbly pledge to each other our lives, our fortunes and our sacred honor 56 signers of the declaration these names will be read by private Edward Ned Hector of the Third Pennsylvania Artillery Company a free black colonial soldier, patriot and an American hero Which one of you out here has courage? Which one of you would be willing to sign your own death warrants? These people were willing to sign their own death warrant Attend now as I read their names The Honorable President of the Continental Congress John of Carrollton, Topkinson document is the secretary of the Continental Congress willing to sign this document Let us give them United States Army Old Guard Fife and Drum Corps drum line in a battle feature Please welcome the veterans and active duty service members of Voices of Service and their moving rendition of America the Beautiful for joining the National Archives July 4th celebration The ceremony is coming to a close but the spirit of our independence lives on Our national characteristics of service, sacrifice and unity will help us through these challenging times and for whatever challenges we face in the future The National Archives is honored to continue its mission to protect, preserve and make public the entirety of the American story Please visit archives.gov to learn more about the American story and how you are part of it We are one people, we are united, we are America Happy 4th of July from the National Archives The audience, did you hear how the people were behind what was read? Did you hear the spirit? We felt it and it was quite an electrifying time to be up there and to hear their response So this is the first one where I really get to see the expanse of the parade and really get to enjoy the portico and all the National Archives has to offer for the 4th of July Really enjoyed it and got a lot out of it and gives me a real good sense of history now The music was fantastic from the opening band all the way through to the Drum and Fife Corps It's the energy, the people Everybody's celebrating what a great country we have You can't get a better feeling for loving your country than being right here where it all started So this is the best place We're in the greatest city in the greatest country in the world and I just feel honored to be a part of it The festive atmosphere, everybody is having a great time It's a very American patriotic feel And check out the Declaration of Independence I see the Declaration of Independence on 4th of July I mean there's nothing better We're here to celebrate our nation's capital 4th of July with you guys and visit all the great monuments and all the festivities One reason where the archives exist is to show our founding documents and tell the American story Very special experience It's really special It's been wonderful Also patriotic Happy 4th of July Happy 4th of July


Realistic gaming here today. We're gonna be storing area 51 in Roblox, and there is area 51 Oh my god, what there's an alien out already. What is he doing out here? Okay, so it seems like our mission is done here.  We're gonna run in there like now until we gotta do the knowledge to run Well, we can't exactly do it here, but just pretend we're doing the knowledge to run. Come on.  No don't go in here yet. It says stop everybody only does it guard right here Hey guard, guess what man?  He says stop. You know what? We're not gonna listen to you. Let's go in here. Okay. So look at this place, man There's even a stage for the alien So when are we like celebrating the aliens you guys or something? Why is there a stage for the aliens aliens area 51? Okay, I don't know what that is for but let's go down here inside area 51 you guys go down here. Check it out Okay, so we're inside of area 51 Oh my god, where are the aliens at? Somebody show me the aliens. I want to see the aliens I might want to keep one as a pet for something you never know Okay, UFO follow the sign that'll take us to the UFO Oh my god, okay, so I don't see any aliens yet aliens. I'm here to take you home I'm gonna take you back to mars or wherever you're from. I don't know man. Where are aliens even from? Well, I mean they're from space, but they can be from anywhere in outer space only if there's an alien Oh my god, yo alien. Let's go. Let's get out of here, man. What is he doing?     There's an open door Let's see where that takes us. Dude, that alien is still coming this way. Oh my god. No, don't bring him over here This dude got smashed. Oh my god. Yo, you good my boy. All right. I think he's good Okay, let's keep going guys because the alien's gonna come this way. Wait, where did he get a coil from? This dude, he has a coil Oh my god, okay, subscribe to pewdiepie. Okay, so let's go up here. What exactly is there up there says tnt Okay, so we might need this oh We might need this tnt for something to get out of here or to blow a door Oh my god, there's too many people. Yo Okay, let's go keep it steady Oh my goodness. Okay. We got this. No, you know what? I don't even need the tnt. I'm out of here Get up with this guy. He's partying over there. All right. See you guys later Okay, uh, so there's tables in this room That is pretty freaky, huh? Okay, let's go over here But yeah, let's follow the ufo sign. Where's the ufo at? Oh, like it says ufo right here Okay, so we follow the sign on the ground And they should direct us to the ufo you guys This might be the real deal So let's go this way. Oh like there's an alien over there chasing someone Okay, what's in here? Oh, i'm a special player Okay, I don't know who that is. I'm out of here man. Come on. They know let's get out of here Oh my god. Okay, that's ninja. I thought that was an alien, but oh, what you know Dude get away. No, don't touch me Dude get ninja right there Oh my god, okay, so we just got ambushed by the aliens. I have no idea dude. You have an alien on your head Well, look at his shirt. I'm going okay So this guy is signed up for the now to run to storm into area 51 That's pretty hilarious Okay, so so much for the guards to stop us, right? We just stormed in this bad boy like we were storming in Toys R Us dude. There's an alien right here I stormed area 51. Okay, let's take a picture with this alien All right, that one's for the bucks you guys. Okay, so let's go back down here Oh wait, are the aliens blocking the other way use this one? Okay, so it seems like we found the secret entrance In two area 51. So let's go check this side out My god, there's like an airplane over there I wonder what that's all about. Okay, so we dropped all the way down in here Be an alien click to be an alien make sure to rejoin after bite Oh, so we could be an alien, but we have to rejoin I don't want to rejoin. Oh my god. Wait. These aren't zombies. These are not aliens I mean, I guess they have zombies in every 51 you guys Oh god, okay So this place is no joke at all Okay, so let's try to get to the UFO Because it says that there's a ufo in here. I definitely want to ride that bad boy. I can't this way Hopefully the aliens aren't over here looking because I know there's a lot of them around here Okay, any aliens around here? Okay, I think we're good so far Yo, oh my god. Look. She's on top of there because of the alien. She's scared No, don't do it. Pleasure. There's an alien right there You know what? I'm out of here. Let's go to the UFO. We need to go to the UFO. That's our objective right now Please don't let there be eight. Oh my god. There's two aliens right here. You gotta be kidding me, man Oh, no, now he's chasing us great Okay, so now we're being pursued Dude, is that an alien egg? Oh my god. Why is there an alien egg right there? Okay, you info. Oh Nice the UFOs are right here. Can we actually ride it? Oh, we can Oh my god.   That's the question I'm breaking out of here man. So you guys like oh man, we can't break out of here What kind of UFO is this man? Come on. Okay, so we can't break out of every 51 with the UFOs I would have been epic, man Hey, can we drive it out of here? Oh, I guess you could just fly the UFOs inside Getting dude that guy's getting chased by the alien. I got your man.  Okay, you know what? No Oh my god. No, no Great the alien killed us Dude, now he's riding the UFO himself Okay, so so far we've seen a couple aliens And we've rode a UFO which is pretty awesome And we were supposed to come and rescue the aliens, but the aliens are killing us So I don't know about that one, man Oh my god. Oh no, that's a ninja Dude, he keeps getting me with this alien outfit Okay, so we went that way. Let's go this way now Wait, what's that door over there? Let's go check out that door dude. That alien has like super powers What? Oh my god. No don't get near that guy Okay, can we get around go go go before he goes? No lock the door No Dude, I was trying to close the door on this dude. Oh, like there's a door with a with the number pad on it I hear like a monster roar I think it's coming from this way. Oh like there's a door Where does this take us? There's an alien workshop.  There's aliens everywhere Oh my god Guys there's aliens in here. Why is that alien? Oh dude receiving alien eggs. Oh my god. This looks frequently weird Uh-oh, uh-oh that alien is moving I don't think he's supposed to be doing that man Okay, I'm out of here Wait, how do we get in here?  No, okay. I'm stuck here with the alien Oh my god. Can you please leave me alone? Oh, I'm looking fancy, huh? Okay, you know what?  No I had no idea what was going on.  I think that was the game pass room for us to be an alien and we broken there somehow Oh my god. Okay. So now if the creator ever sees a video He could like patch that Okay, so let's go down here one more time and see if we missed anything in particular I feel like there should be another entrance Okay, whatever.  Oh, yeah, we haven't checked out that room in here Let's go check it out because the alien killed me last time Alien you better not be out here lurking man Okay, I think we're good Oh my god, there's an alien in here. He's in the medical bed. Yo wake up man. I'm here to take you home Okay, I think this guy is definitely a gon or something.  Oh look we could get this suit right here Wait, does that door open? Why is there a door right there? What? That makes no sense. There's like nothing on this side Maybe it's like a secret door I don't know. Oh, yeah, let's ask him for the code. What's the code man? Hey, hey, you need to put the code for us My boy You need to pick us up with the code real quick. We need to go in here Guys move the owner's trying to put the code Oh my god, no let the owner Dude the owner's right there. He knows the code Come on put it put it put it. I want to see what's in here. Go go go. All right. Nice. We're in here Oh, you get coils in here.  What why is there just a big hit on the ground?  That's pretty cool, man All right, you guys. Well, unfortunately, we couldn't take any aliens home I really wanted to take one back home with me because who wouldn't want a pet alien, right? Well, thank you guys for watching. Thank you guys for the amazing support If you guys enjoyed the video, make sure to slap the like button If you're new to the channel, make sure to subscribe and turn that notification bell on and I will see you guys In the next area 51 right Bye


had the pleasure since the year 2001 of not only organizing these conferences with my colleagues here, but of also working with our next speaker. I think that I can actually attribute a lot of what I've done in the last 10 years to the relationship that I have with Dave Thomas, specifically because I think it was RubyConf itself that got all of it started for me. And I think it was August of 2001. We had the conference in October of 2001. Someone had been organizing it, a guy named Guy Hearst, and life got in the way. And RubyConf, the first one, was in jeopardy of not actually happening. So we were on IRC. There were 12 of us on IRC and Ruby laying at the time. And Dave Thomas, private message me and David Black, and invited us to join a channel called RubyConf. So there are now three people in the RubyConf channel. And he said, this is really important.  We have to make this happen. And so we did. And it was because Dave kind of made us do it. He supported and encouraged us. And so the first RubyConf conference was actually co-organized by me, David Black, and Dave Thomas. The opening remarks at the first Ruby conference were given by Dave Thomas. And so we decided that for this conference, as a special 10th commemorative edition, it would make sense for Dave to do the opening remarks again. So please welcome Dave Thomas. This is typical, right? Software conference, supposed to start speaking at 9.15 and it's now 9.30. So we're going to start late and probably finish late. 10 years. 10 years is absolutely amazing. Sometimes it feels like, you know, a couple of months. Sometimes it feels like 100 years. But through that time, I've never stopped having fun. And that's absolutely amazing. And one of the reasons for that is the people that we've been involved with. And people it's going to sound like terrible, like log rolling, but people like Chad and Rich and Mike, Nicole and James, everybody else, absolutely amazing. And I really appreciate it. But it also happens that today is, well, back in 1918, on November the 11th, the 11th day of the 11th month, at 11 o'clock, they signed the Armistice, which was a temporary ceasefire between Germany and basically England and the rest in Europe, which ended the First World War. And since then, we've actually celebrated First Armistice Day and now Veterans Day on November the 11th. I'm talking about giving thanks to people. And as we're all gathered in one place for the only time today, I would very much like to do that. Could I ask people here who are active or ex active or reserve in any of the armed forces, please to stand up? Come on. I just want to... So those of you who stood, if you can, on your badges today, right in what branch of the service you served or serve in, everyone else look for those badges and walk up and shake hands and say thank you. Good idea. Thanks. So Chad said come along and talk to the conference and I said okay, but what do you want to talk about? And, you know, it's the 10th conference you would think that we need to talk about the history and everything else. And Chad said, no, just basically talk about what's in your head. And it turns out I can actually do that. This was actually taken almost exactly 13 years ago to the day. I had a sinus infection. And it wouldn't go away, so they did a CAT scan and that revealed something. So I went in for an MRI, which is kind of cool. So this is an MRI of the front of my head. The big white things obviously are my eyeballs. You got my nose in the middle. You can just about see my jaw at the bottom there. It's kind of fun because they do like slices this way and that way and all kinds of ways.   I kind of got like this sort of Darth Vader thing going on, which is fun. Go back just a little bit more. Now I turn from Darth Vader into that kind of alien thing in Predator, right? The guy with the, which is also kind of fun. You keep going back a little bit more. This is kind of like round about here. Just about our interest. Any doctors in the house? Okay. Because there's something a bit weird on this.  Because remember my eyeballs were white.  You may notice there's a kind of asymmetry here. There's that thing in the middle of my brain. It turns out that I have something called an arachnoid cyst, which is the membrane around my brain kind of went the wrong way. And it kind of bulged into where my brain could be and my brain didn't grow there. So I am actually missing the majority of my left temporal lobe, which is kind of freaky when you first discover it. Part of my brain is missing. I asked the doctors, they wouldn't do it. If they'd be really cool if they'd put a door or something in there because I could store my keys and things, but no, they wouldn't. So they were kind of surprised to discover that I had this big hole in my head. Because they basically, so I said to them, was this like something that's growing? And they said, no, because you've had this all your life. It's perfectly normal, not normal, but it's perfectly stable. And I said, well, how do you know that? And they said, because if it developed after you were an infant, you wouldn't be functioning.  But they then said, but you know, we want to do some tests. Because why not?   It's kind of like a three day IQ test.  So like all the spatial stuff, all the word recognition also sounds absolutely fine. And in fact, they gave this little histogram of all my scores across all the different ranges, and it goes down, down, down, down, until it gets to one. My memory, or more accurately, my free recall memory doesn't exist.  For memory. And that explains a lot because I've always had this really, really weird memory.  But if someone said to me, like, you were, you know, do you remember when you were doing this, then I could normally fill in the blanks. So memory was in there, I just couldn't get to it.  It also explains why I've got this really you may have noticed that if you're talking to me in a crowd, I quite often just sit there and nod. It's because I can't hear you. I don't have this thing called cocktail party effect. Because that's audio separation is done in there as well. And I don't have that. So I actually cannot hear distinguished voices if there's more than one voice going on at the same time, which is kind of fun. Good excuse just to sit there and zone out. So because of this, I am exactly the wrong person to give any kind of opening historical remarks. Fortunately, though, I work in an industry with revision control. So I can give some historical stuff. And that's what I'm going to do. I'm gonna go through just real quickly kind of very personal, what I've been doing for the last 10 years because what I've been doing for the last 10 years apart from the book stuff and the consulting stuff is pretty much predicated on my Ruby life. And so I'll just go through that real quickly, show you some stuff. And then second part of the talk, I need to do my normal harangue the audience act. So in the last 10 years, I first came to Ruby in 1999, it might have been the end of 98. But I think it was 99, who can tell. And I came to Ruby because I was one of these people that loved programming languages. And I used to download all these programming languages and try them out. And normally they wouldn't last more than an hour or two. Ruby lasted a day, I phoned Andy and said, this is really, really cool. You need to play with it. And we got play with it. I haven't stopped playing ever since. Back then, if you typed Ruby minus V, it would say Ruby 1.4. How many people here have used Ruby 1.4? Matt has Chad has Ruby 1.4 was sweet. Right. It was minute. You can actually get your brain around it. It was like, you know, the download was like, I don't know, 107 bytes or something. It was a really, really small bit of source. But of course, that didn't last. But it doesn't matter because we loved Ruby. Now, at this point, we just finished writing Pragmatic Programmer and we were about to write a book on executable specification, the idea of writing something that specified the problem you're trying to solve and actually then run it to verify that it did what you thought it would do. Kind of like what aspect Cucumber have become, but with a different emphasis. And Ruby was the language. You're going to do it then. And we were going to write a book about it. And we started writing this book and we discovered that we had to keep explaining what we were doing in Ruby. So we started producing this little website of what is Ruby to kind of as collateral for the book. And it turns out that that got bigger than the book and was more interesting in the book. So we started putting that together in the book. Of course, just to make things interesting for us, Matt goes and releases Ruby 1.6 in 2000. But that was okay. It was still fairly small. And out of that came the first edition of programming Ruby. The first edition of programming Ruby, if you haven't seen it, is about half the thickness of the current one. Part of that's because the libraries are smaller, part of it's because it doesn't cover as much stuff. It doesn't have like meta programming and stuff in there. It doesn't have testing. But it was still out there. This book absolutely totally flopped. At the time there were probably, this room would probably represent the people doing Ruby in the US at that point. It really wasn't a big, big deal. But it still was a very satisfying book to get out. Just some numbers. At that point, the core of Ruby, if you downloaded Ruby, you got roughly 960 methods in 69 built-in classes. So it wasn't small, but it wasn't big. So one of the things we really wanted to do was to get Ruby out there, get it more popular. We convinced Addison Wesley to let us release the book in HTML form. So I spent a couple of months converting it from LaTeX, which is what it's written in, into HTML. And we put it out there, and you can go find that on like Ruby Doc and everywhere else now, which is kind of fun. The other thing, though, was in order to write the method reference, I actually had to go through the source code line by line and work out what every single method did. So probably for a time there, I was probably second to maths in terms of my understanding of what actually happened inside the interpreter, because I had to read the whole damn thing to understand it. And I thought, I don't want to do that again. So I tried an experiment in social engineering. What I did was I went through the interpreter source, and I took all of the documentation that I'd written for the book and put it into the interpreter source in a different format. The format I called RDoc for my Java doc, it was Ruby doc, called it RDoc. And the intent was that if I put the comments in there, and if those comments were useful and up to date, then when people made changes to the interpreter, they'd also update the comments. And that way, I wouldn't have to do it again in future. It took about two, three months to go through and type all this lot in, but when I finished, I think I had every single method documented inside the interpreter, both in the C code and also in the Ruby libraries. So this is from fine, for example. I also had to write the tools to extract this, and this is where I'm going to sort of like reveal all. RDoc was a, as I said, it was a social experiment. And as such, I think it's worked. I think now it's unusual to find people writing Ruby code that they don't document with comments. You expect to be able to find the API online somewhere in whatever format it is. That's actually great. I really appreciate it. Plus, the core team, the Ruby core team, are now documenting all of their methods using RDoc. And it's great, right? It's in there, and it means that whenever you get a new release of Ruby, you're getting up to date documentation with it. Here's the secret.  I wrote those as quickly as I could. I just basically messed around with the Ruby parser that was built into IRB and sort of hacked that so I could do the source code. It was an abomination. It was really, really bad. The only reason I did it was because I really needed something to get these comments and to explain to show people how it was useful, right? It would be actually usable in the field. And I've been waiting for years for someone to actually work out that that particular emperor had no clothes and to rewrite RDoc and IRB. And I know Eric has a talk coming up immediately after this one on his work on that. He's actually taken on that challenge. What he's doing is incrementally improving what's there, which I think is a very brave thing to do. But I really appreciate that because it desperately needs doing. But I'm still very pleased to the fact that RDoc actually has survived and is actually doing what it's supposed to do. So after writing the book and doing the RDoc and HTML, we've been writing books then for about three years. We were broke. So I went and got some work. And the next thing I worked on was a web app. This is in 2003. It's a web app called Dion. It's for a schools program called Destination Imagination. And I went back and looked at this. I checked it out of version control. I haven't seen it for like five years. So I went through and had a look at it. And I was kind of surprised, I have to say. Any directory tree that's dumped out of TextMate looks like any other directory tree. But it's still interesting that I have like an app directory, a DB directory. BO is Business Objects, which is kind of like my model directory. There's quite a lot of sort of common things in there. It's a fairly big project. 36,000 lines of code, 44 models, 100 something controllers. But the fun thing is, if you look inside it, you see some wild stuff. So here, for example, is a database table definition. Does that look familiar? It's, I mean, there's only so many ways of doing this. So it's really not surprising that it does look familiar. But there's some interesting stuff in there. For example, I chose to encode the lengths of fields as a parameter to the type. So I'd say varchar 100 as opposed to string lidesk comma length as 100. It doesn't matter. I mean, it's the same concept. That's kind of fun. I even had things called migrations. I had controllers that subclassed application. Again, not really, you know, rocket science. Something that was interesting, I still don't know if this is a good idea. I came across this, like I said, I'd forgotten I'd done this. And it's kind of like, oh, not too sure. If you defined an inner class inside your controller called app data, then the system would automatically persist that between requests so that you would actually have effectively accession related data per controller that was stored. And that makes your controllers look a little bit different to a Rails controller. I don't know if I like that or not in retrospect. It was kind of a fun idea. My actions in my controllers are a little bit different to Rails ones, but it was kind of like the same kind of idea. So this is like in Rails you'd have edit and update as the two actions. Here I have edit product in the product controller. So I go and fetch my product out of the data. I add some, I create a hash of options. I add that into the display hash for that product. And then rather than calling render, I call standard page. And then the equivalent of the update method is called handle edit product. And if you ignore some of the housekeeping, it looks pretty much the same as it would look nowadays in a Rails application. Which is kind of cool. I'm not saying this is actually clearly a lot, lot worse than anything that you do now. But it's just kind of interesting the way that the function that you need and the constraints that you're working under on a web application kind of drive the design. And it's interesting how you can have parallel paths arriving at kind of the same point. So skipping forward a little bit more. My life had become too easy and too sweet. So Max decides to mess it up by releasing Ruby 1.8. Ruby 1.8 was a big, big change. A whole bunch of new stuff came along. If you look in terms of method accounts, we went from around about the 900 mark, 800 and something in Ruby 1.4. Now we're up to 1140. Some new built-in classes. It got a lot bigger. What was worse from my point of view is we also now knew how to use Ruby a lot better. And so the book had a whole bunch more crap in it based on how we now use Ruby. So the page count went from being a fairly manageable 860 up to something like 960. Which is kind of scary. But that's okay. We got the book out in 2004, 2005, around about that time. And everything was absolutely wonderful. Until this happened. Some little upstart from Denmark put this video online on how to build a blog in 10 minutes. And the world changed.  And suddenly a whole bunch of new people came along. And I was really excited because Rails was a really great way of solving a problem that we all had. So I thought that was really cool. Looking back this almost looks quaint. Notice they hasn't got migrations or anything. And he's using scaffolding, which, you know, dynamic scaffolding. So there we go. The entire thing in 40 seconds. Why is that video only 40 seconds long and the original is nine minutes and 47 seconds?  Use Rails. Yeah. Like my haircut. All of that kind of stuff. All of that stuff came out, you know, left with this. So that's it. So obviously Rails changed Ruby, or it changed the Ruby community. It brought a whole lot of people into it. If you actually have a look at the graph of even just book sales, it goes from this and then accelerates off like a jet taking off. I loved Rails. I think it's a very, very, I still think it's a very cool way of doing web apps. So of course we have to write a book on it. And of course the original book was that thing, really easy to write. Also around about this time, Mike Clarke, Nicole Clarke, started Pragmatic Studio. So Chad and I and Mike coming out there, helping people pick up Ruby, pick up Rails. To date, we've done about sixteen hundred students have been through the studios and hundreds more have attended conferences. So that's been fun. And of course David, not to be outdone by Matt's, starts revving Rails. And I'm sitting there busy trying to do catch-up. The only reason I'm really showing this cover is that, do you find this cover offensive? I got the weirdest email set from about this cover. We released it as a beta book and I get this email from someone saying, is it possible to order one without the terrible new cover? I'm not too sure who's that supposed to attract twelve-year-old girls that are into boys and professional web development. If I need to, I suppose I can Photoshop the cover of the first book on and glue it on so I won't be quite so embarrassed. Then I sort of come back with some kind of like don't worry about it. He comes back with another email. Personally, I think the cover with some pink unicorns and hearts would be perfect to attract twelve year-old girls. Then it gets creepy. Others get a distinctly, yeah, others get a distinctly Nambo, Dambla vibe from it.  For the rest of you naive people, it stands for the North American Man Boy Love Association. This was the subject of much discussion over dinner that night with my wife. Then it gets creepier. We get another email about two days later from some totally different person. I wanted to thank you for the great cover on agile web development with Rails. I don't even program, but when I saw those legs I just had to have it. Well, long story short, a few of my friends got together to make a tribute. Could you please pass this on to legs for me? And there was a link. And the link was to a page that contained copies of the covers of the book with softcore gay porn on it. So my wife gets a little bit, you know, incensed and does the old Google bit. Turns out the two people that sent me the emails actually both lived in the same place on the east coast and now both live in the same place on the west coast and they're friends of each other on LinkedIn and everything else. So this is kind of like a little bit creepy. But just to let you know, this is the kind of stuff that can happen. One of the best pieces of advice that Alison Wesley gave us when we first wrote the book is never use your real address. And now I see why. What else happened around that time? Well, we actually developed our online store. This is a Rails application. Obviously it's about 60,000 lines of code. It was initially developed with Mike Clark and myself. And since then we've had Michael Kosciowski working on it and more recently James Edward Gray's second is working on it. This is really cool. It runs our entire business. I mean basically everything. You see the store side of this. Behind the covers it's doing the catalogue stuff, the sales stuff. It's interfacing out to the back end systems like Amazon and stuff. It does stock control, international rights. It's a cool system and it's changing all the time. So we would not have been able to do that without Ruby and Rails.  Moving forward, 2007, Ruby 1.9 comes out. I was really excited because Ruby 1.9 had a whole bunch of really cool new features in it. The sad thing is it kind of fizzled. And I think it fizzled because although the language is ready, the language is absolutely rock solid, the libraries weren't. The chances of you being able to take your existing application and just install the gems that you needed that would work on the Ruby 1.9 was pretty much zero. And because you didn't have the libraries and the gems that you needed, you wouldn't be able to use this. So it was a bit of a toy. And that's been really upsetting because it's such a great, great Ruby. However, that situation has changed. This, again, more stats because guess what? We have yet more growth. We're now to about 1,370 methods and 10 new classes. A lot of that has to do with the new encoding support, the multinationalization support that's built into it. Anyway, over the last two, three years, people have been working like crazy to get Ruby 1.9 usable in terms of libraries and everything else. And this August matched released Ruby 1.9.2. And at the risk of sounding like Steve Jobs, it's the best Ruby ever. I am absolutely serious. I mean, I know Chad's been using this this year. I've been using this as my exclusive Ruby all year. I've not had any problems. It is gorgeous. Absolutely. How many people here are using 1.9.2 as their main Ruby? Okay, about maybe a quarter, a third. If you're not using it, please, please switch across. It really is pretty painless. You'll find it's such a gorgeous experience. It's faster. It's way more capable. The regular expression support is great. The new enumeration stuff is unbelievably useful. They'll change the way you program. So please switch across to do it. So to kind of support that, we've got a new version of the Ruby book out. Hey, that is now supporting Ruby 1.9.2. Some stats, yet more methods, yet more classes, actually no more pages in the book, which is nice. But here's the wild thing. While I was typing this graph in, I actually did a quick regression on the number of methods and found something really wild. This is the number of methods in the Ruby interpreter. It actually fits a polynomial growth, not just like it fits it. It fits it almost perfectly. Like it fits it so perfectly. This is a science experiment. You get arrested for faking your results.  It's almost impossibly accurate. Maths could not have done more accurately if you'd tried. Add one more method and it would be worse. But the nice thing about this is we can now predict ahead and we'll know that the next version of Ruby has almost exactly 2000 methods in it and the one after that will have close to 2500. God help us. Anyway, just like a little bit of, I really, really want people to use Ruby 1.9. So like I said, today we're actually releasing the 1.9.2 version of programming Ruby. It's available in paper and PDF form. But I've been beaten up over the last year because all of our other books are in EPUB and mobile format so you can read it on your Kindle or your iPad. So I spent the last three months retyping the book from LaTeX into our production system so now the book's available in Moby and EPUB format. And if you read it on iBooks, you'll find there's an Easter egg in the reference section. It's kind of cool. If you already have the electronic version of the book then this is just a free upgrade because it's counted as a new printing not a new addition. So at some point this morning we're going to switch this on and you'll just be able to download it. Do not do it over the conference network please. But like I say I really really want people to use Ruby 1.9. I really want to give some kind of incentive for people to do that. So what we decided to do is we're now going to sell the paper book and the PDF for ten bucks. So I may well be taking a collection outside on the last day. That's going to be while the first printing lasts. But we'll see how it goes. Like I say, if you don't, I really wish that I put a submission for a talk into here on why I love Ruby 1.9. Because there are so many good things about it. You really should look at it. It's so cool. All right. So that's where we are now. What's going to happen in the future? I have no idea. I have no idea. If I can't remember the past I most definitely can't remember the future. But I'd like to spend some time just setting out a few challenges. Three challenges in particular that I'd like to give to you all. The first one, I call inspire somebody. It's not going to look like I'm talking about inspiring someone for the first few slides. Bear with me. I am. Because it starts out with this slide. I hope you can actually see that. The Bureau of Labor Statistics goes out in polls to find out what's happening in the real world. And it turns out that in 2009, out of the working population, roughly 47% of the working population of this country are women. They then break it down per industry. And the industry that we're in is computing and mathematics. In computing and mathematics, only 25% or roughly half the population norm are women. This is not great. But weight, as they say, there's more. Kelly was kind enough to do some analysis of this conference. If you look at this conference, 5.6% of the attendees are women. So out of a population of 25%, then roughly a fifth of those would be here. If we were a population norm, there would be five times as many women in this conference. And that's sad. It's shocking. But it's not as shocking as the next number. Because if you look at open source in general, Floss is the European free slash Libre open source. This data comes from a report that European Union commissioned on open source software. It's called Floss Pulse, which is a ridiculous name, free Libre open source software policy survey. And they came up with the fact that in open source, there is only a 1.5% participation rate by women. So if you look across the board, you have 47% in the working population. You have 25% in software and mathematics. Down to 5%, 5.6% here, down to 1.5% across the board. So I want to address that. To address that, you've got to find out why it happens. And clearly there's two things that are happening here. First of all, there's this population change from 47% to 25% taking place and people actually entering the industry. And then you have this problem that of that 25%, only 1 in 5 cares to come to a conference like this. Why is it? Well, the Floss Pulse survey has a whole bunch of reasoning behind it. They talk about implicit pressure during your teenage years. The old girls don't do this pressure from teachers and this kind of thing. There's this perception, which is probably not necessarily an untrue one, that software is lonely.  And there's also this fact that now that we're here, it's actually kind of like a de facto male dominated. It's not necessarily an attractive industry to enter. Interestingly, it wasn't always that way. Sarah Allen pointed out to me that the original ENIAC programmers were mostly women. Grace Hopper wrote the first compiler. It's just over the years, it's changed a way. The survey has some interesting, if hard to read conclusions. Women are actively, if unconsciously, excluded rather than passionately disinterested. The effect lies within the Floss cultural and social arrangements. My bold, the exclusion happens among people who do not mean to appear and who do not interpret their own actions as hostile to women. They also talk about this hacker ethic. The idea that we're cool, we can control the universe. We're hackers. But to us, it's almost like us versus the mainstream. We're different. And to us, women are part of the mainstream. And so quite often when women are introduced, if you like, to projects, it's almost as they said here, they become the carriers of sociality. They bring the outside in. They're not part of the community. And as a result, we tend to kind of let ourselves go a bit. There's a whole bunch of inflammatory talk, inflammatory presentations. There's, I actually had some websites on here that I took down because I didn't want my picture appearing with the website thing. There's websites like Testically, right, which is a PHP website.   Right. How would you feel working on a project called vagina? So there's stuff we can do. Is it a problem? Well, regarding the open source community as a whole, have you ever observed discriminative behavior? The audience, the 21% of the audience said yes, 75% said no. Looks pretty good until you realize that's what happens if you ask the men. If you ask the women, it's almost exactly the opposite. So my takeaway from this is, first of all, the Ruby community is not in a bad position. I think we actually do better than most when we have our mistakes. But I think we do better than most. But the problem is, even if we're well intentioned about it, we don't always know that we're doing it. So one of the things I would like to do is to try and change that to try and put a little bit more self awareness into all the little things that we do so that we don't drive women away. Possibly a test is when you're thinking about what someone's doing or what you're doing, rather than casting it as male female, cast it as black white, because we've all been kind of like trained as the wrong word. We have better empathy, better sympathy for that particular situation. So someone puts up a slide deck to talk about, I don't know, background worker processes and shows pictures of slavery. Maybe you'd go, not quite right. Yeah, if I talk about priority cues and show segregated bathrooms, you know, blacks, whites, you'd probably go, that's not quite right. It's exactly the same thing applies. And what I'd like you to do is to start thinking that way. And then if you do find something offensive, if something starts triggering that little spidey sense, do something about it. If you're in a talk and it's offensive, stand up and get out or blog about it and say, that was ridiculous. I'm not going to go to that. Tweet the guy into the oblivion. Please react, not just sit there and passively accept. Because by reacting, you're saying, yeah, it happened, but you know what? We're not going to let it happen again. So that maybe will take the 5% and move it closer towards the 25%. But what are we going to do about the 25%, about the long term, the picture that we're not getting women into software. And that's ridiculous waste in so many levels. Well, here I'd like to make a suggestion. I think what we need to be doing in general, in the software industry in general, is be talking more to kids. Fewer and fewer people are entering software as a profession. And fewer and fewer of those people are women. So I think mentoring is a really important part of what we do. There's a really great example from a guy called Scott Thompson who actually lives down my way in Dallas. He got involved in something called the Girls Engineering Club. It was a club that was started at his girl's school. I believe they're at about 10 years old, something like that. And he was drafted in to teach these girls programming as part of their engineering. And so they all turned up at someone's house and they carried in a whole bunch of, you know, old equipment and set up in a kitchen table. And he wrote a blog post about it, which I strongly recommend you go read at some point. In the middle of that blog post, he said, using shared screens and my iPad as a presentation controller, I walked the girls through the keynote presentation about some of the basic concepts of software engineering. Then we fired up Ruby in IRB and I showed the girls how to work with numbers, variables, and simple control structures in Ruby. They had to sit three to a computer, but that also let them help each other out. They learned to use loops to print out silly things about me. For example, I had the computer print out Mr. Thompson rocks and the girls felt they absolutely must get their computer to print Mr. Thompson, certainly not rock a thousand times. There was an awful lot of giggling, but as a teacher, I was proud to see them pick up the basic concepts and apply them to their own goals. My favorite exclamation was, wow, I could use this to help me do my homework. At the end of the article, he says this, with the girls engineering club, I got to experience a little of that joy of discovery once again. The price was a little elbow grease, some careful thought, and a bit of my time. It was absolutely a bargain. I agree there is nothing cooler than teaching kids. And so one of the challenges I'd like to set for all of us is to go out and inspire people, inspire a new generation of people who will come along to software. And why am I saying this at a Ruby conference? Well, the answer lies in cosmology.  I prefer the one from the Planck project that says, during the beginning of the universe, 10 to the minus 33-ish seconds or so, it underwent something called inflation, which is actually a phase change. In the same way that, for example, water turns into steam. It's a change of state. The same thing happened to the universe. And in the same way that steam is something like 1,000 times less dense than water, it expands as you heat it up. The universe expanded, expanded unbelievably in less time than exists. I mean, from a phenomenally short length of time, the universe expanded. And what happened is during that expansion, the universe was basically homogenous, but there were quantum fluctuations in that goo, in that foam. During the expansion, those fluctuations effectively got frozen. They got far enough apart that they couldn't kind of blend back together again. And it was those quantum fluctuations in the initial foam of the universe that they now believe led to galaxies. Just little deviations from regular uniformity eventually created the galaxies that we live in. The same thing applies now, I think. Ruby is now no longer a little niche thing. Ruby is now an industry. It's a standard. We are growing. We are growing phenomenally. When we do the studios, it used to be that people who came along were hobbyists. Now the people who come along are being sent by their companies. Ruby is growing and growing and growing. So in the same way that small changes at the beginning of the universe lead to galaxies later on, I think that the changes that we make today, the small changes that we make today, can lead to major changes in the industry for everybody down the road. And so I really would like to encourage you to go find someone to inspire. And here's Sarah. It's talked again to Sarah Allen about this. And she tacked on, I love this.  Go for it. Second challenge, diversify. Now here I'm not talking about the composition of our audience. I'm talking about yourself. The cheetah. There are about 10,000 cheetahs left in the world, which is kind of sad. One of the reasons that there's not that many, apart from mankind, is that sometime, a few thousand years ago, one particular mating pair of cheetahs became effectively the Adam and Eve for all current cheetahs. And what that means is that all current cheetahs are effectively clones. They actually share almost identical genes. So when cheetahs breed, basically the only surprise they're going to get is boy cheetah or girl cheetah. He looks just like his father. It's guaranteed because there are no other genes. You're not suddenly going to get a white cheetah or a redheaded cheetah out of that genetics. Technically it's called homozygous. The two genes that go to a loci are always going to be the same. And that leaves cheetahs susceptible to disease. It means, but significantly, they cannot evolve based on reproduction. The only evolution you're going to see is based on mutation. So it's a very, very fragile existence. Now, in the software world, we have exactly the same thing. We call them Java programmers. Or we call them C-sharp programmers. Actually, no. Let me be accurate. They call themselves Java programmers. They call themselves C-sharp programmers. And here's the bad secret. They call themselves Ruby programmers. Whenever somebody identifies themselves as I'm an XXX programmer, well, what they're saying is, I'm monolingual. I have one tool and I will use it, whatever. So if you look up monolingual in my dictionary, you get a couple of different things. Firstly, there's an unbelievable arrogance to saying, I know the right language. I know the right tool. Because you don't. But there's also a remarkable ignorance about it as well. Because with all due respect to Ruby, it's just a programming language. And if all you know is Ruby, then you don't know, for example, what it's like to do functional programming. You don't know what it's like to do logic-based horn clause programming. And if you don't know that, then you are not going to be writing programs well. Because you haven't got the experience to do so. There is another word for people who are monolingual. It appears a bit further down the road. But we call them maintenance programmers. Because eventually that's what you'll be. Because eventually everything moves on. The same applies, not just the language, but to everything. Anybody who just says, I know the way and this is the way I'm going to do it. I've just spent four years learning how to do this object stuff. I'm not going to change. Why should I throw that investment away? Those people are dying. Please don't become one of them. So my second challenge is to push yourself to learn. Learn a new language next year. Go for something which is different from your experience. If you've never done functional programming before, maybe do a Haskell or a Scala. If you haven't done a Lisp-like language, look at Clojure or Common Lisp. Just choose something different and learn it. But don't just sit there and read a book about it. Actually code in it. And code something significant. I put 3,000 lines. I have no idea what the number's supposed to be. But something which is actually big enough that you've got some experience at the end of it. And then ideally, ship it to someone.  What's the risk of doing this? Well, people will argue the risk is, oh, I haven't got time to do that. Well, if you haven't got time to train yourself, then find a different industry. No, the real risk, I think, is that people say, I might like it. I might like it better than what I'm doing now. And I don't want to do that, because really I like Ruby, or I like Java, or I like C Shop. It's kind of scary to think that there may be something better out there. But you know what, if there is, take it. I do this, I keep coming back to Ruby. But I program Ruby differently because I do this. If you don't want to do that, we live in an industry which never looks back. I would strongly recommend that you should. Look at some of the original languages that got us to where we are right now. Simulow, the first object-oriented language, is a very, very cool language with a very weird syntax. But it's well worth learning, just to see how things could be. And Simulow has concepts that we don't have in modern programming languages. It's very cool.  You can find them yourself as well. Find languages that maybe you haven't even heard of. And just look at them. Don't just do this with languages. Do it with everything. Try new things. Experiment. Because that way, you're introducing diversity into the gene pool. And that way, you can do this fitness function thing to say, does this work well for me? And that way, you can evolve. And that's what we're trying to do. So related to that is my last point. And that is, get out of the rut. I have used this slide, Chad tells me, on every single one of my RubyConf talks. I believe I used it on the very first talk. Back in 2000, the idea was that we were all pioneers. We were setting off into the unknown. We had no idea quite where we were going or what we were gonna do when we got there. We just knew that we had to do something.  And after a while, everybody found somewhere that they liked being, or maybe the horse died or whatever it was, and they started forming little communities, little towns. So we'd have the web development town and the testing town, whatever it might be. And that was kinda cool. You had other people, and it was like you didn't have to get on the horse every day and ride. It was cool. And after a while, those towns started getting a bit fancier. More people came. There was a bit of specialization going on. We could have nicer things. And after a while, the popular towns started growing and growing and growing. And then, after a while, not everywhere, but some places, this started happening. Sorry the video's not so great. But we started seeing suburbs forming. Kinda taking over the land. They look almost like Petri dish things, right? They take over the lands around towns. And suburbs are kinda like the opposite of getting into your wagon and exploring. A dear, dear, kind, sweet, gentle man once wrote a wonderful blog post. I think he even mentioned me in it. It was wonderful. Well, if I was so inclined, I might write this. Or that's not fair. But I would definitely write that. I think Ruby is in danger of becoming suburban. What do I mean by that? Well, kinda cookie cutter. Everything tends to look like the next thing. And because of that, it's homogeneous. Not too many surprises are happening anymore. We used to have all these cool things that would pop out. And people go, that won't work. And then it becomes like the next big thing. That doesn't happen as much. And one of the reasons it doesn't happen is that once you get comfortable, you start getting judgmental. You start saying, well, that's not how we do things around here, son. And that stamps on innovation.  You go, oh, that day, if they can't do that, we always do testing. That's all we've always done stuff. That's the way the Ruby community does it, yeah? Because we don't even think anymore. We just have this cookie cutter thing going on. And then what happens is, once you get sitting in this rut, we have to do something to make it interesting so we invent all these complicated structures around it. And things become high ceremony. Nowadays, it's not uncommon when you start a new project to download 40, 50 gems just to get the thing off the ground.  To me, that means that things are becoming boring. One of the problems is that we have a whole bunch of incredibly smart people in this community. A lot of them are in this room, but across the entire Ruby community, so many brains. And so many of them are just spending their time fine-tuning other people's ideas. Why? Because they're smart enough to say, I could do that better. And you know what, they can. Absolutely, of course they can. It's always easier to refine something, it's always easier to do something better, but so what? So instead of saying, I could do X better, my third challenge is to start doing something new. And to make it an absolute challenge, do it worse, because that is where pioneering happens.  Pioneering happens where you don't have to be perfect, you just have to survive. Do it worse and do it new. And along the way, please remember that the whole reason we're doing it is to make it fun. And that's it. Thank you all, I had an amazing 10 years.


Good morning, everyone. We are thrilled to be here. This is our first open-stack summit that we've held outside of the United States and it's Looking to be an excellent one. We are going to have over 3,000 people here this week from 50 countries and 480 cities. So every summit that we've had has been an international summit and has had participants from dozens of countries, but this one by far tops them all in terms of the representation that we have from communities all across the world and and that's really I think such a great thing for open-stack and really for the industry overall. So thank you for being here. We're all very excited to have you join us this week as part of the open-stack community.


What's good Josh bull rocks back again with another video, so I'm gonna check out ricochet bonk compilation ricochet He is someone that will do whatever he can to make you look like a million bucks If you're in the ring with them and that is always a good Trait to have when you are a wrestler you want to make sure your opponent looks Just as strong, you know or sometimes depending on the size difference You may want to make them look a little bit more imposing like their moves do a lot more damage It's the art of selling and if there's anybody that can sell and take a bump It's definitely ricochet, so we're gonna check this out. It's gonna be some crazy ones, man Appreciate all the love and support you guys have shown on the channel. Don't what is going on? That was weird job.  That's the first time that's ever happened Don't know what that means. Hope that's not a bad sign of anything, man We're gonna keep our fingers crossed shout out to the homie that does the the the WWE best moves man linked to the original video will be down below. We're gonna check this out. Let's do something He was selling all over Still one of the best sequences watching that live I couldn't believe what I was walking away. What the What? It's like him and Super kicks especially when Adam Cole is giving them just don't really fare too well, but just super kicks in general He's about to get super kicked out of his suit And a good match, too Someone that big doing that is Oh You know ricochet is good I wouldn't even try to pause it right there, but he's really good at the facial expressions, too Like he will sell the dead fish stare like he's really good Love it Oh Ricochet jumped with it to give that extra Out of the other side Here's the thing about this and I once again got to give him credit He's so athletic he can jump in do those over rotations to make all your moves look that Devastating that is what makes him a good opponent for a lot of people to wrestle against especially the big guys that don't have so much of the Athleticism rather than the size like somebody like a Braun Strowman can benefit having a match with him because He's gonna oversell. He's we're not oversell, but he's gonna he's gonna over rotate on moves He's gonna really sell the impact. He's gonna jump with the moves to make them look that more devastating Like that you make that look better than it could have been Oh My god Look at the dead That form was cold because of how ricochet flipped with it They had a good series of matches to Oh He makes you look like a million It's going to take a lot Still one of the greatest RKO sales of all time it's still I don't It's up there with the Evan born RKO in midair. It's the way he sold this RKO I don't think we will ever for a very long time.  He like I missed it, but he's like he landed on his neck.  That was very Man may not like Logan, bro. Once again, he shows he he can he can go in the ring, bro Hey, man, this video is great just going down memory lane and in seeing How ricochet made all these guys look like a million damn Bucks and that's one part in one aspect of wrestler. So comment down below Let me know what's your favorite bump and or sale From ricochet in any match that you can think of that he's ever been in one of my favorites Obviously, it's that RKO where he looked like he damn near broke his neck And of course the infamous Adam Cole superkick right at the right time Fantastic chefs kiss beautiful, but I appreciate all of them. So what you guys showing on channel wrote 250k I'm still young speedy you to wrestle champion world. Appreciate you're kicking me. See you next week. Peace


Everybody forced here ripping a box of 23 24 boom and chrome University basketball delights for JD. Good luck JD. Let's do it, man Let's do it That brawny James took that dual LeBron brawny Okay Refractor of Omaha bill you Isaac McNeely Darren Green Sean Stewart auto's El Marco Jackson First woman base all solid one there salted connect Decent auto and refractor up next. I think yep first woman auto Garway dual Number to 250 Garway dual to 250 Blue wave to 199 Solomon ball blue lava. Sorry blue lava Johnny broom to 399 of the purple True blue to 199 Kwame Evans purple mini diamond Zach Edie out of 399 and Green max Amos number 24 of 99. That's a decent box. Shady. Nothing too crazy Some good names in there though appreciate the order as always, but we'll get these out to you