We're going to get started. But before I get started, does anybody here play Ultimate? Does anybody know what Ultimate is? This is so sad. So I've been playing Ultimate for most of my life. It's a disc sport. I will say the terrible word frisbee. So I've been playing for most of my life. And I've been fascinated watching the sport grow. Because when I started playing, like the typical response is the response I got here and nobody knows what this sport is. But now it's actually like on ESPN3 and it's getting lots of public attention. It's probably one of the fastest growing or potentially the fastest growing sport. But just last week, the U23 Worlds was in London. And India competed for the first time ever. So Sushmita Azad from Bangalore said that being part of India U23 team means that I get to represent India in a sport that is the microcosm of the ideal world. There are no referees, no body contact, no heckling. Just highly competitive play, which only works because of the integrity of everyone playing. And so I think that has a lot of parallels to the communities in free and open source software. So I brought a few jQuery disks to give away after my talk. Do you want one? Throw it to you. Come see me after the talk. So it seems appropriate that I would be giving a talk about the community here at the first ever jQuery conference in India because India actually accounts for 13% of sessions across all the jQuery foundation sites, which makes it the second most active country following the US. And for comparison, the third most active country, Germany, only accounts for about 4.5% of sessions. So broken down by a city, Bangalore is actually the most active city, not just within India but across the entire world. And India accounts for six of the top 10 cities. We do the Bangalore, Chennai, Hyderabad, New Delhi, Mumbai, and Pune. Also, we have three projects going on right now in Google Summer of Code. And two of the three students are from India. So it's pretty exciting to be part of this conference with such a vibrant community, even if it turns out that all you do is go to Stack Overflow and steal answers. So as an open source project, jQuery UI benefits quite a bit from the contributions of the community. And despite the relatively small size of our code base, we have a lot of moving parts. It takes quite a bit to keep the project running. We are, after all, the most popular JavaScript UI library in the world. So we're quite fortunate to have a very active community as a result. Nearly every aspect of jQuery UI has been created or improved by hundreds of individuals, from bug reports to patches to documentations. We'll find community contributions in all the normal places. But the community contributions actually go well beyond this. We have logo designs, site designs, site implementation, we have style guides, language guides, event organizers, people answering questions on Stack Overflow, forums, IRC, testing pre-releases, giving feedback on proposed APIs. The list goes on and on for community contributions. So there's been increasing awareness recently that successful projects are built on more than just code and creating a welcoming environment for everyone, not just developers, is very important for their community and the project. So it's something we've been passionate about since day one and we're glad to see that more projects are taking strides in the right direction. And in fact, one of the contributions that had the biggest impact on me wasn't code, it wasn't even a traditional type of contribution. At some point during the 1.8 release cycle for jQuery UI, Andrew Powell mentioned to me that our upgrade guides weren't very good. So I took a step back and I read through our upgrade guides from the standpoint of someone that's not intimately familiar with the code base and it was very obvious that he was correct. So at that point, I started to really understand how important high-quality documentation is. And this made a big impact, not just on jQuery UI, but in a lot of my personal projects as well. And as a result, we received fantastic feedback with the 1.9 upgrade guide, which was massively more detailed than any previous upgrade guide we had written. So even just providing feedback is an important contribution and it could be something that sparks a change that could affect hundreds, thousands, or even millions of other individuals. So beyond just the individuals that participate in our community, we also rely on lots of other projects and teams. We rely on services and projects such as Git, GitHub, WordPress, FreeNode, Travis, Jenkins, QUnit, TestWarm, Node, NPM, Grunt, W3C, TC39, JSCS, JSHint, CSSplint, PhantomJS, BrowserVendors, plenty of other projects and teams. Let's just go on and on and on. So as you might expect, there's a lot of overlap in these communities. So contributions to one project often have a widespread impact that have affect other projects and communities. So over the past seven years, members of the jQuery UI team have been active in several of these communities and building upon these existing projects and sharing our own contributions enables us to improve the landscape for more than just the jQuery UI community. By fostering a collaborative environment and ensuring that we have open lines of communication, we're able to solve not just our own problems, but those of other projects and teams as well. So perhaps one of the most illustrative ways to explain why this is a natural thing for us to do and how we've helped build up the community is to just walk through a typical day as a jQuery UI developer. So let's say I'm working on a bug fix. I'd probably start by writing a test and we write our tests in QUnit, but we support several versions of jQuery Core and currently we support 16 versions of jQuery. So manually running the test suite against each individual version is pretty tedious. So a while ago I created an extension for QUnit that lets you run many test suites and then it aggregates the results and then you can see them in, basically creates a new QUnit test suite that is the aggregate of many QUnit test suites. So with the help of others, this has become a QUnit plugin called QUnit Composite and that's now maintained by James Green. And so as I'm writing code, I often wanna view a diff of the changes that I've made, but I don't really like working with the command line diffs. I much prefer using an interface like GitHub, but obviously I can't use GitHub while I'm doing my local development before I've committed and I don't wanna install a GUI to deal with everything. So as a result, I created a module called PrettyDiff. PrettyDiff has the exact same API as GitDiff except that the result is a web page that looks very similar to a GitHub-style diff.  And PrettyDiff is freely available on NPM and it's becoming an indispensable tool for myself and many others. But this tool probably never would have happened if I hadn't been able to benefit from all the improved UX and workflow of working with GitHub on a daily basis. So once I've got my test written and the code's patched and I've reviewed my diff, then I run the full test suite. And that includes lots of tools like Grunt, JSCS, JSCint, CSSlint, Uglify, PhantomJS, GruntHTML and a few others. And the projects that I've listed were either created by JQuery YT members or they were improved by JQuery YT members or they've had bug fixes by JQuery YT members. In some cases, the team members have even joined the core team for these other projects. For now, I'll just talk about GruntHTML. GruntHTML is a module that validates HTML files and we use this to run our demo and test pages through them to make sure that they are well formed. So Jiren Zephyr is the dev lead for JQuery Y and he's also a dev lead for many other projects. He created and maintained this module and he worked with Mike Smith from W3C to get the validator.new code so that you could run it against a large set of files locally in a very short amount of time. So cross-project collaboration like that is very beneficial and it allows us to cut down on development time and work with multiple communities. So since Mike was already familiar with the validator.new code and Jiren was already familiar with writing Grunt plugins, we were able to get this done very quickly and the result is that we now have automated validation that was previously a little tedious but it was very time consuming and now it's not tedious at all and it's very fast. Plus it's available to a large audience of web developers, right? It's not something that's JQuery specific.  So Jiren Zephyr built another plugin or another module called commit please and commit please works by installing a commit message hook in Git. So we have it listed as a dev dependency in JQuery UI and then when you run MPM install on JQuery UI it installs this commit message hook and what that does is every time you go to commit it will validate that the commit message conforms to the commit message guidelines and if it doesn't it will reject the commit and then it will show you your original commit message and an explanation of why it didn't conform to the guidelines. So this can be really valuable having consistently formatted commit messages. So for example we can use this to generate the change log for any release just by parsing through the commit messages because we know that there's a specific format and we know that if there are ticket references or pull request references that they're gonna be in a specific place within the commit message and they're gonna be in a specific format and we can parse out all that information automatically. So if you'd like to enforce any rules in your own projects you might wanna check out commit please. So across the various JQuery projects we run a lot of other tasks during builds as well. Many of these have also been built and developed by various team members. For example some of them are Bower copy, Compare size, ES format or Git authors, JSCS, Grunt spider, Perf janky. This just keeps going on and on because we like to automate lots of stuff but we won't talk too much about the other tools because I'm a busy guy and there's still a lot more to do. So now that my changes are committed I'm ready to push them up to GitHub and once the code's pushed up to GitHub then it kicks off the CI build in Travis. As part of the CI build we run the full test suite against all of our supported browsers and we accomplish that through a mixture of test warm, Jenkins and browser stack. This actually has some interesting history. So test warm was created by John Rezeg back in 2009 and there were no tools like this back then. So he actually designed it to be more like study at home rather than a tool that could be used with an automated process that can spawn browsers on demand. The idea was that for every commit to one of our projects it would create a new job in test warm for every browser that we support and then anyone from the community could just join test warm with whatever browsers they have available and those browsers would just wait for jobs to be available and when they are they would run the test and then they'd report the results back to test warm. This worked out pretty well but it did have a few issues. We mentioned, Dave mentioned earlier about the change to request animation frame and that not running in the background. So we had problems like this where people would connect to test warm and then they switched to another tab where they switched to another application entirely and that would mess up the test runs because the browser behaves differently in the background than the foreground. We also had some problems with people installing browser extensions and then the extensions would interfere with the tests and we'd get all these false negatives and we'd have to rerun the tests and see if they were gonna pass for somebody else. So it definitely improved the amount of time needed to test because if anybody's ever tried to run their test read against every change that they make in 10 different browsers, you'd probably go insane. So luckily in 2011, Ritesh Aurora reached out to me within a few hours of releasing the browser stack data and within a few weeks of that, there was an API that was designed by Adi Esmani, Oliver Morgan and Matthias Binance and as soon as the API was available, I built a module, a node module to connect to the API and we started leveraging browser stack to connect to test form. But since then, the cross browser testing landscape has changed quite a bit and so now we're working on moving over to intern. Intern's a Dojo Foundation project. It has much wider scope than test form in addition to just replacing the job queue and the results aggregation. It also has support for web drivers so we can do real automation testing and it also directly integrates with browser stack and many other services. So we've been working with intern for a few months now and we're migrating over the projects one at a time and this will not only improve our testing but it will enable us to improve the intern project as well. So just as we've been active in other communities, we expect to become active in the intern community and help build up more infrastructure and improve that tooling. So that's an overview of everything that's involved in just a simple bug fix. So if you were to spend a few minutes thinking about all the tools and services that you use on a daily basis while you're doing development, the number would actually be pretty high. And so then if you think about all the people that are involved in maintaining all of those projects and all the time and effort that's been put into maintaining those projects and building the features that you need, you can see why it's important to have strong communities that are helping maintain these projects. So we rely heavily on the work of others so that we can more efficiently do our own work and as open source developers ourselves, we understand that value that the community contributions bring. And so because we understand this value, we strive to create mutually beneficial relationships with other open source projects. So for example, we've worked with the Drupal team before to replace their autocomplete widget and this benefits the Drupal team because rather than focusing on building common UI controls like autocompletes, they can focus on building a first class CMS. And it benefits the jQuery UI team because any enhancements or bug fixes that the Drupal team works on will get pushed back upstream to us and then all jQuery UI users would benefit rather than just users of Drupal. So when we found out that Drupal would be introducing dialogues into their admin panel in Drupal 8, I started a discussion with them to find out what it would take to get the jQuery UI dialogue into Drupal. And so their team did a review of our dialogue widget and they said that it met all of their use cases. They just needed a few accessibility updates. So we worked with them to get those updates in and then did another round of testing with them. And then we shifted around our roadmap and our release schedule to make sure that the updated dialogue would be out in a stable release of jQuery UI before the Drupal 8 feature freeze. So sometimes these projects, these collaborations cross many projects. So we had previously worked with the WordPress team to get CSS touch action into jQuery UI interactions. This allows things like drag bones sortable to work properly on Windows 8 devices. But today it's even more important with more devices supporting touch action. So TJ Vantol, one of the developers for jQuery UI, had put together a patch and when he was ready to send his pull request, he ran into an interesting problem. When he went to run the bill, as I mentioned we validated our CSS through Drunt-Contrib-CSSLint and it was failing the validation because touch action was such a new property that CSSLint didn't know about the property. So it said it was invalid. So as you might expect, Drunt-Contrib-CSSLint is built on Nicole Sullivan's CSSLint and CSSLint is in turn built on Nicholas X's Parcelib and Parcelib is what knows about all the actual CSS properties. So TJ sent a patch to add touch action support to Parcelib and then we had to wait for that to bubble all the way back up. So it started as a feature in WordPress, resulted in a new feature in Parcelib, CSSLint, Drunt-Contrib-CSSLint, jQuery UI and WordPress. So this does have some additional upfront overhead but the long-term benefits are well worth the effort of working with all these other projects. Sometimes we identify portions of a project that are large enough to become their own projects and splitting off into a new project has a few pretty big benefits for us. First of all, the one big benefit is just having code completely separated from jQuery UI just makes maintenance easier because you don't have all that coupling. But starting a new project can also entice new contributors and new adopters of the project. So as part of the merge between jQuery UI and jQuery mobile, we need to get to the point where we're using the same CSS framework. So rather than continuing to build CSS frameworks in the confines of our projects, we decided to build a standalone CSS framework but we didn't want to just add to the dozens of existing CSS libraries and frameworks either. So what we did instead is we just contacted the project leads for like two dozen of the most popular CSS frameworks and we explained to them what we were trying to accomplish. What we really wanna do is define a set of common classes and markup that we can use for common widgets and page layouts. So imagine if there was a gallery that you could go to where you could view themes that would work jQuery UI, jQuery mobile, digit, bootstrap, Kendo UI, foundation, and any other UI library. Based on the number of community created plugins that leveraged the jQuery UI CSS framework, we knew that this was a feasible concept. What we really care about is basically creating an interface for us to conform to and then the user can load any CSS framework they want as long as it implements that interface. So several of the project leads that we reached out to were interested in this idea and so we held an initial meeting and we had all the interested parties attend and we laid out a plan for how we would move forward and as a result we now have the CSS chassis project which is being led by Sarah Frisk. So even though this project was born out of the needs of jQuery UI and jQuery mobile, most of the team for chassis is actually not from either of those teams, it's its own team and this allows us to just like Drupal can focus on being a CMS and not have to worry about building an autocomplete widget, now jQuery UI and jQuery mobile can focus on building our JavaScript libraries rather than focusing on building CSS that will go with it and so chassis can focus on CSS only and then we can just pull that back into the projects. So even without an alpha release we already have interest from some notable projects. Digit which is Dojo's UI library plans to use chassis in version two of their project and WordPress has also expressed interest. Once there's a stable release of chassis they plan to build their next default theme. They release a new theme every year and they plan to build their theme on top of chassis once there's a good stable release out. So it's exciting to see such large projects with interest so early on. So we've done something similar for touch devices and this is a fairly hot topic so I'll give some history on this. Back in February of 2009, Paul Bacaus, the creator of jQuery UI, had filed a ticket to add touch support to jQuery UI and he included a patch. This was six and a half years ago now and you may be aware that we still don't support touch events. And the reason is because when Paul filed this ticket touch events only existed in Apple's proprietary fork of WebKit and I was fundamentally opposed to supporting a proprietary event system especially one that the developers just had absolutely no input into. There was no open standard for us or even other browser vendors to follow. It took a year and a half just to get the touch events implementation into the main WebKit repo and that only happened because Google reverse engineered the work that Apple had done. Half a year after that happened, Mozilla released their own implementation of touch events with Firefox 4. Mozilla's API never caught on which is a bit of a shame so it was later removed in Firefox 18 but then eventually Microsoft released I-10 developer preview and that included their own take on touch events which was a new concept called pointer events. Meanwhile, the W3C formed a working group called the web events working group to standardize touch events and the idea was to just take what was in WebKit and write a spec for it so that there was an actual standard for others to follow. That working group had representation from every browser vendor except for Apple and it's worth noting that even though we had all the browser vendors as members they were there mostly because they believed in getting web compatibility not because they thought that touch events were the right answer to the problem. So I represented JQuery Foundation in this working group and I tried to bring community awareness around the problems with touch events and that included legal issues with patents, an awkward API and just a dreary future with everything that was going on with all the different event models. So as part of this work I published a blog post and that contained a call to action from Microsoft to submit a proposal to the W3C to standardize pointer events. So after much encouragement from the community Microsoft did submit pointer events to the W3C and the pointer events working group was formed. Again all the browser vendors except for Apple participated in that working group and while the specification was being written there started to be a lot of polyfills popping up. So I asked the working group if everyone would be on board with selecting a single polyfill for us to promote and this would give us the W3C, the browser vendors, JQuery and Dojo all saying this is the one polyfill that you should use and hopefully that would get rid of the competition and people would focus on a single implementation since there's really no reason to have multiple ways to polyfill pointer events. So everyone was on board with this and we settled on the Polymer polyfill that was implemented by Daniel Friedman from Google. Since then Google has transferred the project to the JQuery foundation and we renamed it to PEP which stands for the pointer events polyfill. So just like Chassis PEP has no dependency on JQuery and it's just standalone polyfill that we will then pull into JQuery UI and JQuery Mobile. And this is important to us because we want all web developers using pointer events as soon as possible even if they're not using JQuery in their projects. So we also have members from Microsoft and Dojo helping with PEP as well. And in addition we're working with the HammerJS team to build proper CSS touch action support. So right now PEP relies on a touch action attribute because you can't really polyfill CSS and it builds on top of touch action. So we're working with the HammerJS team and Microsoft to see if there's a way that we can get at least just support for touch action through CSS so that the polyfill is 100% matching the spec and there's no slight deviation there. The Hammer team is also working on a build of Hammer that expects pointer events to exist. So right now Hammer provides an abstraction over a mouse, touch, and pointer. The purpose of using Hammer is to get gesture recognition. And so they're working on a build that will expect pointer events to exist and the idea is that you would load PEP and then you'd load Hammer and that way you can get a smaller build of Hammer. So this is a great example of how we work with browser vendors and standard bodies to push the web forward. The jQuery foundation actually does quite a lot of work like this because we think it's one of the most effective ways to improve the landscape for everyone and I'll talk more about that in a little bit. First I want to talk about the largest project that was ever born out of jQuery UI and that's Globalize. So in 2008 we introduced the date picker widget in jQuery UI which is actually our most popular plugin and it didn't start in jQuery UI, it was created by Keith Wood and Mark Verbansky as a standalone plugin. We pulled it into jQuery UI with the 1.5 release. At that point we had two dozen handcrafted localization files. So today we ship 74 localization files but they're still handcrafted and they're still limited to only the dataset that the date picker widget cares about. So in 2010 we started working with Microsoft to create Globalize which is an internationalization and localization library and it's based on the .NET locale information. The initial work for that was led by David Reed from Microsoft and it brought a lot of benefits to us. So by leveraging the .NET locale information we jumped up to 350 locales plus we had access to more information than just the limited set that our date picker was using. In addition to having more data we were also no longer responsible for maintaining that data so it's great when we don't have to keep track of the locale information for all these locales because we don't speak the languages, we don't know the customs and so we just have to, when somebody sends a pull request saying this thing was wrong and they fixed like part of a locale we have to go try to find another source to verify it. There's quite a pain so not having to maintain that data anymore was pretty important. And of course globalize is completely decoupled from jQuery why it doesn't even use jQuery core. But we've since switched to use Unicode CLDR instead of the .NET locale data. And CLDR is the largest and most extensive standard repository of locale information. So this actually gets us 740 locale and even more data per locale than we had with .NET. So the switch to CLDR along with all the new APIs to support all the new data that's available is being led by Hafiel Chavier. And we're in the process of rewriting the date picker widget and updating the spinner widget which also uses globalize. So if they use the new globalize APIs no should ship with jQuery why 113. As part of the work that on globalize Hafiel has been working closely with members from Unicode, Twitter and Adobe. And there's also been encouraging conversations from the Moment.js team as well as IBM and Dojo for the work that they're doing on their ECMO 402 polyfill. Hafiel has done a lot of work to bring the JavaScript globalization community together. He compiled an extensive comparison list of all the major libraries that exist for globalization. And it compares the goals and feature sets of all the projects. And so that way potential users can come and look at this list, compare to their needs and decide which project is best suited to what they need to do. All the data for that comparison list is public and the individual project leads can come in and update it as they make changes to their projects so that the information's always up to date and accurate. Hafiel also created a mailing list so that he can consolidate all the communication about just JavaScript globalization in general. Because as I mentioned before, open lines of communication are extremely important. And that work provides a lot of value to developers even if they don't end up using Globalize and maybe they use some other library. So at this point, the pattern should be fairly obvious. As we work on J4UI, we look for more general solutions to the problems that we're trying to solve. And if we can identify any of them, then we determine how much work is involved in creating that general solution. So sometimes that results in new projects like chassis or Globalize. Sometimes it just results in new J4UI plugins like the position utility. But either way, we just try to find the solution that makes the most sense for the most people. So again, we're trying to just address issues for as many people as we can. So let's jump back to the standards work that I mentioned earlier. I talked about my involvement in the web events working group and the pointer events working group. Helping to find standards is, it pretty much guarantees that we're gonna reach the largest audience, right? Because once we define standards, that affects everyone on the web. So that's why this type of work is fundamental to the JPRI foundation and all of its projects. Another way that we help shape standards is by providing feedback based on our past experiences and knowledge. So for example, when the new number type inputs were being added to HTML5, we were working on our Sprinter widget. Now I'd noticed that our Sprinter widget had step up and step down methods that defaulted to taking one step. But what we expect said that the step up and step down methods default to take zero steps. So what that effectively means is those methods were designed to take exactly one parameter and so just calling step up with no parameters doesn't actually do anything. So I emailed the, I posted a message on the WhatWig mailing list and a week later the spec was updated and now the APIs matched between jQuery UI and HTML5. So with jQuery UI being used on over six million sites and getting 10,000 downloads every day, we're well equipped to gauge developer reactions to proposed APIs and various implementations. So an excellent example of this is focus handling within dialogues. We've tried out a few different implementations of this and we still don't think we have the best possible implementation so we're trying to figure out what algorithm to use to determine which element should get focused when the dialogue is first opened. Unfortunately right now the ARIA specification and HTML specification don't quite match on what they say should happen for determining which element gets focused. So we'll just keep iterating on this and gauging feedback from the community to see which implementation is ideal and once we have an implementation that we think works well then we can go back to the standards bodies and say this is the experience we've had, these are the things we've tried, this is our recommendation for how this should be handled and then hopefully get the ARIA specification and the HTML specification to be in sync with each other. In addition to standards bodies, we have a great relationship with all the major browser vendors, all of them except for Apple. Jacob Rossi and previously Tony Ross from Microsoft have been a huge help in tracking down and fixing bugs in IE. Boris Zabarski from Mozilla is our Firefox liaison and he's just a great resource for history and web compatibility and just general questions. Mike West and Paul Irish from Google are available on the jQuery dev IRC channel along with Mike Taylor from Mozilla who previously worked for Opera. We also use non-jQuery IRC channels and mailing lists so we can communicate with some other teams as well and whenever possible we try to get bugs fixed directly in the browsers because again that affects the most people and it also keeps our projects smaller and cleaner. So hopefully this has given you some insight into how the jQuery UI team operates and all the work that's involved in maintaining the project. I only touched on some of the projects, organizations, teams and individuals that have been involved in this work but most of this would not be possible without the support and help of the community. So maybe you've built one of the tools that we use every day or maybe you've sent a pull request to one of our projects or maybe you've only searched on Stack Overflow. Either way you're an important part of the community so I'd like to thank you for coming out to the first ever jQuery conference in India. I hope you've enjoyed your first day or second or third depending on if you're at open webcom for any of the workshops. Hopefully I'll see you around at dinner and during networking. If anyone has any questions what happened to the jQuery UI grid? That's a good question. So we started working on the grid back in like 2010 I think and it was a very ambitious project. This actually gets into like questions that came up earlier about data stores and it turns out that building a grid properly is a massive project and there are already good solutions to this and so after spending like a year or so on the project we decided that it was not a good investment of our time because there were already good solutions and people were already using good solutions and we figured we could focus our effort on dealing with standards, working with other communities and just maintaining what we have and finding smaller controls that can be built on top of rather than trying to tackle a large project that's going to deal with data binding and data storage and lots of other components too. So we just after a while we felt it was just not a good use of our limited resources. Anybody else? Elaborate on grunt.html.  There's documentation on how to use it. Basically you just feed it a list of HTML files and it will spit out a list of validation errors and you can control for specific errors if you want to suppress certain errors. You can suppress those. For example, we have pages that are intentionally not well formed because they're sub-resources of another page, right, like for an age-act request and so we want to ignore the fact that there's no title or something like that. But the way that it works is it actually runs the validator.new code. So it just runs it locally and then processes all the files and gives you back any errors. Anybody else? Thank you. I think he'd made a bold move by not having any slides and doing a slide-less keynote. I really appreciate because I know as a speaker how hard it is to do a presentation without any slides. He did have his little notes, I guess, here. But just keeping people occupied without anything to see is pretty hard. Did you guys like the keynote? Lot of information, lot of touching upon real challenges, right, not just hand-waving but real stuff. So I think that's really appreciated. Thank you, Scott.


