So I had a totally different video planned, but then the Super Mario 3D All-Stars news continues, and this is I would say somewhat negative news depending on how you look at it. You guys have seen the headline by now, but hey you know what despite that we're still giving away three copies of this game through a Gleam.io link down in the description. We also have another giveaway for a Switch Lite and two games of choice for second place winners. Laundry list of ways to enter down in the description as well. The primary ones being subscribed to the channel hit the bell icon. You also get 15 extra entries into every giveaway we do by joining our Patreon at Patreon.com slash Nintendo Prime for as little as $1 a month. Alright, enough of that. Let's talk about what's happening here. So Oatmeal Dome over on Twitter. For those who don't know who Oatmeal Dome is, he is in the hacking community. He advertises himself as a Switch IOS macOS tinkerer covering data mines, leaks, rumors, Nintendo industry news and more. That's kind of what he does. He's just firmly planted in the hacking community amongst all those devices. Now I want to note before I talk about this that the hacking community isn't always a bad thing. I know I'm really against game leaks.  I hate that. I think that's just a slap in the face to the developers. Also, it only happens because somebody who has a copy of the game leaked it and sometimes this comes from media members, other times it comes from retailers that illegally sold the game early. In fact, I know there's actually been some Walmarts in the United States that have sold some copies of Super Mario 3D All Stars already. You could try your luck and see if they're willing to do it in your area. But I don't really care if you do it and get it. I care that you don't leak it to the internet. But all games end up on the internet eventually, especially once launch day comes. And Super Mario 3D All Stars is no different. According to Omiel Del, I got his tweets on screen here. So Super Mario 3D All Stars has been leaked onto the internet. Now again, hate leaks. I hate when games leak like this, but we do learn some interesting information and that's what we're going to go over today. All the games are apparently emulated. Galaxy and Sunshine run under a Wii and Gamecube emulator named Hagi, possibly made by nerd Nintendo of Europe Division. Mario 64 is running under an N64 emulator, but they can't tell which emulator it is. It's some new emulator obviously that they've never seen before. Galaxy in particular is actually extremely interesting because they recompiled the original code to run natively on the Switch CPU. So those A57s that work or whatever. Those ARM57s. But everything else, the GPU and audio is running in an emulator. So it's kind of weird. The Brux of the game is running natively on the system, but then the actual visuals are in an emulator. It's kind of interesting.  About the N64 emulator, the Shindoku pack ROM is used. So we're talking about this emulator. We can't really tell what it is. So it's a ROM. There is a ROM. So if you're wondering which version of the game it is, it is the Shindu pack ROM. The texture code and translation patches are all applied on the fly. So the first person camera has inverted controls versus the original for some reason. But yeah, they're literally like, it uses the Vulkan API too. That's a strange thing about that. The Vulkan API is being used for Mario 64? Why? Interestingly, the code patches are done through Lua. The emulator takes over execution upon after reaching a certain PC process and transfers control to the Lua script. Also, whoever made the emulator configuration file made a typo. They spelled the word canon as canoe. Hack the canoe up the river. That's hilarious. Gotta love those typos, make it into code. I doubt it breaks anything in the game. It's just kind of a funny thing, especially with the codes written. It's not a piece of code that runs as a script. Other minor tidbits. The project codename potentially is Stardust. It is located in the files. They also might be a sub codename for Galaxy called Shiguro. You would assume that's a reference to Shiguro Miyamoto. The menu that lets you choose games is made with lunch pack. For those who don't know, lunch pack is actually an internal engine at Nintendo. He mentioned this used by Splatoon, Mario Maker, Animal Crossing. It is Splatoon 2, Mario Maker 2, and Animal Crossing Horizons uses it as well. It is one of several internal engines that Nintendo has. I can't remember what the codename is for the Breath of the Wild engine. Nintendo is an interesting company. They're one of those game makers that make their own game engines. They make quite a few of them. They're not like Ubisoft or EA where they make them. EA's got Frostbite and Snowdrop with Ubisoft. They take that engine and try to apply it to everything. Although Ubisoft is still using some of the Anvil engine for some games. But it's interesting that Nintendo does that. Nintendo has been dabbling with Unreal Engine 4, so you can see that applied to more games. But that's got nothing to do with this one. Lunch pack is how the menu is done. But I think what's interesting is that the games are emulated. Now, I had a sneaking suspicion. This was the case when they announced it because I mentioned maybe the most disappointing thing when this pack was announced was just how little work it seemed went into it in comparison to pretty much all the other old games that have come back. We've got the Crash Bandicoot, we've got the Spyro Trilogy. We've had all these other games come back. And we just have seen much better remasters or remakes if you want to go. Final Fantasy VII is maybe at the top of that list. We've seen Nintendo even do better with these games and they've brought them to platforms like the Nintendo 3DS. Let's forget what Activision and other companies are doing in Square Enix. Let's just look at what Nintendo has done. Ocarina of Time brought over to the 3DS, completely redid the visual style, added some new features. Majora's Mask brought to the 3DS, completely redid the visual style, literally added new content into the game. Fishing is now in Majora's Mask in the 3D version. Was not in the original. A whole new area. Right? You know, they brought Mario 64, I think back in the day, over to the DS, added a few new features. It's weird to me that Nintendo has brought these games over to other platforms and simply straight up added features. I mean, this isn't Nintendo per se, but even Hyrule Warriors, like the Legends version was brought over all new content, new features like Nintendo has done, you know, or been part of these jobs where they take their old games, they bring them to new platforms, especially like the N64 and up home console games. And when they do it, they tend to do more with these games.  Super Mario 3D world that we're getting next February, they added new content. They potentially tweak the game because it looks like it even runs faster. Like you literally move faster in the game, not like a faster frame rate, but like the speed of the characters is faster. These tweaks don't appear to be present here. It looks like it's just an emulator, you know, a few emulators, just running these games with texture packs, like HD texture packs. That's what it looks like. And it's been kind of my one criticism of Super Mario 3D All Serves from inception, was that, not really inception, but I guess from, you know, because it's been, we've been conceptualizing this, you know, for a while since the rumors came out back in like March, but it's baffling to me that Nintendo didn't put more effort into these games. Now, the thing is, I'm still going to buy them. And my reasons for buying this collection pack might be different than other people's reasons, because I do believe that Nintendo should do more, but they're not going to. Obviously, this is what we get. They're not going to do more. And millions upon millions of people are perfectly fine with that. The reason I'm fine with it is because Super Mario Sunshine, to buy it on like the second hand market, it's like over 100 bucks. It's one of the harder to get more expensive GameCube games. And I don't have it. I played a little bit of it as a kid, but I don't actually have the game. So I really want to revisit it. And I could technically do it illegally. I could just get a ROM, but I don't believe in the emulation ROM crowd when it comes to just playing games illegally.  And then you want to do some fun things with it. Great.  That's fine. You know, do, do that stuff and insert Shrek into the game. Like that's cool. But do whatever you want with your own legal copy of the game. But I don't believe in these people that download these ROMs and just never buy the games or like, you know, even download the ROMs, you know, and can't find their copy of the game.  But you know what, I just don't like the emulation ground and I don't own Super Mario Sunshine. So I'm not going to go download it and play it illegally on my PC. It's just not something I'm interested in. So that's the primary reason that with the price of it on the second hand market that this is worth it to me. And obviously you add on that I don't have to do any modifications to it. I don't have to install any mods. It just will be in widescreen at 1080p. That's great. And I get the other games along with it. There's also obviously the collector in me. I'm obviously a Nintendo collector. You guys have seen some videos where I've been on camera and you'll see, you know, a gaming collection of stuff behind me. You guys know I like collecting things. So obviously there is the fact that this is a limited time release as much as I don't like that Nintendo's made it a limited time release. We can't help but notice that despite being a limited time release, that just makes it a more collectible game. It's just a more collectible collection. That 35th anniversary, uh, notations on it. The 3D All-Stars, uh, you know, logo. It's a collectible now. I own Mario All-Stars back on the Dance Nest. So I might as well own the 3D version. So as much as I'm against these practices, you can call me hypocrite for still buying the game. I just, I can't help it because I have other reasons that I was going to buy this game anyways. You know, I always was going to buy this no matter what Nintendo did with it. It's just, I would appreciate a little bit more effort than just literally emulating the games and just running HD texture packs, basically. And they're using all the original code. I mean, it's just, it's fine. It's cool.  I think I actually have one more, uh, kind of negative story about 3D All-Stars today. It feels weird. We go from positive stores to negative, but you know what? That's just the way things ebb and flow, you know? You know, I got, I got three, four videos coming for you today. So there'll be something positive in there somewhere, I'm sure. But, anyways, thank you guys for tuning in and I'll catch you in the next video.