So as I said in earlier videos, or I said in class anyway, that Aristotle's ethics is going to rely heavily upon his metaphysics. He thinks the answer to, I'm sorry, what ethics is trying to do is trying to answer the question, how are you to live your life? And your answers are going to have certain metaphysical presuppositions. For Aristotle, how you are to live your life is going to be, answering that question is going to be heavily influenced by the question of what is or what does it mean to exist. So everything we talked about when we were dealing with substance, trying to deal with that, you know, even dealing with the four causes, trying to explain change, that's going to have a lot to do with answering the question, how are you to live your life? One thing that Aristotle is going to talk about real quick and what's really important in this idea is the idea of an end, okay? And you know, the end is basically the goal or the purpose of a thing. So lots of things have what are called instrumental ends, right? And these are ends that are good for something else, okay? So for instance, you know, my smartphone, my phone is instrumental, has lots of instrumental ends for it, right? I can talk on this phone, I can receive email on this phone, I can know where I can locate myself on a map with this phone. So this phone has lots of instrumental ends, it's good for many other things, okay? Lots of things are like this, you know, my keys, right? My keys are good for opening up my car door. What my keys are not good for is say fertilizer for these trees, it makes really bad fertilizer for these trees. So does my phone, my phone makes really bad fertilizer for these trees. However, if I wanted to take a picture of these trees, my phone would be good for taking pictures of these trees. This is the idea behind having end is what is it good for, right? And an instrumental end is that it's good for something else. So we have things that are good for something else, this is, you know, has an instrumental end, right? Well now ask yourself, can there always, I mean there's always going to be an instrumental end. Is it always going to be the case that if something is good, then it's always good for something else, right? Well, think about that. You know, I have my smartphone and it's good for, for instance, communication, either by talking or by texting or by email, right? So it's good for something else. I'm going to say, okay, well is communication good for something else? I was like, yeah, you know, communication is good for something else, you know. We get to express propositions, right? So we get to communicate information. We also get to communicate, for instance, emotions, let each other know how we're feeling. This helps build relationships. Okay. Is, you know, communicating information, is that good for something else?  So keep pushing it. Is it always just good for something else? Is that always just good for something else? Well, it looks like really quickly that if something is always just good for something else, then the question is whether there's anything good to begin with. If it's only ever just good for something else, why is all of this good anyway? It looks like when we're dealing with ends that there's going to be good, there's going to be something good that's good for its own sake, right? So when you ask the question, well, what is this good for? The reply is, well, that's good for this. And this is what's called an intrinsic end. It's good for its own sake. So for instance, you know, we're talking about communication. We tend to think of knowledge as something that's good for its own sake. Well, what is knowledge good for? Well, it's good because it's knowledge. Happiness. What is happiness good for? Well, it's good because it's happiness. Pleasure. What is pleasure good for? Well, it's good because it's pleasure, right? You keep asking, well, what is it, you know, is it just always is it good for something else? It looks like there's nothing that's ever going to be good to begin with. So we have this distinction between two kinds of ends. We have instrumental ends and we have intrinsic ends. And instrumental ends are ends that are good for the sake of something else. And intrinsic ends are good for its own sake. So this brings us to kind of the point of ethics, right? The question that ethics is trying to answer is how are you to live your life? And the answer that comes up really common, not across philosophers, but across a variety of different views in time and, sorry, across history and across place is happiness, right? We are seeking happiness. This is the thing that matters. So happiness, whatever it is, is an intrinsic end. Happiness is, what is it good for? Well, it's good for happiness. It's just something that you, it's just something that you want for its own sake. So the question then is, what is this intrinsic end that is happiness? You know, several different views have been offered. It was trying to account for what happiness is. So it's, you know, it's not exactly a settled question. But the idea is that, well, whatever happiness is, it's an intrinsic end. So the question that we have now is, well, how do we find the intrinsic end? So the question is, how are we going to find this end, this intrinsic end for us that is happiness? Well, to start answering this question, we have to first start answering, well, what are we? So Aristotle, kind of following Plato here, thinks that there's three parts to what a person is. All right? There's three parts to what a person is. And I notice this means, you know, answering the question, what is our form, right? If we're asking what are we, what kind of thing are we? If we're asking what is our form? So we already got the formal cause loaded in. All right? Well, for us, Aristotle says, we've got a rational part that's our mind, and we've got irrational parts, all right? Now irrational here does not mean something like, you know, just completely contrary to reason. That's not exactly what is meant by irrational. More along the lines of, it's like there's a part of us that doesn't use reason at all. Not that it's contrary to reason, it just doesn't use reason at all. And there's two irrational parts to us. One is, you know, he looks at what's called the vegetative part, right? So this doesn't mean we're vegetables. Now again, Aristotle is a pretty natural born biologist, so he starts with looking at how things are in common and then how they're different. And there's something that I have in common with all of these things, all right? All these trees, plant life. And that is that we grow, we take nutrition, and we live, right? We grow, we take nutrition, and we live. That's the vegetative part of the soul. Just the basic, you know, the basic survival functions of what you are. Now vegetables are a lot different from other kinds of things on the planet, right? And this is, you know, something that we have in common with animals that plants don't have in common with animals. And this is called the appetitive part. And that should sound kind of familiar at this point, I think it about Plato. And the appetitive part just wants things, right? It wants things and it hates things, okay? So, you know, good tasting food, well, it wants that. It hates bad tasting food. It wants food. It wants to love. It wants to, you know, to possess, right? It wants a whole lot of things. Now the problem with the appetitive part, and this is what we share with the animals, is that it wants all these things, but it doesn't have any real way to discern between them. It just kind of wants and grabs and gets at it. So this isn't exactly, you know, irrational at this point. It's more like just non-rational. The appetitive part just wants things. So that's the irrational part of this. But the rational part of us, reason, right? That's the part that starts figuring out which things to want, or it doesn't figure out which things to want. It figures out which of these wants to go after. It figures out which of these wants to go after. So that's going to require knowledge of the world, what it's like. It's going to require understanding the four causes of everything. What kind of thing it is? What's it made of? Where it came from? And when we deal with ethics, what its purpose is, what its end is, what its final cause is, what is it supposed to be, or what is it, you know, what is its being that would be most fulfilled. So we need reason. We need the rational part of this to find this final cause. So in answering the question, what is our happiness, we have to answer the question, what is our final cause?


What is up you guys welcome back to another one if you are new to the channel I'm Gold Pony on the new car truck SUV reviews on YouTube that is me on the screen and in this video I have always done this comparison because it is the classic comparison between the new 2022 Honda Civic versus the 2022 Toyota Corolla and this is what everybody always wants to see of course I've reviewed both of these cars I reviewed the new 2022 Civic the 2021 Corolla is the one I reviewed of course nothing's really changing for the 2022 Corolla the specs are already on Toyota's website so I am going to do a comparison today a lot of similarities between these two vehicles which is why they are so often compared but there are many very big differences between these two as well and so in this video I will be highlighting the 10 key differences between the 2022 Civic and the 2022 Corolla hopefully it helps you guys make a decision in the end I will be starting at number 10 working my way to number one there will be a clear winner in the end however that might not be your clear winner dependent upon what you're looking for in one of these compact cars so having said all of that what do you guys say let's go ahead and get started with number 10 on the list so number 10 comparison is going to be with the pricing 2022 Civic is going to start at $21,700 however 2022 Corolla is going to start at $20,025 therefore when it comes to the price comparison the Corolla actually takes the win here putting us at a score of one to nothing Corolla in the lead then making our way to number nine being the power plants on these two and so I'm going to use the most powerful power plants between these two just because if you're looking for more power that obviously is going to be the one that you're looking for and so for the 2022 Civic the more powerful engine is going to be a 1.5 liter turbocharged inline four cylinder this one puts out 180 horsepower at 6000 rpm 177 pound feet of torque coming in at 1700 rpm 0 to 60 time for the Civic comes in at 7.4 seconds for the 2022 model year then so when you compare that then to the 2022 Corolla more powerful engine is going to be a 2 liter naturally aspirated inline four cylinder 169 horsepower at 6600 rpm 151 pound feet of torque coming in at 4400 rpm 0 to 60 time for that one 8.2 seconds therefore Civic takes the win as far as acceleration goes for as power plant goes putting us at a tie one to one then make your way to number eight on our comparison being fuel economy comparing apples to apples with this one and so 2022 Civic is going to be 31 in the city 40 on the highway for the base engine then for that more powerful engine I just told you guys about 31 in the city 38 on the highway taking regular unleaded fuel for both configurations then when you compare that to the 2022 Corolla 30 in the city 38 on the highway for the base engine being the 1.8 liter naturally aspirated inline four cylinder then 31 in the city 38 on the highway for that more powerful engine so since the more powerful engine is actually going to be a tie it's the same for both of these vehicles when it comes to that base engine configuration the Civic does take the win by two miles per gallon there on the highway both of them taking regular unleaded fuel so therefore Civic is going to win this comparison putting us at a score of two to one Civic is in the lead then make your way to number seven being the braking comparison and so this is important if you have to come to a quick stop you want to know which one is going to come to that quicker stop between these two as far as the brake sizes go the 2022 Civic is going to give you 11.2 inch ventilated front disc 10.2 inch solid rear disc producing a 60 to 0 stopping distance according to motor trend of 122 feet and so on the other side of things the 2022 Corolla comes in at 10.8 inches ventilated in the front 10.2 inches solid rear disc then in the back with a 60 to 0 stopping distance of 119 feet it's a little bit lighter of a vehicle which means the Corolla does win the braking comparison just by a little bit there putting us at a tie once again two to two let's make our way to number six on the list so next comparison on my list is going to be the rear legroom a few of your passengers obviously this one is going to be pretty important to you 2022 Civic comes in at 37.4 inches which is actually kind of impressive for a compact car for example I am an even six feet tall this is how much space I had when I reviewed this Civic decent amount of space for what this vehicle is 2022 Corolla is going to come in then at 34.8 inches so substantially less again for reference I'm an even six feet tall this is how much space I had in the back of the Corolla so overall when it comes to rear legroom Civic is going to take the win here putting us at a score of three to two Civic is in the lead next on my comparison list number five being cargo space 2022 Civic comes in at 14.4 cubic feet this is what that looks like there 2022 Corolla comes in at 13.1 cubic feet so slightly less both do offer a 6040 split meaning you can fold those rear seats down in both different vehicles but overall Civic is a bigger vehicle so it is going to give you more cargo space as well putting us at a score four to two Civic is in the lead next on my list is going to be a comparison between the tech on these two 2022 Civic now offers a full digital gauge cluster which is amazing I love that I didn't get a chance to experience it but I'm just going to throw a picture on the screen here of that new digital gauge cluster on the other hand 2022 Corolla gives you a partial digital gauge cluster which looks good but doesn't look nearly as good as that full digital gauge cluster but there is more to the tech than the gauges of course making our way then to the infotainment screen the 2022 Civic gives you a nine-inch color touchscreen display whereas the Corolla gives you an eight-inch color touchscreen display so slightly larger screen with the Civic and where it really takes the win for me here is wireless android auto apple carplay is available with the Civic whereas it is not available with the Corolla so that is what really puts it over the top for me civic is going to take this one not only because it has a bigger screen the digital gauges but the wireless connectivity is definitely a big one here putting us at a score five to two Civic is in the lead then making our way to number three on the list is going to be the driving dynamics and so this is going to be the slightly subjective comparison because this is my own personal opinion here however do take into account I've driven over 600 vehicles now so I have a little bit of experience when it comes to driving dynamics so I'm going to include in this the ride quality the handling and actually the cabin noise as well so when it comes to the 2022 Civic it does offer good ride quality more than I expected excellent steering feeling handling that's really what impressed me the most on the Civic it does have a heavier weight to the steering instantly points you in the direction that you want to go cabin noise though kind of bad I got to be honest but that is to be expected the Civic has always had a decent amount of cabin noise and it's still there for the 2022 model year but then when it comes to the 2022 Corolla good ride quality once again I would put it at the same level as the Civic there just okay steering feel though it does have a looser steering feel substantially looser than the new Civic so it doesn't give you that better feeling of being in control of the vehicle in the end and again cabin noise not the best both really don't give you the best cabin noise I got to be honest so overall just because of the heavier weighted steering because of the better handling found in the Civic once again I got to give this one to the Civic 62 Civic is in the lead next comparison number two on my list is going to be reliability and I know this is a big one when you were comparing these two and so when it comes to the 2022 Civic as far as consumer reports goes in the past if I'm looking at the base engine of this Civic and they can calculate these scores based on which parts have been carried over to the new model year and what is traditionally done in the past average reliability is what that base engine is going to give and of course the upgraded engine is going to be turbocharged you can imagine it's going to be at least average or possibly worse because typically history tells us that turbocharged engines at least at the time of this video are not as reliable as they're naturally aspirated or even direct injected counterparts so I will say that when it comes to the 2022 Corolla well above average reliability according to consumer reports so that is the very highest reliability rating that consumer reports gives out and of course they are not paid by any outside sources they buy all of their own vehicles which is why I always use them because they are unbiased in my personal opinion so obviously this one is going to go to the Corolla it is a more reliable vehicle but Civic is still in the lead but now our score is six to three but to the last comparison I wanted to give you guys here is going to be the styling slightly subjective but on the other hand not really here is why 2022 Civic has an excellent redesign what makes it an excellent redesign is because it is lower and wider and traditionally when you make vehicles lower and wider it always results in a much better looking vehicle of course the design goes along with that it is lower than the Corolla for example Civic comes in at 55.7 inches when it comes to the height of that one 56.5 inches for the Corolla so it is a little bit lower of a height when it comes to the Civic making it better looking and then when it comes to the width 70.9 inches when it comes to the width 70.1 then for the Corolla so it is just slightly wider but it does have a wider wheelbase there than the Corolla once again so therefore in my personal subjective opinion you might have a different opinion than me and that is perfectly fine the Civic is the better looking vehicle because it is lower and wider making it a more aggressive appearance in my personal opinion so this one is going to go to the Civic as well but in the end both are very solid picks and that is why they have always been compared to each other I would actually throw in although this is the classic comparison I would also throw in the new Nissan Sentra and the Hyundai Elantra as well with the Sentra you have an excellent weighted steering feel that is one thing I specifically remember excellent handling with that one with the Hyundai Elantra you get crazy amounts of tech and America's best warranty as well and very nice interior quality with that one too but overall let me know what you guys think of the new Civic of the Corolla let me know what you think in the comment section below and which one you would particularly pick that is about it for this one you guys thank you so much for watching if you're free to follow me on social media at the bottom of the screen if you want to see what's coming next on this channel before it actually gets to YouTube be sure to hit the subscribe the bell notification button if you're in a new car reviews that is what we do here on this channel after all do appreciate you guys watching more than you know I will see you guys all in the next video stay gold