Hi, this is your host of Limbhakti and welcome to another episode of TfL. Let's talk and today we have with us Nima Nikban Co-founder and CEO of Karnataka Nima is great to have you on the show. Hey, thanks for having me It's my pleasure to host you today This is the first time she and I are talking on camera and before recording as we're talking You know the company has been around since 2010 as you said Which also means that not only you folks predate a lot of modern shiny technology like Kubernetes You have seen also a lot of evolution and today we are primarily going to talk about like Generative AI and the fact is that a lot of industry they have been using AI already You know security has automotive healthcare, but generally I has kind of opened a new kind of like floodgates So there is so much to talk about today, but before we go there, I would love to know a bit about the company itself What was the idea behind the company because you're a co-founder So why you created the company back in 2010 and then we look at 2023 How do you have seen the evolution of space and the evolution of company itself? We started in 2010 as you mentioned and we actually were part of a DOD research project and that goal of the project was Consume hundreds of different real-time data feeds and then be able to give a query capability To analysts to data scientists to developers to you know quickly be able to deploy stuff into the into the field And at the time, you know You know no sequel was all the rage Hadoop was all the rage There was still the big warehouses that the legacy warehouses like the terror data's They all really had a huge amount of trouble dealing with real-time data and being able to do complex query They could do a few things they could do a lot of pre-planned things where they did a lot of indexes and you know Supplemental data engineering to make it happen But to be able to really find that needle in the haystack to really be able to do whatever you want Across all that data as it continued to flow.  So what if we flip the equation on its head? Let's make a database that's for you know Allowing data to continuously stream in to be able to write any query you want without data engineering and leverage all of this Abundant compute in a distributed way In a way that allows the developers the data scientists They know to ask any question they want and get back responses quickly with up-to-date data And that was the basic premise behind Connecticut And we started building, you know in 2010 and you know, we became the you know analytic engine for You know the speed layer for that program where we were sitting on top of actually, you know, a cumulo And and you know doing all the analytic temporal and spatial work for for that project over time You know, we we went into you know, larger large enterprises like USPS, which is one of our first flagship customers Where you know again, they were Doing something that really required a new type of solution. They said hey, we put sensors on every mail carrier We need to be able to analyze this in real time And it looks like you're the right solution for that. And you know, that was one of our first major wins and from there We really focused on becoming a You know real-time speed layer for the modern enterprise So are you mostly targeting the public sector government entities? No, I mean, we have we do have a big DoD Customer base, but we also have financial, you know large large banks, you know large telcos Anyone who's you know trying to take advantage of real-time data from sensor and machine where they want to be able to do advanced analytics that you know potentially fuse that real-time data against, you know, historical data sets to be able to query it without, you know, any type of Limitation and have it be up-to-date have it be performant.  If you look at modern word It won't be wrong to say that we live in a data-driven world apps can come and go all the time But data is I mean as we say data is the new world, but you know, that's that real asset How do you've seen the evolution of data and when we talk about real-time data? I mean, of course we can look at EVs, smart cards I mean everything, you know, we are collecting and generating a lot of that and sometimes a lot of things have to be done Real-time. So I just want to understand the evolution of real-time data, but sometimes what happens is that there are a lot of technologies Which continue to co-exist where some technologies evolve, you know, so they transform I just want to understand the role importance of real-time data real-time data has is really starting just starting to kind of Get its foothold in the modern enterprise. I think, you know, really it started as You know, very simple calculations that just looked at, you know, the the latest, you know record that would come through and have a, you know, have a very simple, you know You know threshold-based, you know rule-based, you know analysis And it's evolved to a place where it's really the, you know, the the ability for your You know, your data team your your your enterprise to understand what's going on in the business in real-time So to be able to query it not, you know, not just in a window But to query it, you know across all of the activity that might be happening over, you know Several months or a year and be able to fuse that against other data sets That's really where real-time data is going so it started out as something really simple like hey Let's look at the last five minutes of data and run these rules, right to now where it's gone to a place where this is How we understand what's going on our business in real-time We need to be able to query it not just within the last five minutes But within, you know, the past year or multiple years have it be up to date be able to fuse it against other data sets that may be historical or real-time and really Be able to be creative in what we can produce because that's going to give us that extra advantage and be able to, you know Give us that, you know, that next level of efficiency that everyone's striving for It won't be wrong to say that we live in a data driven world How have you seen the evolution data, especially real-time data with the emergence of new use cases And if you can also talk about What do you think is the rule of real-time data in this modern economy?  And we'll put it all on, you know, back then HDFS and we'll figure out how we use it later You know, I think we've gotten to a place now where, you know There's a lot better understanding of of the data inventory of a given enterprise And things like, you know, Databricks and Snowflake have done a really good job of kind of being that You know, authoritative data store for all of the data and making it easy to do kind of the static or batch like reporting and analysis And, you know, I think there there is now, you know, that next That next iteration where we fit in where it's, hey, we've we kind of understand, you know How our data plays together, right? But now because we've analyzed it on a static basis And now we got to put this into action where, you know, I can give my You know, my C-suite a single pane of glass where they can understand everything that's going on in the business And not just have static KPIs that are that are, you know That are being maintained but allow them to double click, right? And be able to ask the questions that they that we didn't think to ask beforehand, right? You know, that's really where that ad hoc query capability that speed layer Capability to do that on real-time data. That's that's where we fit in And I think that's a lot of, you know What we see is the evolution of the like the database space on that kind of capability level, right? Where, you know, we've done what we've done so far has done a great job at dealing with static problems Or dealing with questions that we know people want to ask and now it's getting to okay I've got something where the the data is constantly changing And I don't necessarily know all the questions that need to be asked in the moment And I need to be able to deliver that capability and that's where I think there's still space for innovation Where else do you see the scope of real-time data beyond some of the use cases that you mentioned Or some of the use cases that is Traditionally associated with yeah, I think there's there's two things there I mean one is the expanded role of vector search and embedding generation, right? And you know a lot of that is best run on the GPU And that's something that we've been focusing on is you know making it really easy to do You know large-scale real-time embedding generation doing doing very powerful brute force GPU vector some vector similarity search And you know that that alone is something that you know the GPU is you know really You know unique in and it's ability to do but then also you know It's ability really to brute force calculate, you know in brute force process data Really fits in well with what what we're what we were just talking about which is with LLMs People are going to be able to ask questions and generate code that that you know sequel or whatever it might be that you know, you know Codifies that question and they need they want to have an answer quickly And you might also even have a world where LLMs are talking to each other And you know, they need to be able to say okay, I need to know, you know, how many packages are You know available for delivery in this area, you know, whatever it might be You're going to see that need to be able to run ad hoc query You're going to see that need explode, right? And again, the GPU is really purpose built for being able to do you know massive processing without having to pre-define and pre-plan queries and indexes You mentioned vector search Can you talk about how our vector databases and knowledge graphs being used for Insights on structure data versus the more common language use cases? Yeah, I mean so like with with knowledge graphs, you have, you know The ability to find more Entity correlations, right where you have in the generative case really in a heightened Entity, you know, an entity detection and classification capability from text now knowledge graphs are then being used to To take whatever the user put in tie it to what entities might match via, you know A vector search and entities detected and then pull out new relationships, right? And then, you know, again find more vectors off those, right? So with with knowledge graph and vector search together, right?  So, you know, I think with generative AI and thinking about LLMs You're going to get get to a place where it's, you know, much more advanced Fixed workflows like, you know, you can think like auto GPT where There's going to be need to be able to Connect to and query knowledge bases and those knowledge bases are going to be able to, you know Need to have multimodal capability, right to be able to answer things by finding Related entities via knowledge graph or, you know, to be able to pull out related time series data via vector search or, you know You know, there's there's going to be that need to be able to converge all these analytic disciplines And tie it with the ability to do it quickly as the data is updating because the LLM is going to need to, you know Have just like if you were you, you know a user you're going to need to be able to have the latest data and have it be You want it to perform quickly so you can take your next step without any contest Genitive AI is the hottest topic these days Talk about the impact it's going to have on your industry and your products Yeah, I mean there's two parts for us. I mean one is powering vector search, right? And, you know, we can do, you know vector search In ways that are unique as far as giving you added flexibility With the results of results of a vector search or the input to a vector search But also being able to do that in real time, you know, so not indexing and being able to do it at scale And leveraging the GPU That's something that's unique to us and, you know, really You know, that's something that kind of fits into the the generative workflows of today The other, you know, the other big part is having a language to SQL capability baked into the product So yes, there are other products that, you know, try to act as, you know Kind of an intelligence layer for multiple databases But we believe that it's also incredibly powerful to have that capability in your database so that your Language to SQL generates the SQL that takes advantage of all of your unique capabilities around time series spatial and graph So we bake that into our product, right? So you can, you know, literally say like execute question Give it a natural language question and have it return SQL for you and that and that's baked in the product, right? And that goes back to what we see as the future Which has been brought on by by this generative AI revolution, which is a User expectation that they can do ad hoc query just through natural language, right? And be that LLMs themselves are going to be, you know, you know, exchanging Needs and queries through natural language So having a database that has that out of the box that can bring all the different analytic capabilities to bear We think is going to be Any unique offering In general, what kind of trends are you seeing especially When we look at generative AI and what does it mean for kinetics?   But You know from there, you know, we're also seeing the need to be able to take that next step of okay Okay, you have vector search. Can you scale your vector search? Can you scale it with data latency? So all those are the things that are being, you know, competed for now and and that's, you know Where we see our our advantages being able to do it at scale being able to do it as You know, new vectors are being generated in in real time um, and and then on the actual, you know, large language model side, you know, there's I think a a Explosion of different opportunities going on as far as you know, first it was around. Okay, we want, you know We want to make co-pilots that, you know, help for code generation or Help for support, you know, but I think there's um A lot of innovation yet to be had on how do we use Generative AI and the large language model approach for enterprise and enterprise data, right? And that's where we're still I think in the early days How to separate hype from reality because I mean I cover all these emerging latest technologies Some technologies are just like a blip on a rotor But then many others which transform our industry if I ask you when it comes to generative AI Is it a hype? Or is it the next? transformative Devolutionary technology like docker container Kubernetes or the Linux kernel. Yeah, I mean, there's definitely a mix of both right like, you know I think when like chat gpt first came out like people thought out there's like this All-knowing all powerful lm that can kind of do anything And I think, you know, we're realizing, you know, especially as people understand lm's more and how they work that, you know There's really a limit to to how much they can do and you know the you know How you can use them to accomplish certain things right now that being said They still are, you know a tremendous capability that if you weave in correctly for certain Tasks or you know for certain, you know Really thought out workflows can can really deliver some amazing capability, right? So I think there's a lot of that still to be figured out of like, okay How do we how do we, you know weave this in into delivering a A still, you know, wow factor capability for an enterprise, right?  It's it's got it's it's definitely got it's like, you know Certain uses that you know if used correctly and and orchestrated correctly can deliver still some next level next generation capability But you know, it's it's it's going to take some time to to to cultivate that and figure that out But it's also not Just like stand this thing up and you know, now I've got this super Super intelligent brain that can figure out anything out, right? So, you know, I think I think anyone using chat gbt for for more than an hour or two can kind of see that, right? So, um, you know, I think it's it's definitely something that It is it is a little bit hype, but it's also there. There is there is a there there And then we look at these emerging technologies. It's very important for organizations to while stay on Trusted reliable technologies. They should have their roots firmly planted But they should also dip their toes In new technologies. How do you enable your customers to maintain the balance? Sure.   And so, you know, there's going to be um, you know different Different products and different comfort levels of using those products. And so we're really focusing on how do we support that Where, you know, we we can help support, you know You know doing large language model work by yourself or support working with other ones that might be hosted So we're really working, you know, also nvidia is coming out with their nemo cloud llm as well um, and we're focusing on, you know, how we interrupt with that. So um, we think there's going to be a kind of a whole wide variety of of uh, generative llm options and we're looking to really support all like we certainly don't think the answer is hey You know use kinetica l kinetica for You know making your own llms and hosting in there that that's not going to be the answer The answer is going to be, you know, much more varied Neema, thank you so much for taking time out today and of course talk about kinetica But also kind of, you know, broader discussions around generative AI. Thanks for all those insights and I would love to have you back on the show Thank you. Thanks for having me and love to be back on again