Bini ito? Bini ito. Ya skey ho kwa it? Ha ha ha ha ha ha ha ha ha ha ha We have not had one ? Not even so. We have had three. Mojeali twansha Like this, like this. Bb by the way ni main by Sautei e Geu. So you come out. Mgingine fariye kakuja na vibe, I love such normalism, And I'm a mnagani my friend. And by the way, do you know we are asking a question on our social media platforms? Menta lu kuwapi? Menta lu. Okay, I'll see you. I'll try to iPhone Facebook by the way and all those other platforms that put up to Y254. Hashtag is social Friday where we bring your weekend on a weekday. Kata, na nan nezashindo kumaliza kwa umye? Una nangili mimi ya nani, ule pastail kwa meshikuwa kimuam konwezi ni. That's why I am mentally. Nini mwano zi wite jina kashuwa. Nime blah. Hey, okay. So, ash in studio. To me barikiwa. To me... The one that's gone. Ame hang, ame hang. But we have an amazing guest with us, a dancer, a content creator, a brand influencer, a very huge one.  We are here to give you a silent mode. We are here to give you a silent mode. I hope you will enjoy it. I hope so. Hey, bana. Let's have an audience know whom you are. My name is Kayet Orwa. I am a content creator, dancer.   We wanna give kwukum ת flavored怎樣. To give you more, we will do more. We take the same pitch, usually we call them Pauli. What is theálix kiss? Fela There is a dash. Gapanya kiss. Get him whatever he says. нет anything wrong with herself. kinda... What scenario has one been forced to say? In겎. Uki pigo kwa kwa shule? She's very polite. So, dancing, brand influencing, I can imagine you started out dancing, right? Yeah. Which year was that? I've been dancing since I was small, but on social media it was in 2020. 2020? When I was small, I was also trying to dance. Not your big? Misichiwame. Kindly, misichiwame. So, Mr. Ukeha, shuani? Yes, I've gradually, right now, actually, I'm not sure if I'm going to dance. Yes. Tu muikengoma? Tu kuikengoma. We are practical beings. Muikengoma. Tu muikengoma, see? All right. You have... How many followers is it on TikTok? Like 600? 600, yeah. 600,000 followers. Kuna niwa najiwa personali hapo? 600,000 followers. Kuna niwa najiwa personali hapo? Wami fika thao? Jani oni countimu zi maimembo ono? I just want to vote in mebeba hapo. How does it feel knowing that you have so much influence on such a large number of people who want to vote for you? Yes. I see how it goes. I see how it goes. It feels nice, but sometimes it's also scary because I feel like so many people are looking up to you and like me personally, I'm still trying to figure things out. So... Like, kumnanga reyamchu, wini hajiwa fika, like, from my point of view. Kitugani wa Shai Fanya hadu kawana or like you realize I actually have this much influence nini kushituwa. Either views or a product you promoted or something. Ami watu kusumbu wa mahali kwa barabaro kipita kwa kaya? I guess it's that your recognition, like the first time someone recognized me, hidu kwa tukwa supermarket then, just a group of guests then, kujama, furae. Like here in Delhi, people actually know me like that. You are out there. Do you intend to grow more and bigger? Yes. How do you figure out? The direction your brand is going? Just a maximum point. Ikisha fika maxima ma puta fika uta kwa minimum say na sana, aim ten another place. So, the question of the day that we are asking is where are you mentally? So, say, where are you mentally? We go to South. That is so politely answered. Like Suko Vibhaya. But first Kupo. Is there a meme that can describe your life right now? Hmm. So, what is it? Is it your name? A meme. Okay. Okay.  Hahaha. Kuna kwa kutukana jifu ni kanga. Hahaha. Kana gala. Yeah. Hahaha. Nimecha kaji na tunikanga na madem sa. Haha. Katu nishi. Yes, Yes. Welcome we find on social media kaya. On all my socials, YouTube, Tik Tok and Instagram just kaya to Oro. I saw this on your one of your pages. I try to, every once in a while Oh, you're so sweet Thank you Kata The conversation is so chill Ni ni Tadizu ni kwa ntutizu ya Ni ni za jabana kwa kwa tumetulia tu So I'll look at kibrit So maske wu kudaba piya kwa? Kinda So I wanted to ask you about your brand You have worked with a couple of brands How do you make money? How do you make a living? Or yes, how do you make a living out of the content that you create online? So I feel like it's more Okay, at the moment I'm not doing content like professionally, like full time So it's just like when a brand approaches me Like I'm not looking for it You're the prize Ya, like it's okay But still, it's okay Ya, it's okay I was asking actually that for Val And Benitez just opened a TikTok account I think he has like 10 followers The trick I'll give you one of those and at least I'll give you another one We're not tough to advise you on that What's the trick to increasing followers And even reaching the kind of numbers that you have? Like first of all you should be posting Consistently and frequently Not once in a while then you go Frequently? Kila siku? Kila siku na best Okay, how do you know your niche? Yes, maybe I can dance but that's what I want to be doing For me, you look at your most viewed video Like that's what most people want to see So that's what you go with What's your most viewed video? Naku dance wana ni So you should be dancing How do you know that? How do you know? I don't know How do you know what a mouse is?  Your confidence is gone Before we wrap this up Please remind us again we have guys can reach on social media I'll try to go now Benitez Naku na cheza wa piliya Nya ugliza re tori kwa question Of course Bacha niko kawali From Tazbe to Saturday Tazbe to Saturday Benza kawali Ya ni loko, like a loko Ya kwa ni upcha no e Ya kwa ni upcha Sorry, kwa bu ni loko Sorry, sorry Rajiza ni fambia kwa? Rajiza ni fambia layo Skihiri Ya, skihiri inir A lafupia kezho Skihiti bado Skihiti bado Bata pukuna entrance Pari kwa? Apupia pari, langada Ebutu sa idea Na you know Ayafari ya Mamu begi Ya, he's a good DJ Ya, ya And where can we get you, Valentine? Eh, kuwango, batusi kama I'm on Twitter, Wifi for underscore channel On Zikwam I am at colormiva, you are? Benitez IG Benitez underscore K.E. Tkona at Rajiza the DJ Fari shout, nene ya ko Shumambia, shout and don't Asya na Mamu mamu kona Chil kiasi Aku buke hand Tkona ku DM At Masai KTA on all social media platforms At Hela team, also at infusion Buu isatini digapia y Rajiza kwa me sahab We do this every single Friday from 7 a.m. All the way to 10 a.m. So tukutani next week Same time, same place for us Kwa komisijiri Different clothes Yes, batu neza Rudia Na depend Nambua there is a video that we need to watch Nani surprise Na usyone tmese hau na faku dance Kata Usyone tmese hau na faku dance Iko saa Maliza kwa nge raku


Thank you. Thank you all very much My goodness What a welcome including my fraternity brothers here a good afternoon, and I thank you all very much. I Can't tell you how honored I am that so many of you have come out here to say hello and Let me say you have already made me feel so much at home as Henry the 8th said to each of his six wives. I won't keep you long No, I'll tell you they've got a full day for me out there at the University at Purdue and I don't want to fall behind scheduled You see after I leave the University. I'm heading home for California And Nancy told me not to be late for dinner but Well, anyway, I would like to say just a few words to you on the way in today Being a midwesterner myself. I saw those typical midwestern farms Then your neighborhoods and your churches and schools and your city county building with its dome and I Have to tell you back there in those puzzle palaces on the Potomac You can sometimes lose touch with the basic values that we're working so hard to try and defend But coming here to Greater Lafayette has been what has kind of reminded me of a town over in Illinois It's a town where I grew up Dicks in Illinois and where there's a little bit of my heart still there I Can see with the young people and the children that are here that this is kind of a family day, too You know It was the hopes for our children that brought our forefathers to this land And it's continued to be the thing that we strive for is to make this a better place And a place of freedom and hope for these next and oncoming generations So today our families give us strength still I have to share a little story with you Just the other day a man sent me a letter and he had a little episode in it. He thought I would be interested in It seems that on a Sunday morning with the Sunday paper He preferred to read the paper and his son bill Little bill came at him and wanted with a glove and a ball and wanted him to come out in the yard and play ball And he wanted to read the paper and he noticed that on the front of the paper was a map of the world Connection with some story and he hastily cut the map of the world out cut it into pieces And then said to billy here you take this and put the map of the world together And when you get back why then we'll go out and play ball. He figured he'd have plenty of time to read the paper Billy was back in seven minutes And he said how did you do that so fast? Well, he said on the other side of the map There was a picture of a family and I found that if you put the family together then the world took care of itself well, I Know that I have to move on and then get out there to the University the things that are prepared there, but again I just thank you from the bottom of my heart if nothing else good happens on this trip I'll go home about three inches taller because of this welcome out here today. Thank you very much.