This has been your first ever time speaking at the 21 convention. Really interested in your thoughts on the event, what's your experience been like so far? Oh so far it's been fantastic. I you know I think viewers are probably going to see this or they're going to see the two speeches that I do but they don't understand the stuff that goes on behind the scenes here and there's so much more going on at this and I like I said this is my first time here so I can't really speak to the old you know older prior ones but there's so much else that's going on we have meet and greets I spent close to three hours in the the hotel bar here just answering questions and just talking to guys and just just that interaction the network I really I need that stuff I really do because it gives me material and it gives me like things to think about we've got you know Alan Roger Curry we've got Richard Cooper we've got Ivan Throne is here a lot of these guys who are you know fixtures I think anyways fixtures in the red pill community and it's not just about angry dudes you know spitting hate at each other spitting hate at women and stuff and I think anybody who would come to this who watches these videos or comes to these things you would know that just how ridiculous that idea is that all of us is just about about angry guys because the guys I meet and I'm again we've got some other events that are going to be happening that are off the the scene is like it's not just about talks I think that that's where a lot of the value of this particular conference is is in but I need that one-on-one and this this convention really really provides an opportunity to you know you can pick my brain I can pick your brain and the great part about this is I get that here you know I get the the one on one and you know people are throwing questions at me like I would I I would never would have thought of that if I hadn't been here awesome stuff man well Rollo thanks again for being here thank you being great and with that you can get first access to Rollo's talk on 21university.com all by clicking the link underneath this video and this is Mike signing off for the 21 report with Rollo Tomasi I'm talking with Rollo Tomasi from the rationalmail.com and he's written several books and you might have read them and you're aware of them and I don't want to go over that information because he's a dynamic person and there's constantly information and research coming out of this person's mind here and that's what we want to tap into today in a little chat and give you some hope as well. Welcome. Thanks. The speech went well. Very well. I gave my speech about the state of the mass fear the state of the mass fear address. I also is a really kind of turning into a resource of men's globalized universalized experiences online in various forums my you know through my work through other people's work through various podcasts I've got my own podcast right now going with the red man group and so it's not just one form of media it could be books it could be could be like said podcasting it could be coming to an event like this and learning about it so I mean that's probably the best way I can describe it.