Lithuania said on August 16 it will close two of the country's six border crossing points with Belarus, because the geopolitical environment has become more threatening, Deputy Transport Minister Aini Vesyukovishiyut told a Council of Ministers, just weeks after Russian Wagner Group mercenaries took refuge in the neighboring country. The two rural crossing points, which were not used by commercial vehicles, will be closed from Friday, Lithuania announced. Poland has closed all but one border crossing point with Belarus this year following the imprisonment of a journalist of Polish origin and expulsions of Polish diplomats and last week announced plans to move 10,000 additional troops to the Belarus border to support existing guards. The country said in July it had concerns that the presence of Wagner fighters in Belarus could lead to increased tension on its border.


Okay, welcome back to Big Data New York City. I'm John Furrier with Dave Vellante, my co-host. This is theCUBE, our flagship program, where we go out to the events, in some cases, create events. In this case, we are in New York City at the Warwick Hotel, right across the street from the Hilton, where Hadoop Summit and Stratoconference is taking place. Big Data New York City is part of the bigger theme of the Big Data Week going on here. And Dave, I'm excited to be with you here because one of the things that's actually happening here is that we are here having our own event. And a lot of people don't understand what's going on with theCUBE. And I want to explain it. I want to take the time to explain it. Yeah, John, why are we here? Why are we here? We're at the Warwick Hotel, right across the street from the Hilton. You can see it, you know, right from here, from our studio here at the Warwick. Why are we here? Okay, we're here because our relationship with the Riley media has changed a bit and the ecosystem, and we're here because of Hortonworks and when this goes generous, underwriting support and from overwhelming support from the community of Big Data to allow us to come and support us, we're sold out, not sold out, we're filled up all week. We had to start early today. We already got about eight segments already done today. Our whole focus with theCUBE from day one was, we really didn't have our hand out, Dave. It was we're an open source content and we want to give back and to us, we believe that the best content is still out there to be had. And our mission from day one with theCUBE was to go wherever it takes to get that story, to share perspectives, take the human component of the story out there and share that with the crowd. And one of the things we felt strongly about was going to these events. And we've gone to all the events through the Hadoop world except for the first one, but 2010 is our fourth year. And then we've been to all the events, Dave. So it was a shock to us when O'Reilly media asked us, actually didn't even ask us. They told us they don't want us involved in any more of their shows. So we said, okay, no worries. We'll still come down here and we're coming down here on the floor at the work on the main first street view behind, as you can see covering the event. And again, we want to be part of the community. We are part of the community and we're proud to be present at creation from day one of the big data community. A lot of other people coming in, Johnny come lately into the industry. We're happy to be here from day one and we give back. So one of the reasons why we're here is we have a commitment to programming in this area. We want to continue to do a good job. We're known for going deep. We're known for being meticulous about the editorial independence. Yeah, sometimes we will proof check those spelling names on the lower thirds, but we'll get to that. We just have a lot of fun doing it, Dave. So I want to explain to everyone that is the situation. Well, I want to add to the, we can't thank enough the community for the support that we've gotten. John mentioned WAN Disco and Hortonworks in terms of providing financial support. Also MapR, the guys at Squirrel and Hedap, also providing support, but more importantly, the individuals that are helping us create the programming. So Hilary Mason is coming on the Cube. Alistair Kroll has agreed to come on. Ed Dumbill, Alistair Kroll and Ed Dumbill are the co-chairs of Strata. So that's fantastic that they've agreed to come on the Cube. Amar Awadallah. Amar Awadallah is coming on. Chris Lynch, who's a partner at Atlas Venture. Ben Haynes, who's a former CIO at PAPS. He's now the CIO at Fox. Merv Adrien's coming on. Rob Bearden, David Richard, Arun Murthy. These individuals are given their time to come on the Cube to provide editorial so we can do independent coverage. John, that's what we do with these events. Yeah, you know, Dave, I've always said it. And I've said it from day one. I'm a big fan of Tim O'Reilly and O'Reilly Media. I've been watching those guys for decade. I know all their moves. I know what they're doing. And I know their business. We are not competitive with them. So a lot of people are like, what's going on? No matter what is said, just for the record, we feel great about O'Reilly Media. We like those guys. We're just not competitive. We just do a completely different thing. I mean, it's like trying to compare ESPN in the early 80s through all the networks. They're just different. I mean, we're different than them. So I think a lot of the things that I want to share isn't about going into great detail. It's just cultural differences. We love sports. They love fashion and other things, but just different. So we have no problem with those guys. We like covering them. More importantly, we care about going to where the stories are. We launched our CrowdChat application. We have our data science operation. We're using whatever tools that we can build to create the best stories possible, to service those stories, to bring those stories with analysis, doing our best to reinvest and getting the better writing. And again, it's going to be a process, but we're excited to go to the events and go to where the action is. And here from the people themselves, it's all about the people in the community, Dave. Well, we had eight segments tonight, John. We got 17 segments tomorrow, 15 segments on Wednesday. So there's no shortage of continued, no shortage of demand for people who want to come on theCUBE. So we're really pleased about that, because we really didn't know, John, what was going to happen when O'Reilly made the choice, not to include us. And so really thrilled about the support that we're getting. We'll be covering big data NYC. We'll be covering the activities, the announcements at StrataConf and Hadoop World. A lot of guests coming over from across the street, literally across the street, big party tomorrow night, Tuesday night. So I'm excited. Well, we're going to wrap it up here. Just going to review. I just put it on a blog post. A lot more coverage again. There's tons of content hidden in the networks. Dave with silkenangle.tv. Go to wikibond.org for research. I just put up a post just on the top trending stories from our CrowdSpots application. We're monitoring all the hashtags. We understand the social networks. Essentially, these are all press releases. These are all announcements. But this is the buzz. Top story in the community of tweeters. MapR, Wire Security, and to Hadoop. We didn't talk about those guys today much today, because we got really into more of the Cloudera Hortonworks conversation, which I did mention in the blog post. Great to see that conversation come to an end as Cloudera has acknowledged publicly that they are no longer competing with Hortonworks. So that's going to change the game significantly in the Apache community. Second story, as C-Sense breaks, this rules of physics, again, promoting there. And then obviously, the big story in terms of substance, but didn't get the virality, was the HD Insight Windows Azure. I think that's mainly because I don't think Microsoft has plugged into the community as Hortonworks is. So I think Microsoft just doesn't have credibility yet, Dave, in the industry to get the virality. And then the Cloudera partners had an event here.  Although we have no details, we got briefed on the program, but we weren't at the event. And then finally, EMC, Isilon made it. I think this is the EMC, you know, tweet machine going berserk here. So Hadooping with us is free. So that was a conversation about Isilon, and I don't know if you remember, Dave, but our conversation with Sunju Patel, as I said to him, you guys are more big data than Green Plum. And he kind of gave me that shake. And, you know, Isilon's not known in the big data community. People think of Green Plum, which is spun out for Pivotal. But Isilon runs big data there in all the big web scale companies. Huge. Jo Tucci agrees with you, John. When I interviewed Jo Tucci in 2011, I asked him, what's your play in big data? He went right to Isilon. I said, well, what about Green Plum? He goes, yeah, you know, they provide the analytics and, yeah. They're a carburetor. They're a carburetor in the big data engine. They're now Pivotal. We are here to break down the news. This is what we do. We love having fun. This is theCUBE. I'm John Furrier, Dave Vellante. We're gonna stay here for two more days of who knows what's going to happen on theCUBE. So we'll be back tomorrow. Stay tuned and we'll see you tomorrow. theCUBE is a live mobile studio.


Behind these doors, there's a fascinating world of science and research, where IAEA scientists use nuclear technology to improve the lives of millions of people. Let's take a closer look at the work being done behind these doors and its impact around the world. Behind these doors, environmental pollution is being monitored. The work being conducted is used to advise countries how to prevent pollution and mitigate its consequences. Radiation medicine is used by hospitals worldwide to treat cancer and diagnose diseases. This laboratory ensures that radiotherapy or x-ray machines are set correctly so patients get the right dose of radiation. And our cultural heritage is also being preserved behind these doors. Tests are conducted to discover the origins and composition of ancient objects. Experts can take their equipment to the places where these precious artifacts are located. Activities in the field of food and agriculture are carried out jointly with the UN's Food and Agriculture Organization. Pests are a major problem. Insects like the fruit fly decimate entire fruit fields, ruining crops and livelihoods. This laboratory provides support to countries that use a method known as the sterile insect technique to suppress and eradicate pests. Animals provide both food security and financial support, but they can suffer from deadly illnesses which can be passed on to humans. This laboratory produces vaccines for such animal diseases. Plant breeding is also a focus at the IAEA laboratories. This research leads to new varieties of plants that are disease resistant, have higher yields, or can grow in extreme environments. Good soil is the basis for healthy and abundant crops. Scientists help countries to improve soil fertility and make the best use of scarce water resources. The healthiest of soils can be damaged with too much pesticide. IAEA experts produce tools to help farmers apply pesticides effectively and safely. Since these laboratories opened in 1962, there's been no comprehensive renovation. Even though the demands for the services they offer have increased substantially, they're expected to increase even further as the problems the eight labs address continue to grow. These laboratories need to be at the top of their game scientifically. Using the latest technology while meeting the highest safety and security standards. This is why the IAEA has launched the Renewal Project to renovate and modernize them. This will enable the IAEA to offer better services, train even more visiting experts, and continue to improve the lives of millions of people for decades to come.