My name is Tony Arsiri, and I am not an engineering program. I'm giving a talk on three of my projects today, Rev or Backer and Raya. But I kind of decided the standing scheme is a bit redundant. So I am renaming Rev, which is probably one of the least Google-level names ever since I know, I guess. So I'm going to now call Rev Coolio. So anyway, I really love network programming. Pretty much ever since I discovered the internet, my network programming has been my big thing. And I kind of get this idea, the most furious view of the world this way. You know, they really know their application, their web framework, and rack. And then below there everything is black box. And really quick, I'm curious how true that actually is. So how many of you have really dug into the source of any web framework? Pretty much anybody in the room, how about people who've dug into rack and see what's going on? How many of you have really looked at the source code of any web server really dug into it? Well, quite a few, that's a little bit surprising. How many of you have dug into VM? A bit fewer, but a bit more than I was expecting. How many of you have really dug into the source of the OS kernel? Yeah, a bit fewer there. So, you know, I really think there's a lot outside of HTTP. And most of the stuff that I was doing prior to web programming was not related to HTTP. So in 2003 I started this project called Distribute Stream. And the idea was it was a bit torrent but better. So I originally started writing a bit torrent library in C, you know, I saw. The bit torrent was originally written in Python and I was being seized all of it at the time. And I'm like, oh, rewrite in C for speed, it'll be faster and better. And as I started doing that, I really started noticing all these problems with bit torrent and I thought it's all better. And I spent about two years trying to develop a replacement protocol to distribute stream in C. I learned a lot of stuff about network programming in general, but didn't really make much of it. So in 2005 I had to step back and admit I'm not really being productive. I need to learn some new language that's better than C that would make me more productive. And there's this quote, I believe it's by Bill Joy, I tried to find it again after I first saw it, but I can't. But it gives a little something like, there comes a time in every C programmer's life when they realize that they've debugged enough memory leaks and enough arithmetic errors and written enough linked lists and enough hash tables, and they may have all done a language with a higher level of abstraction.  But I heard, you know, I sort of overlooking Ruby for that reason, but I heard about this new VM called YARV. And, you know, seeing that I'm like, okay, well maybe Ruby will be faster soon. And what really sold me on Ruby was Rails. Rails had just come out and started working for a startup company. And they wanted, you know, they wanted to do web programming and Rails was really good for that. So in 2006 I was working with the senior project team at a local university and I had them start rewriting Distribute Stream into Ruby. So I sort of had this idea that, you know, it would be a bit more to be the Python peer-to-peer protocol in Distribute Stream to be the Ruby one. And I was using the event machine to handle, you know, planning for massive numbers of connections. And the real idea that separated Distribute Stream from BitTorrent was that Distribute Stream could have this install be the entire network. It was all centrally managed. And then you could apply collaborative filtering algorithms like Slip One to sort of predict what the transfer rates would be between peers that they'd never have exchanged any data of. So at the same time I'm working with Rails and we were having a lot of problems meaning we were deployment. So, you know, the initial way that you could deploy a Rails app was with CGI.  And as CG came out, you might remember Lighty. A few people, wow. Lighty used to kind of be the main way that you were supposed to deploy Rails apps. So it was pretty good at the time for CGI. And it's another thing that CGI came out. But what I thought Rails really needed was something like Apache Poyote. Apache Poyote is an HTTP connector for Java. So it's basically your web app can talk HTTP directly. Sort of mold and writing that myself, but I didn't have to because it's a thing called Longroll came out. And it really came out in 2006. It's up through Evan's keynote. Sorry, Evan, that might have changed some things. I had actually seen it. So I was waiting for Matt to announce that Yard would be coming out that Christmas. So I was really expecting it for some reason. But that didn't happen. There wasn't any Yard. Where is Yard? And, uh, not being me, it's at Panda. But, uh, there was an open bar at the hotel when I started drinking. And then they had this thing where you could come ask Matt's question. I got a pink hider in it and Matt's, I'm sorry about that. I was a little bit drunk. But after that, I met this guy. You might remember him at the time he had hair. That would be Zed Shaw, if you don't recognize him. You know, I'd seen him earlier that day. And he got up in front of everybody. And he said, I'm Zed Shaw. And I wrote Longroll when I received thunderous applause. So, you know, people used to like Zed. So I can't remember him easily. Quite a lot of people care more about, like, speed and performance and stuff like that. Our Rails app is actually going into infinite loops to just deploy it on Longroll. If you ever install Longroll, you've probably seen this thing called the CGIEOF multi-part patch, I believe. And there's this bug where anybody can send an outform to a bus to your server and put an internet loop. And I started talking to Zed about, like, oh my God, you've discovered this crazy security vulnerability we're trying to keep under the wraps for now until we can get a patch out of it. And I was talking to Zed about the sturdy stream and using event machine.  And she worked on his project, which was Ruby Event. She was a writer-rapper for LibEvent in Ruby. And he had some problems with that. Never really done the work down. Never really did. So meanwhile, later at the conference, there was a number of board, I don't know if any of you know about this. But basically, Matt's employees, she got together on Sunday night. And I created this new repository for 1.9, sort of freeze commits to the mass branch and merge yarn into new. I don't know if I was in any way influential with that. But that was a really good thing to see come out of some of the conference. So 2007, you know, this project built on event machine. We're having some issues with the event machine. I became a committer. I tried to fix as many of these problems as I could. And basically, the code base is really hard to work with. And I just got really frustrated. So Rev actually, I didn't start. It was started by this guy named Frankie Rines and Shaw. It was to be a Ruby wrapper for the LibEV library, sort of like LibEvent, but maybe a little bit cleaner, a little bit easier to use API, that sort of thing. But both of them soon left, basically, before either of them had committed any code at all. So, you know, it's easy to complain about something like event machine in-house, right? But I think the best way to complain about stuff is to try to write something better and see if you can. So, Zed and I have kind of been friends, anyway, on any blog themes. So I introduced him to our designer, Rines Mard.  And shortly after she made that for him, Zed posted, you know, a blog post. I'm sure you don't know about it. But Zed was basically gone, leaving me, like, this Frankie guy disappeared. So, basically, I was the only one left here to try to write this name of that framework. So that framework is now clearly, you can find it on GitHub there. So, where are the kind of things you'd use it for, right? If you need to handle a large number of incoming connections, there's this whole C10K thing you might have heard about. Like, how can you scale to 10,000 plus connections, right? We're using something like a library like WebDB, you can do that. You have large amounts of IO, if your program is really IO bound, primarily. It doesn't use a lot of CPU. You know, this is something you could really look at. And the other thing that this is really good for is shared state between connections. When you have shared state and you're using friends, you have to synchronize it. It's hard, the concurrency is hard. And this lets you sort of eliminate the concurrency and do everything with callbacks. So, what sort of things would you actually write with this? WebSpiders is a big one. After DistributeStream, the next thing I used it for was my company and a lot of WebSpiders. I used Red to build a massively concurrent WebSpider. HDDB pushes servers to maintain persistent connections. So, again, it's going back to that massive number of connections thing.  That's a good shared state problem where you're trying to take some state and deliver it to all the other connections. So, RevSupported Platforms, it works on MRI 1.8.6 Plus. It also works on YARV. And now I finally got working on Revinius Head after some changes I made and some changes you made there. So, here's a quick crash course on event programming. So, normally when you're trying to get stuff off the network, you just call method and give it some prams and get a response. But the event programming, instead of doing that, you use these callbacks. So, if something's successful, you have a non-success callback. If something fails, you have a non-failure callback. Another way to do this is with a block. So, you can start your request and you get this response object back and you can look at that and go, is your request successful or not. So, event machine kind of reinvents the whole IHO layer. So, event machine is sort of originally conceived to be something like a multi-language event library binding. And it kind of didn't succeed at that for some reason. It only succeeded in the Ruby community. And basically it reinvents the whole IHO layer. I built the Coolio with the Ruby primitive. So, all the sockets that use all the IHO objects come straight from Ruby. The SSL stuff also comes straight from Ruby. So, there's really two things you need to know about Coolio. You have the event loop object. And this is the only thing in the entire library that are blocks. And then you have these event listener objects that you attach to that. And those are all in the blog. So, here's some quick example code. Here you have, this is your basic echo server. You have a connection class that has these three callbacks here. When something connects to it, when something closes from it, when something reads from it. And it's really simple there. Whenever you read something, you just write it back out, right? And then down there at the bottom, you see it creating the TCP server. You give it that connection class. And then you attach that to the event loop and run the event loop. And then I'll just sit there and block receiving incoming transactions. For getting HTTP, you have quite a few more callbacks. So this exposes a lot of the events that can occur throughout the HTTP request lifecycle there. So this basically will connect to a web server, make it get request and print out the results. It's also got file system monitoring. Anyone ever heard of Watcher? Yep. Few people. Yeah, cool. Watcher is built on rev and uses it for file system monitoring. So this guy named Ryan Dahl contacted me after writing this web server called Ev. He wanted to support using rev side by side with Ev. Ev was based on LibEV as well, so it seemed like a really good fit. And originally when I had backported, I wrote rev originally for 1.9 and backported it to 1.8. And Ryan actually found some really nifty tricks for interfacing with 1.8 scheduler and I adopted those into rev at the time. And then you know, Ryan kind of gave up on Ev. It never really got popular, but he took the ideas of having LibEV back end and created new .js out of that. So some next steps that I'd like to happen to Coolio. asynchronous file IO. So if you've ever used Node, everything is asynchronous. And to accomplish that, there's sort of this companion library by the author LibEV called LibEIO. It puts all these blocking requests into threat pools, so they can be asynchronous too. And then Roger Pack has offered a $50 bounty to anybody who will swap out the LibEV back in and switch it to LibEvent. LibEvent just has better support on Windows. So then I discovered Erlang. This book came out here and I read it and I thought Erlang was really awesome. I have a quick video to play for you here. It's kind of loud, so please cover your views if you don't like loud noises. Hey, do you want to feel so parallel? Erlang! I'm quoting the language for people who need gratuitous amounts of parallelism. It's almost literally hyperland. It's like adding parallelism to a pure Euclidean space. Sound of the alarm. You're going to be uncomfortably parallel. What's that? You want databases? We'll help out. Pedabases. Pedabases. Pedabases. Pedabases. You'll be good at them. It's a functional language for men. Monctional. Monctional. P-map puns. Functional. Functional. Parallel. P-map is our man. Four of us and you're the one who has the room for. You'll be so fast that Google will be like slow down. Parallel ports. So much parallelism. Yaw! And it's parallel. Search parallel, holy parallel. Parallel. Parallel. So many children. So many children. 4,096 children. Hyperland. You're children and they'll be good at databases. And children run abnormally fast. The run as fast as Google. What's the running thing? The Google. The run as fast as Google. It's actually Google. And it'll be a tie. It'll be the quarterback to battle with you. Or they don't gamble with parallelism. Awesome. So, we have a lot as originally, or I need to distribute a stream that is playing around with a bunch of concepts for how to use threads and how to do IO efficiently and how to manage CPU. And sort of the dream all I came up with was you have a single-event IO loop. You only run one thread per CPU core. And then to get higher levels of concurrency beyond that you use wide-way user-stakes processes. There's a couple tools you can use on 1.32. There's this thing called Fiverr's which would appear in Ruby later. And then on Unix there's these things called new contacts that you can use to do that. And both of those are basically co-routines. So, Erlang had really created a good implementation of this model because, you know, it blew my mind when I originally saw it. And at the time, YARV had gotten fibers. And so I tried to take the ideas of Erlang and build them on top of fibers. And on that Christmas, YARV was released and I was a happy band-up. So, in 2008, I released Revactor. And Revactor is actors for Ruby 1.9. So, one of my big motivations for this was I written a web-spire for a company in Erlang originally and my boss kind of found out and said I couldn't use Erlang so I decided to do Ruby instead. So, yeah, the basic idea is if you take co-routines and we're ever going to normally block if you're doing synchronous IO, but you can use fibers and you can switch back to other fibers that can do other things while you're blocking on IO. And this technique was seen later in a couple other libraries. As far as I know, it's the first one to do this. I was doing it on 1.9 before it was even released. But a couple other libraries that I'll never block in Unisynchronia and I'll talk about it in Unisynchronia later. So, you know, I really didn't like that model.  So, Revactor, it was the first I still think it's the most comprehensive solution for combining fibers and events. So these other libraries, they just, you know, give you synchronous IO on top of an invented backend. But what Revactor does is it lets you use fibers to communicate, or it allows your fibers to communicate with each other and block on each other and send each other messages. Here's a quick example of how you would write an Echo server with Revactor and really, you know, this looks exactly like the kind of thing you would do with threads, right? You have, you create a listener socket, you have a loop that listens for incoming connections and then it creates the, in this case, which is your concurrency-permanent events. It's there and listens for you, listens for the client to write stuff and just writes it back out to the socket. So since Ruby seems to love web apps a lot, you can write asynchronous web applications using this web server called Rainbows. And Rainbows is the Unicorn web server modified for asynchronous bus processing. And Unicorn, if you know, it will automatically spin up 1 VM per CPU core. So if you want to have a single web server that takes advantage of all your CPU cores and lets you do a venture of the programming, you can use Rainbows. And here's some quick examples that really love the Rainbows Bing function. It's pretty neat. But I don't really know how to use Rainbows and never really try this. But if you're interested in doing web programming with this, take a look at Rainbows. So I need a volunteer from the audience. David Tabor is already here. So we're going to do some live-action role-playing of the actor model. So come up here on stage. I have a couple of messages here. This one is a ray and this one is a hash. So I'm going to be off doing something, but come and put the array in my pocket. So yeah, I'm up here speaking. I'm up here doing my thing. Now I'm ready. And I'm going to look in my pocket for a hash. And all I have is this. So now I'm blocked. I can't do anything. So come put the hash in my pocket. And now I've got a hash and I'm blocked. But this list is back in my pocket so I can help me do my thing. Until I do care about a list, I know where it is. So that is my attempt at doing live-action role-playing of the actor model. So I'd love to continue talking about revactors, but I'd really like to get on an array. So if you want to know more about actors that are back there in general, there's a website for it. So you know, I really became disenchanted with this whole idea of faking synchronous eye on top of fibers. And I have another little video to share with you here to explain that. Are any obvious disadvantages to patching a blocking library? To use fibers at the socket level? It's far too much effort to have to rewrite large chunks of every library just to make it a sink and fiber aware. Just use threads. No, not a happen. Even if this is a personal project, I won't use threads, so I guess they'll just have to continue rewriting parts of a bunch of libraries as I go. Oh, wait. I remember who you are. You're the omniscient guy who needs rock to scale and you think threads are going to stop you from servicing your rock-millions of users. And I remember that you hate fibers for whatever reasons. I don't hate fibers. I just think a lot of people are misusing them for silly things. My boss wants all of my scalable async platform backend. And from experience, I'd rather wrap the async code in fibers than have tons of callback spaghetti. What scale are you really talking about? Because last time you just started blurting the word cloud with me like it meant something special. These can mean large scale, obviously not right from the beginning, but as functionality and the client base grows, it needs to scale up majorly within interfaces to pretty much every large social media-related sites on the web. Do you have any actual numbers or is rock to scale really the best description of your capacity plan? I can't talk numbers. The platform is still in early development stages, but it needs to be able to make many hundreds of requests in real-time. You don't know what the numbers are and yet you're saying hundreds of requests in real-time that can work just fine using threads. Okay, let's say thousands of requests in real-time per online client and it should give you a rough idea because it's too early in development to be able to be too specific. That just means you are doing no real projections, which means it's purely technological masturbation and it's the thousands of requests per client in real-time that's more than likely a completely silly sentiment for the plain and simple reason that a particular user is unlikely to even want to read all the results of thousands of requests each time they visit.  You should tell your boss to pay for some consulting from someone that's built these kinds of systems before you're already set in stone that you need raffle scale, which is both architecturally wrong and bad for the business, it's only because you want raffle scale that you seem completely certain that threads are inappropriate for your use cases. You really don't have any idea on the specifics of the system so you cannot judge what sort of scaling is required. You don't seem to understand what sort of scaling is required either and you clearly don't understand the difference between threads and fibers in this kind of context. I understand the threads have more overhead on fibers and any shared data would require locking and syncing. Fibers still share state and if you won't be patched at work libraries to use fibers it becomes hard to understand when your fibers are yielding so you still need locking anyway to provide transactional mutations to shared state. Fibers do not run concurrently. That doesn't change the fact that fibers still share state and by trying to stick or pretend synchronous API on top of things there's a sense of where context switches are happening and run a follow-up along with the problems of threads which will still scale very well. I don't care. Ruby on ground. I don't care. JRuby and Iron Ruby already support concurrent multiting without any sort of global interpreter lock and Rubinus will soon support it too. This means one instance of your application will scale across multiple CPU cores with a sync program that will need to run a separate virtual machine for CPU core. I don't care.  I don't care. To varnish cache which is arguably the fastest and best HTTP cache available uses threads to handle multiple concurrent connections. I don't care. Plansql which is arguably the most popular open source database in the world uses threads to handle multiple concurrent connections as well. I don't care.  I argue with people who think they need rawful scale and that fibers are the only solution. So yeah, that actually isn't a strong and argument there. Large parts of that are verbatim of a real YRC conversation. So, really what it comes down to is a principle of least surprise, right? Well like, on Ruby pretty much the principle of least surprise is not to use a benefit program and it needs to use threads. And if you want to do a better programming there is a language where events are the principle of least surprise and that's JavaScript and I really respect Node for that. Node really found, you know, Node just combined events in JavaScript in such a great way that it's awesome that I recommend Node. So what happened is Erlang kind of fizzled. It's not that it failed per se. There's a lot of really cool projects on Erlang. But all the hype eventually died down and saw this really neat passage from the book Coders of Work which I highly recommend. But that was just some of Joe Armstrong's thoughts on Erlang there. And at the end of that he said to make Erlang popular, you know, Microsoft might stick some curly braces on it. And I'm like, no, I could just use some Ruby syntax. So Zed Shaw, he's really passionate about languages, about getting people to learn how programming languages work and that sort of thing.  And what really makes Erlang's syntax bad is it's just adding insult to injury in terms of Erlang is just conceptually so different from every other language that when you have this like weird pro-audi syntax, it makes it that much more impenetrable. So I started working on Rea and started on it in 2008 and I really wanted to leverage Erlang's strengths. So Erlang's main one is non-stop systems. So, you know, you might have seen the Erlang claims that it gets 99.999, blah, whatever, uptime, but really the core idea there is that there's no theoretical reason why you should ever need to stop the Erlang VM. And real-time programming, together with the non-stop programming, really all the other ideas in Erlang come from these two ideas. So to have a non-stop system it really needs to be faultful and if you have faults and you don't tolerate them, your system's going to stop. Code swapping, if you want to make any changes to your code, you've got to be able to do that live and be able to do it trans-actually and inside a concurrent environment. And distribution is really the final strength of programming there. So I wanted to take Erlang and add Ruby syntax to it. The other thing about REA is it's an immutable state of language. And really, when you look at the whole functional language versus imperative language thing, I think the core idea there is really immutable state. That's really the only major difference between those two language families. I was actually talking to Brian Ford about it has been proven that the continuation passing style of functional languages is equivalent to the SSA model of imperative languages. Here's an obligatory Lady Gaga slide. So I presented REA at Erlang factory back in 2009. At the time I had a mostly working implementation and the big thing I was excited about was Erlang has this idea of a gen server where they take the actors of Erlang and wrap them up and make them into something that's almost an object. So I took that and actually put sort of a Ruby style class syntax onto it. At the time I had a web framework called Ryan. This is what really inspired me to do concurrent objects. I saw this quote from Alan Kay. He had this idea of objects really being these things that are sort of like individual computers. Web services are that kind of thing and they talk to each other with messages. So Node started blowing up in 2009 and it really got people interested in event driven programming. Which I think is neat because Node and Kalio share some of the same technologies. They share these same technologies although I haven't had the Libia for yet. But in late 2009 as I was working on REA it was the OMG too slow. It was really really slow as I tried to develop a standard library. It just wouldn't work because each file I added would take that much longer to live. Basically I really didn't know I was doing the first time I wrote REA.  So in 2010 I basically completed the REA or REA it's over 9000 times faster than I had earlier. I learned really how to write a language on top of your language by failing the first time. And I really started looking at the early compiler itself to get ideas. So I kind of tried to do everything myself the first time with their ideas. And definitely that was a bad idea. And the neat thing that came out of this was now everything in REA is an object. So originally I didn't have any sort of non-concurrent objects in the language but I ended up adding more of these immutable objects. So let's take a look and we'll see if that will work. Yeah. I also know how to live out there. A little bit smaller there. Can everybody see that? Oops. Alright, so here is the REA source tree. I'm going to start this thing called IR. It's just like IRB. So there it is, running on top of your language on there. So a quick first example, hello world. So if you're in Brent's talk you like this idea of putting puts on the end of things. And the main reason I do that is REA doesn't have a top of a little scope, mainly because Erlang doesn't have that. So if you wanted to actually do the more Ruby-like way, you'd have to do this. There's hello world again. So REA has this where this would be an array and review. This is a singly linked list that you can call out there on it like that. And I actually made this bank syntax first class here. And what that does is it actually modifies the receiver. So it's a medieval state language where you have to modify the receiver, but what it's actually doing is changing the binding. So the list is now bound to a new version of the list there. And the other neat thing it has is that if you've ever done a Python you might have reused list comprehensions in the past. Also there's two goals. Again, this is something you may have used from Python. But these are basically the equivalent of arrays as opposed to a singly linked list. And another neat thing it has is pattern matching so you can have these deeply nested structures. So what that's actually done is bound all these variables there. So it has modules just like Ruby, plus two, six n, plus two. So modules are just sort of like collections of functions. They're not quite as powerful as they are in Ruby. So you close two and get 42 there. So then the other thing is there's no real idea of re-opening modules or classes. So I can actually be class out of here. And the reason for that is sort of to get closer to Erlang's hopcode swapping semantics. So this is declaring a class of immutable objects here. So it did have this little shortcuts in the back here. So you can actually bind an instance variable directly from initialize there. And I can define a method here. What we've done there would be a variable names there or whatever. So the instantiation syntax, I do want to add .new. I don't have singleton objects yet. But so for now, do you instantiate something you have to sort of do or type on style there? Do you add to .add and get that? Lambda, so you can do something. So fun actually comes from Erlang, but if you've ever used Erlang, the fun syntax isn't very fun. What I've done is sort of taken the stabby lambda syntax from already 1.9 and adopted that. So I'll just do animals 2 there. And there's some indicycable Erlang about where in the code server that function happens to be located. And then the invocation syntax here is just like a pipe on actually. So you can just call it like that. So getting on to the naked concurrency stuff Erlang calls its actors processes I'm sort of taking that same name there. What I'm going to do is bind this to PID. And spawn is the method you call to create a new process. So when I reached into my pocket to check for those messages there what I was doing was this receive thing. And receive sort of works like a case statement, but you don't really need a case on anything. You're just kind of doing a case on your mailbox. So this is going to wait for a symbol called foo. And when it gets it's going to tell you I got a foo. There's not up there and that creates a new ID on there. And then to send that PID a synchronous message you use the bang operator there. So we're going to go ahead and send a foo and then what I do it says I got a foo. So that concludes my little quick tour there. Let me see if I can actually get back to Kina here. It's really quick. What's the mirroring thing? It's supposed to be command or control option command to eat. Alright so I don't know if any of you saw it but at RailsConf and at Oskon, Ilya Grugorin talked about EM synchrony and you know I'm not really opposed to EM synchrony. I think it's pretty cool but EM synchrony basically does the same thing as never block. Trying to take fibers and let me do fake synchronous IO with them machine. And the thing about it is he really started popularizing this ID and they're sort of doing it ever since. I think EM synchrony is mainly in the raffle scaling. He demonstrated things like Rails running on top of it. I don't think the vented back ends are really good for the typical things that Rails apps tend to do but because it's popular I sort of dust it off when I'm a backter. I try to modernize them. So if you're interested to check them out I used to like Ray a better. One of Ray's biggest drawbacks in recent history is I've done a really bad job of documenting it but created a new website sort of inspired by coffee scripts and I'm going to load it up with tons and tons of examples. So one of the neat things that is sort of being worked on right now but a few of the contributors on the project is a peg grammar. It's available here on GitHub. It's both on top of this this peg generator for Erlang called Neotoma. That's sort of like true top rate. And the peg grammar is being written by these two guys here and it actually has tests. I don't have any tests on the grammar it's all full of the other tests we have on the language. Some of the neat things that a peg could bring right now the current parser I've written has a lot of trouble handling white space. Removing semi-colons from the end of lines is surprisingly hard. It supports nested interpolated strings so while Ray has interpolated strings you can't nest them and with a peg that's pretty easy. And then everybody loves these like slash-limited projects literals but they're actually kind of hard to implement because they're ambiguous with things like divide for example divide equals. So a peg can really handle this well. And one thing I don't have on the slide that might be possible in the future right now Ray has mandatory parents on everything but with a peg it might be possible to remove those in certain cases. So some of my next steps for Ray I hear one of the things I've been working on lately is singleton classes as I was saying with .new I would like your people to be able to call .new just like a Ruby. I want to get the concurrent objects back that is something that is sorely needed because basically everything in Ray is either a readable data or a process. Name spaces, we all have name spaces and default and keyword arguments and finally I'm going to look at some ways to support meta-programming there's no way I can ever come anywhere close to whatever it has but I'd like to support some one-day cases of it. So one more thing before I conclude my talk here compilers aren't hard I know a lot of people think they're the sort of impenetrable black box but if you actually take the time and start looking at them and study other compilers you know really I had been afraid of it for a while but as soon as I did I discovered it's not that hard at all so I'd encourage you to create your own freaking awesome programming language there's a book by the same name that I would highly recommend as well if I can do it you can too alright