In a world where North American governments are making a strong push to bring the critical mineral supply chain home to America, I'm joined today with Mark Chalmers, CEO of Energy Fuels, the leading US producer of uranium, rare earth elements and vanadium. Mark, welcome. It's my pleasure to be here. It's a pleasure to have you. And congratulations once again on a fantastic Q3. I'd like to jump right into that by asking you, can you highlight the key factors that contributed to Energy Fuels' robust net income of $10.47 million in Q3 2023? Yeah, it was a combination of about four different things. One is uranium cells, some rare earth carbonate cells, but there also were some non-cash adjustments, for example, on some of our investments and also the value of the note that we have with Encore. So there were some non-cash aspects of that, but if you look at the company over this year, 23, we are significantly profitable because we sold the ultimatum project in Q1 and we're still seeing the benefits of that later in the year. Yeah, fantastic. And keeping on the topic of financials, you also had a significant increase in working capital this quarter as well. How do you plan to allocate these resources for future growth? Well, I've been in the smaller end of the mining sector for a number of years and the number one thing is I keep a strong balance sheet. So right now we are fully funded for all of our uranium and rare earth activities here in the United States with the strong balance sheet we have, but we're also looking at also having additional arrows in our quiver for potential M&A in both the rare earth and the uranium front. So I can't tell you exactly how they'll be allocated other than the fact that we have a substantial capacity. Yeah, and it's great to have, especially in markets like this. But speaking of markets like this, Energy Fuels has seen profitable uranium sales this quarter as well. Could you discuss the impact of the current commodity prices on your sales strategy and profitability? And do you see this trend of Americans buying in America continuing? Yeah, I mean, our profitability in the uranium sales was largely based on the fact that we have the ability to produce uranium for what we call alternate feeds. And that allows us to take natural uranium and process it at the mill and it's very low cost. And we currently have our uranium inventories on the books for about $30 a pound. So if you sell at 60 or 70, you know, you get these really nice margins like we experienced in Q3. When you look at, you know, the United States as a whole and there's certainly paying more attention to things that are produced in either the United States with allied countries. And you know, I think it will continue for the foreseeable future. But it's not an absolute.  It's going to take time, but there are there certainly people are taking steps to start the weaning process to start. Yeah, and I appreciate that. And you're just talking about production there that leads into my next question. How are the preparations for the production of uranium mines progressing? And what are the expected impacts on product production capacity and company revenue? Well, as I said in our Q3 call, we're we're readying about four different mines right now as we speak and and and we're doing them kind of in a stair step fashion. And we will respond based on our contract portfolios and other market conditions. You know, the the the margins that we posted, you know, 50 percent margin, really from $30 to say $60 a pound will continue to have strong margins there in the foreseeable future, because one of the first projects we planned to come online is our opinion plane mine that has a forecasted cost of around 35 to $40 plus we still have these large inventories at around $30 a pound. So so we're going to continue to have strong margins as the uranium business improves. Right now, we've got three long term contracts. So we're looking at signing more. So just watch the space, Brandon, but, you know, we're in a good position with our projects and momentum that we have. Yeah, and fantastic to hear. Well, I'd like to switch over to another critical mineral talking about rare earths. Can you elaborate on the company's progress in developing rare earth separation capabilities and strategic importance for energy fuels? There's been a lot of news on rare earths in the U.S. government investing in critical mineral infrastructure at home. Is the U.S. government by chance currently lined up at their door looking to speak with you on that? Well, right now, you know, most of our rare earth strategy, we've completely funded it on our own accord. Certainly, there's interest of the U.S. government to advance the ability to secure and process rare earths more in the United States than has happened for a long period of time. So, you know, we're basically just building our plan out. We secured earlier this year, we secured the Bahia Project in Brazil and we're advancing that. We still receive feed from Kimors in Florida and Georgia. And we're building out what we call our phase one separation capabilities for separate into oxides, at least the lights into oxides at White Mesa will be ready in Q1 of 24. So we're making rapid progress, but we're still looking at more molecules in terms of monazite supply feeds for the White Mesa mill. So in addition to what we're doing with Kimors and Bahia, we're looking at other sources globally, including in the United States to really build up a world material rare earth business in due course. Yeah, I appreciate that. In terms of speaking with the governments, are they actively looking to speak with companies like yourself on figuring out what is the future? Where is the supply going to be coming from and hopefully domestically? Yeah, I mean, we talk to the government and we look at things that may make sense for us. And, you know, one of the issues that we're having is we're moving very quickly right now and our plans are to build out the story and show that we actually have the capabilities of integrating a number of the steps right now on our own devices. And then we'll start looking at more potential government support or off takers from some of the, you know, tier one groups. That are looking for our products. So so I mean, right now we're trying to drive our bus as much as possible and move at the speed that we can move at, not not what others want us to move at. Fantastic. And once again, great to hear. Well, Mark, thank you so much for your time. For anyone looking to find out more information about energy fuels, you can see their website just down below there. You can click on there. There's plenty of information there to take that deeper dive. Mark, thank you so much for your time. Thank you, Brandon.