Hi and welcome to the session. I am Deepika here. Let's discuss the question which says for the following differential equation, find the particular solution that is finally given condition x sin square y over x minus y into dx thus x3 y is equal to 0, y is equal to 4 then x is equal to 1. Let's start the solution. Now the given differential equation is sin square y over x minus y into dx plus x dy is equal to 0 or this can be written as x dy is equal to minus of x sin square y over x minus y into dx or dy by dx is equal to y minus x sin square y over x upon x this can be written as dy by dx is equal to y over x minus sin square y over x. Let us give this equation as number one. Clearly this is a homogeneous differential equation. Now we will solve this differential equation by putting y is equal to vx so put y is equal to vx therefore dy by dx is equal to v plus x till v over dx. Now on substituting the value of y and dy by dx in equation 1 we have so from equation 1 v plus x dv over dx is equal to v minus sin square v x dv over dx is equal to v minus sin square v minus v over x dv over dx is equal to minus sin square v on separating the variables we have dv over minus sin square v is equal to dx over x. Now on integrating both sides we have integral minus sin square v dv is equal to integral of dx over x or cot v is equal to log mod x to the base e plus c. Now on replacing v by y over x we have cot y over x is equal to log mod x plus c. Let us give this equation as number 2. Now we are given the condition y is equal to pi by 4 when x is equal to 1 therefore we have pi by 4 is equal to log 1 to the base e plus c. Now cot pi by 4 is equal to 1 and log 1 is equal to 0 plus c or we can write this equation as c is equal to log e to the base e log e to the base e is equal to 1. On substituting the value of c in equation 2 we get cot y over x is equal to log mod x plus log e y over x is equal to log of mod e x the particular solution given differential equation under the condition y is equal to pi by 4 when x is equal to 1 is cot y over x is equal to log of mod e x this is the answer for the above question. This completes our session I hope the solution is clear to you and you have enjoyed the session. Bye and take care.


Would you like to be off the joint? No way. All right. Lord Gryffindor, Nebraska. Good to see you. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. All right. Thank you. Thank you. Thank you. Thank you very much. Well, I'll keep it short, but I'm going to take it short. I'll keep it short, but I'm going to say here to open this because I just didn't start serving until I do finish. I just wanted to see you all, have you here, and I know what the chores ahead of you are. And yet I think the importance of what we're doing, and maybe all of you are aware or maybe some of you aren't, is that for almost 60 years now the other party has controlled for most of the time both houses of the Congress. They've had more than half of that period. They've had democratic presidents, and all those democratic presidents only were faced with the Republican Congress for one two-year period, and that was in Harry Truman's time. And the Republican presidents, more than 20 years here, I had one house for six years. The House of Representatives was still the other way. And other than that, the only Republican that had a Republican Congress was two years that I had one. And we know what has been responsible for that, Gary Mandarin and so forth. We've got to whittle and get back. I can tell you, this period now, where they're back to having both houses, if we hadn't had a Senate for the six years we did, we couldn't have accomplished any other things. I don't believe that we did accomplish. It's just the difference of night and day now.  I don't know what you're saying, but it's so important to not only get a president, but then I think the argument has got to be to our people. If you're sending a president, it's the only one that is voted on by all the people. The only one that the whole population elects. Then does it make sense to send up congressmen and senators that are dedicated to opposing him in the things that he said he would do? So we've really got it tough. And the last thing I'd like to touch on before we eat and get into all the rest of the meeting here is the importance, and particularly when there was a little fiction or friction, I should say, that came into the present primary. Back in 66 was the birth of the 11th commandment, and it came from California. And I was running for governor at that time. I have to tell you that that made all the difference. Our party at that time was so split in California after the bitterness of the Goldwater campaign with factions that had grown up. And Justice of Indian came up with the idea of the 11th commandment, and then God bless our ladies, federated, limited Republican federation. They passed a resolution that they would not support the nominee of our party if that nominee had violated the 11th commandment. You never saw a primary that was conducted so much aimed at the opposition, not of your own party, but of whoever was going to be the nominee of the other party. And it brought the party together. And I remember we followed up to the point that the night of the primary when the election results came in, and I knew I was nominated, we called San Francisco where we knew they were having the same kind of a hearing meeting there. And got on the phone the people that were had been the high ranking people in the campaign of the leading contender there, and asked them and had the jobs picked out specifically of the same importance that they had had. That we would like to have them join our campaign in that role. And in those jobs. One of those was Cap Wainberg. Yep, that's right. I can't believe you had a question for Reagan. Not originally. No, it's been totally... Cap was for Rockefeller and the Goldwood. I know, there's no telling how much mileage I can get out of it. Well, listen, I think I'd better stop here and let us get on with lunch. All right. And then when lunch goes on, usually these people, they have to go to meetings. Burnley, who's the director of our victim services? Good to see you. I'm very pleased that you could be here. And... Okay. And Rick Abel, who is the assistant attorney general in the charge of our justice management division. Well, good to see you. Thank you. And these are the award winners, Clementine Barfield here, who was founded an organization to help victims of crime. And I want you to have one of our buttons. To help us save ourselves into orders. Well, thank you very much. I'm pleased to be able to present you with us. Thank you. And next is Frank Barnaba, who was founded an organization to help the victims of child abuse. Great pleasure. Great honor. Well, it's so important that you read it. Thank you. Next, we have Colonel Pruitt, who has... Hello there. He's representing Citizens and Victims for Justice Reform. And this is the award for the organization, which he's accepting on their behalf. Congratulations on behalf of Kentucky. So thank you for allowing us to be here. I think you know Ken Ikenberry here, who is an outstanding district attorney. I mean, attorney general, excuse me, who has done a lot for victims of crime as a leader in the National Association of Attorneys General. Thank you, Mr. President, for your supportive victims work, too. Well, I'm very pleased and very proud of what all of you are doing. Thank you very much. All right. Next is Jan Emmerich here. And Jan is one of our real leaders in the U.S. attorney's offices as a victim-witness coordinator. And she's been particularly effective with the Indian victims in Arizona. Well, and again. Congratulations. Thank you for your support. Well, thank you for what you did. And last, by no means least, is Sarah O'Meara. Hello there. I just saw you four days ago. How lucky can you get it? And she's the co-founder of Child Help USA International, working with children victims. There. This is such an honor, Mr. President. That's right. I didn't know that at the time when I got here. But you'll not know what your presentation looks like every day. Mr. President, we have three family members here. This is Mrs. Barnabas. We met her husband earlier. Very important, Mr. President. And we have here Mr. Emmerich and their son. Tony. Tony. Tony Emmerich. Hello there. Hello there. Just one second here, gentlemen. And I guess they're going to be a group picture here. I see a hole in the middle of that question. But I'm sure you won't know that I have signed this proclamation that this is the victim's week. Mr. President, we appreciate your time here. I think every year now, since you've been president, or virtually every year, you've signed that victim's proclamation. I know you've had an interest in this from our California days when you were governor. But we appreciate very much your support of this program, both budgetarily and otherwise. And we particularly appreciate all of these people as representative of literally thousands of people around the country that are now working to help the victims and the potential victims of crime. So this little ceremony here, while necessarily short, is I think very significant for people all over the country. Thank you. Thank you. Thank you. All right. Thank you, sir. Give me a seat, our fan. Mr. President, good morning. Good morning, Mr. President. and some of the others. Distinguished lawyers and leaders of the Bar and the White House, and I know one of the most fundamental of the self-evident truths set in our Declaration of Independence is that governments derive their just powers from the consent of the government. I have enjoyed telling our young people between us and some other countries many times when I got to go to schools and talk there.  And it's why, under our Constitution, we, the people, grant a limited sphere of authority to the government. In other countries, it's the other way around. The government gives some limited authority to the citizens. But I think also the theme of this law day, this particular law day, and that is the importance of voting is something that I think we should take very seriously. I think when we notice and look at recent elections and how great a decline there is in the number of people voting, I'm reminded of what Will Rogers said one day. He said that the people we send to public office are no better and no worse than the people who send them there. But they're all better than those who don't vote at all. So I think this whole theme here of emphasizing the importance of voting, I encourage you to do as much as you can on that. That is the thing most necessary today. And now I've talked enough, I'll start writing. The proclamation on May 1st, May Day is going to have a different meaning in this country than it has elsewhere. It will be law day, our law. So thank you all for coming in. Thank you. Thank you, Mr. President. I did get caught on the down princess of Japan. Ours is the only constitution there were to be passed. It says we, the people, tell the government what it is. That's very nice. I don't know if you have any questions. That's very nice. That's very nice. I'm going to turn to World War II. The Japanese changed the country. That's very nice. World War II. That was something I had in mind. Well, Mr. President, thank you very much for launching us this way. And this voter participation is a program we are pushing in everywhere in the United States. What was it? 53 percent of the votes. And you think that down there in El Salvador, gorillas were telling the people that if they voted in that election, they would be killed. The woman was shot and stayed in the land for hours refusing the other treatment. And Joseph got lured. And they had over 80 percent of their people. But the worst part is our young people, only 18 percent are voting there. And voting blocks, 18 to 24, are political connections. But we have the greatest percentage of that. And as you say, the lowest percentage actually voted of all these people. That's the value. That's the future. Yes.