Okay, so we have Nicholas. Finally, we have someone that actually implemented something in the browsers. A couple of the performance APIs. So it would be really interesting to understand more how it is. So, Nicholas, please. All right. Hello, everyone. Like Peter just said, I'm going to talk about shipping a performance API on Chromium. And I'm going to talk about it from the perspective of how we worked to ship the element timing API. I'm Nicholas, and I work on Google Chrome on the speed metrics team. In particular, my focus is on defining and implementing new web performance APIs. So those are the ones that you can run on JavaScript. So I'm part of the Chrome team within Blink. Blink is Chrome's rendering engine. So basically that's where we implement the JavaScript APIs. So the objectives of the talk are basically two. I want to explain the process that's involved with standardizing a new web performance API so that developers get a more clear sense of the steps involved and can also maybe understand why sometimes it takes so long. In fact, they have a 42-step checklist so that I don't forget some of the steps that are required. And the second objective is to encourage web developers here or web and performance enthusiasts to get involved. We love to get feedback about what we're working on, the new APIs, and what we should be working on, like what new APIs we should be surfacing to web developers. So that's one of the other purposes of the talk, to get some help from you, to get some feedback about what we should be working on. Now let's go over the steps to ship an API. The first step is to identify a problem. So in the case of performance APIs, the problem will basically be there's a gap in measurement. There's something that web developers want to measure, but they can't do it right now or they can do it but in a very hacky or unreliable way. In the case of element timing, the gap in measurement is being able to measure when an image has rendered on the screen for the user. So throughout the talk, I will have some screenshots from some websites to showcase what I'm trying to say. For example, here I have a screenshot from stevesouders.com and the blog is saying how to measure the image render time. So the idea is that you have an image tag and it contains the hero.jpg, that's your critical hero image, and it has an unload where you call performance.mark. That will basically give you a high-resolution timestamp of when you call the method. So that gives you timestamp hero one. And in addition to that, you have to append a script right after the image tag and the script will also have another call to performance.mark. So you get a second high-resolution timestamp, in this case hero two. Now to get the estimated image render time, you get the maximum between those two marks and that is the proposed solution. Does it sound reasonable? No, of course not. It's very hacky and in addition to being very hacky, it's also inaccurate. Why is it inaccurate? Well, those two calls will be running on the main thread, which is the only thread that can actually run JavaScript. But browsers generally actually render content in separate processes, which means that the timestamps will not really capture the actual time when the image was rendered. Now that we have identified a problem, let's start by writing an explainer. So what are the parts of an explainer? The first and most important part is to present the problem. So in the case of element timing, we have the following problem. Developers know what content is important to them, what they want to know has been rendered on the screen for the users, and browsers are the ones who actually paint this content. So they are the ones that can compute when that content has been rendered. So from should be panicers explainer, it can be summarized as web developers want to know when the critical elements on a web page have been displayed on the screen. Now once we have presented the problem, we can have some use cases. So what are the user needs that are being satisfied by the new API? Or what are the user needs that we want to satisfy? And what are some examples of how this new API could be used to solve real developer problems? In the case of hero element timing, we have two examples. One is time it takes for images to be displayed upon page navigation. So some images are displayed on the page immediately after navigation because the user doesn't have to do anything to see them, they just show up right away. And the other use case, a little more tricky but still applicable to this is measure the time it takes for hero elements that are caused by user interaction. So for example, you can click on something that causes a new giant image to appear on your web page. Of course in this case, it doesn't make sense to compute the delta with respect to page navigation because it depends on when the user interaction occurred. So now that we have the use cases, we have a third optional component which is usually in explainers but I will call it optional and it's proposing a solution. So having proposed API of how we could solve this problem. I say it's optional because the idea of the explainer is more to present the problem and to make sure that people agree that this is something we want to solve and the solution is just something optional of maybe this is one way we could solve it. In fact, we discourage people to have very concrete proposals in their initial explainer because then as even browser engineers are human beings, right? So we get attached to the solution that we're first proposing. So then it'll be harder to make drastic changes on the initial proposal if we have a very concrete proposal at the very beginning. So in the case of element timing, our initial proposal is basically let's annotate the hero elements. So the web developer has to do this and you can see there it is using the element timing HTML attribute to annotate this is an element I care about. And let's expose information about those annotated elements via the performance observer, which is the class that exposes most of the web performance APIs on JavaScript. So once you have written an explainer which presents the problem and the use cases that you're trying to achieve by solving a problem, you can start by socializing the explainer. So there are several ways in which you can do this. For the web performance APIs, we take mostly two steps. One is to present to the W3C web performance working group. We basically share the explainer and we talk to them to see what they think, what concerns they have. Do they think these use cases are valid? Is this something that could be implemented in all major browsers? Things like that. The ways of communicating in the web performance working group are several. We have a mailing list, which is in the slides. But we also have bi-weekly video conference calls. So basically we have an agenda every two weeks where we just gather together for an hour and talk about whatever topics are on the agenda. And we have roughly yearly face-to-face. So we gather for let's say a full day and try to solve as many problems as we can in this space. Another way to socialize the explainer is via the web platform incubator group or WICG discourse. So I also have put a link for that discourse, which is basically a forum with ADS. Oh, I should point out that the members of the web performance working group are mostly browser engineers. So people like me from Chrome and there's also people from Firefox and Safari. But there's also in the case of the web performance working group, there's web developers from large companies as well as web developers from other smaller companies. In fact, WICMedia also participates. And there's also analytics providers like Akamai participates in the working group. So basically it's open to anyone that is really enthusiastic about web performance APIs. Now we have socialized the explainer and ideally we partner with people that are really interested in solving the same problem and we develop a concrete proposal. Now this proposal usually will live in WICG. That is kind of its purpose. The idea is that that is the place where we incubate new proposals before they become actual web standards. And in addition to moving the explainer to WICG on GitHub, we also request a design review from the technical architecture group or TAG. It's made of people that are experts in the web and they have a familiarity with the majority of major web features. So they do a high level design review and provide some feedback in terms of privacy concerns as well as design concerns for the API. In addition to this, we send an intent to prototype. The idea being that we're signaling to the world this is something that a Chrome engineer is looking to implement. Before it was named intent to implement, but we decided to rename it to prototype because it is actually more accurate to say prototype because it is implemented behind a flag in Chromium. But the flag is basically disabled by default. So it is code that is not shipping to any user and it is just like basically the playground of the browser engineer where he can just implement whatever he wants without having a fear of it reaching the final users yet. So this intent to prototype is sent to Blink Dev, which is a public forum, obviously composed primarily of Blink engineers. But anyone can see the intents that are sent to this forum. It's basically a Google group. And there is no approvals required at this stage and that makes sense because we're not launching any code to the users yet. Now, proposals can take multiple iterations. As you can see for element timing, we did quite a few of iterations. So the first is the original proposal and then it links to the updated version. And then you click on that, then there's another proposal which says obsolete. And now it has a link to the updated version. So you click on that, oh, it has been moved to WICG. And then finally that link will take you to the actual current explainer. So we have multiple iterations because like I said, socializing the proposal, the idea is to make changes based on feedback. Now, once we have a more solid proposal and after we've sent the intent to prototype, then we can actually start prototyping the proposed API. So implement in Chrome behind a flag that is disabled by default. In parallel to that, we add web platform tests. These are tests that help prevent the greatest joy of web developers, which is like they said in the previous talk, basically browser vendors not behaving the same. So the web platform tests ensure that you can test the same thing on all major browsers. So that's the idea. I can go a bit over how they look like. Here at the beginning you have some imports of some scripts which are the test harness. They just allow you to create new functions and do some assertions inside the HTML file because that's what the test is. Then we have some content of the actual test, some style there, and then we have a hero image which is annotated with the key element timing HTML attribute. And then comes the core part of the test, which is using the performance observer to obtain the rendering timing of that image. And then inside the performance observer, you have a callback and in that callback you do some assertions to check some of the properties of the information that you received. In parallel to implementing or prototyping the API and writing web platform tests, we draft a spec. So the specification of an API is meant to not only inform web developers about how it works, but also inform other browser engineers about how they should be implementing the new API. So some characteristics about it is composed of both pros and algorithms. So some of it is paragraphs, but other parts of it are more algorithmic steps and things you should do in sequential order. It is written in Bikeshed or Respec, so it has a special language just for it so that it can have a very specific way of rendering when you translate it to HTML. And usually a new specification will interact with new existing specifications, like for example the HTML or the DOM specification. The reason for that is, well, you need to call your new algorithms from somewhere. So usually there will be interactions with older specifications. And one very key component of a spec is that it shouldn't have any Chrome specific jargon. Many specs are written by Chrome engineers, but the idea is that when someone from, say, Mozilla or from Apple is reading this spec, they should be able to understand what it's saying and they should be able to implement the steps of the algorithms. So it should not include anything that is specific to Chrome. Now once you have a draft spec, we can start doing the internal launch review. So in the case of performance APIs, our main concerns are privacy and security. The specter ring a bell. No? Yes? Well, there are tons of privacy or security concerns with exposing high-resolution timers on the web. So yes, we need to do a very careful review of any new features that we're trying to introduce. In addition to that, of course, the web performance working group or the tag can also surface some concerns and we have to make sure that all of those are addressed before we actually ship the API. Now an optional step in the process is to do an origin trial. So I have a link there for what an origin trial means, but the basics of it is it's a way of allowing experimentation before we actually ship the web feature, like for real things. So in this origin trial, the idea is that browser engineers can get some early feedback, which, have I mentioned that we love feedback? Maybe I have, yeah. So we love early feedback and the reason we do is because after you ship a web feature, it's very hard to make breaking changes to it, right? Because once web developers start relying on that feature, if you make some breaking changes, you might break, well, real websites, right?  We don't like that. So the idea of this is that a web developer, let's say they're interested in an origin trial for this fantastic new web feature, they sign up and they get some tokens for their domains. And some small portion of page loads can use those tokens and will actually be able to access the experimental web feature. Why only a small portion? Again, so that this website does not start relying on these APIs to actually work properly. And once they start using this experimental API, which is disabled by default, but under control environment, it can be used, then we can get some, oh, we can get some feedback from it. I forgot to say that in order to launch an origin trial, you need to send an intent to experiment. So again, this is sent to BlinkDef and it requires approval from one API owner. So you will ask, what is an API owner? It's a person from, well, it's a web expert, not necessarily works at Google, because we do have an API owner who doesn't work at Google. But it's a web expert that is very familiar with Blink and with Blink's mission and what we are trying to achieve. And they can assess the interoperability risks and the benefits. So there's always trade-offs associated with this API. And once you get an approval from one of these persons, then, yeah, you launch your origin trial and you can get some feedback. So in this case, I'm highlighting feedback from Peter, hi, Peter, that is basically saying the API looks promising, at least for Wikimedia web pages. It looks like it's actually, sorry, accurately capturing the image render time of the critical images from the pages that were tested. So in general, we get some feedback from origin trials, but, well, you can understand that most web developers, they want to use features that are actually already shipped, not features that maybe ship in the future, are they going to ship? I don't know. So we don't get a ton of feedback from origin trials, especially for performance APIs, but if you're interested in that, then let me know, because I'd love more early feedback. Now we need to polish the proposal before we actually ship the feature to users. And this involves many steps. For example, we need to know what other browser vendors think about the new API. So that's basically getting signals from browser vendors, but we also need to think what developers think. Do they actually think it's useful? Or are we just working for no reason? Because if it's not going to be used later, then what's the point? Then we also need to polish the draft spec, which is hosted in WICG. And we need to make sure that there are no major bugs in the chromium implementation, which is behind a flag. And we also need to address feedback from the tag review. So these are examples of polishing the spec. These are pull requests into the element timing GitHub repo. And then these are examples of polishing the implementation, because these are chromium code changes related to the element timing API. Now let's say we are all done and our API is like super perfect, right? Because code is always perfect. Now we're ready to ship. So what's the step we do? We send an intent to ship to Blink Dev. This is again signaling the world, including other browser vendors, that we are planning to actually now release this feature to users, like for reals is now. Not origin trial, like enabled by default. So this is obviously a more rigorous step, because it is actually now the real deal. So it requires three approvals from these special people that are the API owners. And once you get that approval, then we basically ensure that Chrome status is up to date, because I don't know, does anyone use Chrome status at all? So yeah, some people here raised their hands. Some web developers use Chrome status, and our dev rel also uses Chrome status. So it would be nice if it's updated, right? Otherwise, who is going to promote the new web platform APIs? Well, no one. And then we can flip the implementation flag so that it is launched by default. Even after shipping, the work is not done. There are several things that we need to continue doing. For example, the most obvious one is basically remove all the experimental flags, because once they are enabled by default, well, maybe after a while to make sure, like, oh, no, you need to unship this. I removed all the flags. If you still have the flag, it's very easy to unship a feature, but once you're sure you're not going to unship, then we remove the experimental flags. Then we also want to continue the conversations in the web working group, because we're not shipping a Chrome API. We're shipping a web platform feature. So what do we want? We want everyone to implement and ship the new feature, right? And we address issues that are surfaced on the GitHub repository, so that's one example there. In addition to that, we monitor usage and crashes. You can't tell from the screenshot if that's usage or crashes, but obviously it's going a little upwards, so I'm going to say it's usage, right? And we also remove features that do not have multi-implementar support and have very little usage, so that is to say that even after we ship our platform API, we may actually change our minds in the future if we see that it was actually a failure, because sometimes, like, everyone makes mistakes, right, even us, so, yeah. So a very simple process here is a summary. I don't know if you can see very well, but I'll try to be concise about summarizing it. The idea is you have an explainer, then the explainer, again, the idea is to present the problem. After you have presented the problem in the explainer, then you can start socializing your idea to W3C, the worker working group, or to WICG. Then, once you have socialized this idea, maybe, well, we don't partner a lot with people to develop the original explainers, but it would be great to partner with people, right, like, share the work, but perhaps you partner with people that are really interested in the proposal, and you write a more detailed explainer together, and you move it to WICG. In addition to that, we can start requesting a tag review, we can send an intent to prototype, saying we're ready because we have this concrete proposal of how to solve this problem, and we're going to start implementing behind a flag. After you've done all those steps, then you can implement behind a flag, and while you implement, also very important, write web platform tests, so that not only Chrome knows how to implement the API. In addition to that, write a draft spec for the same reason, and then do a launch review. That's more internal, but it helps surface potential problems. After all of that is more or less done, you can start an origin trial, and perhaps get some feedback from it, okay. In addition to that, well, keep polishing your implementations, spec, tests as well, and whatnot. Finally, once your API is in good shape, and once developers are like, when are you shipping? Give it to me now. Then you can send an intent to ship, because you have concrete evidence that this is something that is going to be useful as a web platform feature, and perhaps you have already concrete signals from other browsers saying, yeah, we think this is interesting. Sometimes they may disagree, but that doesn't block us from shipping. Then once you get approval on that, you can now actually release the feature to all users. Like I said, the work there is not done. There are some steps, even after you release the feature, which are cleaning up the code, encouraging other browser vendors to actually ship the feature, if they haven't done so already. We're not always the first ones to ship a feature, by the way, but almost always. We then monitor usage, right? Make sure that it's actually being used by web developers, because if it's not, then what's the point, right? And that is the end of my talk. Oh, something's happening. That's like the signal you're done. I think, is it? How many quarters is my manager willing to let me work on something like this? I would say more of a multitask kind of guy. Like web features can take a very long time. Like you saw from the, when I show the multiple iterations, that's multiple people writing similar ideas until eventually someone actually pushes it forward and ships it. So it can take a very long time. From the time the initial explainer is written to the time it actually gets shipped, for actual intensive working on it, maybe a quarter could be reasonable. Good question. Why are new APIs always in Chrome? That's a good question. Why do other browser vendors not implement many of these APIs? Well, right. Well, it depends how you define standardized, but the main answer is resources. So Chrome has more resources than other browser vendors, both Mozilla and Apple, at least for the web platform, right? So they choose to prioritize on some things and not others. In particular, performance perhaps is something they don't prioritize as much as I'd like to, right? Because, well, I work on performance and I'd love to see them ship the APIs shortly after we do. That would be great. But yeah, that's not the case because of prioritization and the resources they have. But one way to help them prioritize is by shouting at them when they don't have the APIs implemented. I hear that that works wonders. But yeah, the reason is that resources and the prioritization that they have. Do we do any snapshots like from real websites? Yeah, we do have a bunch of lab tests and testing in the lab is really hard because unfortunately, the web is not very sequential, right? Because so many resources arriving at different times, there can be multiple race conditions and the truth is loading the website twice won't necessarily give you the same waterfall. We don't use web page replay, I think. But we do have our own lab setup where we can gather traces from the lab loading and then we analyze those traces and that helps us catch regressions in our own Chromium code. So when things get obviously much slower, we are able to use the lab to detect that before it actually reaches real users, which is one of the main benefits of the lab as well as less noise, of course. So yeah, we do use that. I'm not the person most familiar with that, but if you want some tips, I'm happy to connect you with people that know more. Sorry, why is vendor... Oh, yes. The idea is that we want to make features easy to use, not hard to use. So yeah, I understand what you mean. Before APIs had the prefix, but then basically the problem is web developers don't test for our browsers. So developers that have less market would just copy the prefix and that just looks bad, right? Instead of putting their own prefix because nobody's going to use it, then they would just copy the predominant prefix, like WebKit underscore something. And why would Firefox want to ship something that's like WebKit underscore something, right? The idea is that these APIs are for the web platform, not for WebKit or for link specifically.


Hey, this is Brett and this 2021 Ford F-250 Crew Cab Short Box Lariat FX4 is stock number 14044Z. I am here at Summit Automotive in Fond du Lac, Wisconsin, you're new and used heavy duty truck headquarters. This 2021 Ford F-250 comes with a 6.2 liter V8 gas engine, puts up 385 horsepower and it's paired with the six speed automatic transmission. This truck has been fully safety and inspected by our service shop per the state of Wisconsin inspection process. It has a fresh oil and filter change, all the fluids have been checked and topped off and this truck is 100% ready to go. I'm going to go all the way around in this video, inside, underneath, start it up and take a look under the hood, give you the most accurate representation that I can of the truck. Oxford white is the color and I shoot all my videos in 4K and if you like the video you can subscribe to my YouTube channel which is youtube.com slash Summit Auto. Click the bell notifications to get updates on the videos I do each and every day as well as having access to one of the largest catalogs of vehicle and heavy duty truck walk-arounds on YouTube. Over 8,000 videos and counting this one comes with the 20 inch chrome alloy wheels and it has Michelin LTX LT275 65R20 tires. They have just about half the tread left, just a little bit under, frame and under body is in very nice clean condition. This is a one-owner clean title history, clean car facts out of West Virginia. Front fenders absolutely perfect, no dents or dings on there, headlight lenses are nice and clear and you do get the factory fog lights, the chrome toe hooks and the front bumper and lower valence are all in very nice condition. You get the chrome trimmed grille, Ford logos in nice condition and the hood is in very nice shape as well, other than a couple bugs on there, it's in very nice condition, passenger side front fenders in nice shape as well and this passenger side front wheel, no major scuffs or scrapes on there. As you go down this side of this 2021 Ford F250, take note of how clean that body is, how reflective and mirror-like that paint is. Make these HD videos so if you're far away or even if you're close by and you just cannot make the trip down but you're still interested in purchasing the vehicle, you can see the truck here, the truck and have confidence in the vehicle that you're looking at. Before you even get here, so when you do get here, there's absolutely no surprises and you can make a smart and informed buying decision from wherever you're at. Now if this video helps you make that buying decision, let your salesmen know that you saw the video, that it was helpful and that Brett sent you. Back wheel is in excellent shape and then I can keep doing these videos each and every day for all of our customers all over the United States. Back tires have just as much tread as the front tires and the frame and under body is in excellent shape. Keep in mind, these bodies on these new F250s are all aluminum and that frame looks very, very nice. Little rockers and cab corners are in great shape and it does come with the factory chrome step bars. You get the FX4 off-road suspension package on this one. You get the chrome tipped exhaust as well. Rear bumper is in nice shape. You get the backup parking sensors, no dents or dings on that bumper. And the tailgate is in very nice condition as well. I didn't see any major dents or dings on there. It also comes with a very nice line X spray and bed liner, that's what I got on my truck. I love it. You get the side box tie downs and the bed is in excellent shape as well. And that goes on to the tailgate. That shuts nice and solidly and going down the driver's side just as clean as that passenger's side, no dents or dings in the box. And for full disclosure, this back wheel is very nice as well. No scuffs or scrapes. More chips. Those chrome wheels can get chipped up sometimes. These are in excellent shape. And down the rest of the side doors and cab all look really good. It does have the telescopic tomers blind spot monitoring built in directional signals and they are chrome trimmed on the back. Does have the driver's side door code entry. We do have the code for this truck and if you ever wanted to figure out what your code is for your 17 to 22 super duty in the upper right hand part of the screen, got a video showing you how to find that. Back seats are in excellent shape. No rips or tears back here. Do get two cupholders right there.   Three floor mats back here, cup rings in nice shape and you do get 110 volt 400 watt max plug-in and a USB and USB-C and 12 volt power point back here. Get these seats down just like that like so. Get the wood grain trim on the back doors, child safety locks as well. And the inside and bottoms of the doors all look really good. You get the tire and loading information sticker as well as the VIN sticker, no Canadian trucks here.  No rips or tears on those seats. They are in really nice condition. Power driver seat with lumbar factory floor mats, auto headlamps, power pedals, tilt telescopic steering wheel, LED lights on those mirrors, power windows locks and mirrors, wood grain trim on the doors. These mirrors do power fold in. I always like showing both sides. So you know both sides are working properly and then they do power telescope out and in and out and in. So they are working nicely. Top and side check out the miles, the radio and everything that this truck has to offer on the interior. You get all your different feel histories and everything there. Instrument cluster is very nice and clean. 46,113 miles on this truck. You also get a compass display on there. Instrument cluster is very nice and clean. Comes with the leather wrapped steering wheel, Bluetooth and audio controls on the right. Cruise controls and information center controls on the left. There is your automatic transmission with the optional tap shift. That is a six speed. You get AM FM and Sirius XM radio capabilities on here. Just show you the sources here. There's Bluetooth as well. You have your climate controls on here too. And this is also where your backup camera shows up. Truck's got to be running for that to work. You get your different apps, get your different settings. This one has Ford Pass Connect, Apple CarPlay, Android Auto. So while this one doesn't have the factory navigation system, project your cell phone to the screen with one of those apps. And if you have Waze or Google Maps on your phone, project it right to the screen. And it's like you have nav right in the screen. So that's a pretty sweet system. This one does have the B&L premium sound system, stability control, downhill assist control, turn dial four wheel drive, factory brake controller, more tactile volume tune and climate controls, including those dual climate controls. And you get a USB and USB-C plug-in right there. 12 volt power point and 110 volt, 400 watt max plug-in. All right, here's the magic trick for the day. You get two cup holders, nice storage area, or you get four cup holders. And that's the magic trick. Dual glove boxes, passenger side floor mat, and seat are in fantastic condition. I don't think this truck's ever been smoked in. Headliners in nice shape, no rips or tears on that. You do get map lights up here and your power sliding rear window button. Start it up, take a look under the hood. It starts right up, no check engine lights or anything like that. There's your backup camera, that is working nicely. Take a look under the hood. And I would personally like to thank you for checking out the video today. Check out those LED side lights there, pretty bright. And hopefully from this HD video, you've been able to verify the quality condition options and of course, cleanliness of this truck all the way around inside and out. Cab lights up top are working nicely too. Under the hood, we have the 6.2 liter V8 engine, 385 horsepower engine base, very clean runs, very smooth. Once again, this truck has been fully safety and inspected by our service shop. Has a fresh oil and filter change, all the fluids have been checked and topped off and it is 100% ready to go. There is the emissions sticker. And I would highly recommend this truck to make quality and condition standpoint. I think whoever is gonna get it is gonna be very happy with it. And to see more pictures of this truck or one of our 550 new and used cars, trucks, SUVs, minivans, wranglers, halftones, three-quarter tons, one-tons, you name it. We gotta go to that website right there at summitauto.com. Full pictures and descriptions of every single vehicle all at summitauto.com. And if you'd like to check out more HD videos, you can go to youtube.com slash summitauto. Click the bell notifications to get updates on the videos I do each and every day as well as having access to one of the largest catalogs of vehicle and heavy-duty truck walk-arounds on YouTube, 8,000 videos in county. In fact, in a second, you will see a link to subscribe to my YouTube channel in the upper left. A link to more F-250 videos are done in the upper right, a link to this vehicle on our website in lower left. And a link to one of our latest YouTube videos in the lower right, click those, check us out. We're super excited to help you with this ultra clean. 2021 Ford F-250 Crew Cab Short Box Lariat FX4 in Oxford White Clear Coat. Thanks again for checking out the video. Remember to like, subscribe, and share on the YouTube channel. I really appreciate it. Thanks again.


Welcome back to enter the ether. The podcast all about ethereal clash of souls and upcoming third person mobile. I'm your host, the mangoes joining me as always is my friend and cohost jelly D's jelly. How you doing? I'm great mangoes. You know, I totally did the finger guns even though I don't have my video this week. It was just like instinctual to do the finger guns for the, toward the screen. I felt them in my heart. I felt them in my heart. But this week we have a special guest with us, another one. I don't know if we can call her UG, I guess not, but we have Claire, who's the voice of Kalea. How are you doing Claire? So, uh, yeah, so we're going to get into talking to Claire about voice acting, how she got into it and all that good stuff. But, uh, but first up right out the gate. Um, they had another fun facts, which they showed them minions, uh, well, four of their minions. And then they said something about how there's going to be eventually, um, a minion that will represent each class, but they didn't really go further into that. Now, Claire, I know you, you don't know anything about the development side of it. Um, they kind of compartmentalize everything and you just do the voice acting and such. But, uh, you're, uh, you're, you're just as excited for this game as, as we are. What did you think about the, uh, the minions that they showed? I really like the designs. And I think it's really interesting that they're all based off of, uh, the different classes. I think that's just really cool. Um, and the, all the artists on the team do such a great job with designing these characters, like even the minions. So yeah, props to the team. Yeah. Jelly, what do you think? I completely agree with Claire here that it's such a cool idea to have Minions that aren't just your generic MOBA minions. Uh, and you and I talked a little bit about whether that's what they meant or not of actually having classes for the minions, or if they're just fitting their own type and that's the word they exchanged for type, but it'll be really interesting to see what they do with it and how it applies to gameplay. I would love to see that they had a minion per class because the Sky Slayer minions would be flying minions in the lane. That would be, that would be awesome. But I don't like, I don't like how they do Reaper minions, but there would be minions just climbing up trees and jumping out on you like an Ewok or something. I don't know. I don't know how you do a Reaper minion, but, um, there might, it might be like what you were saying, Jelly, it just might be a type of minion, like Siege minion, melee minion. They're like, I don't know the way they said it. And of course, they won't give us any more information than the mud and sinus keeping, keeping their, their lips sealed on that one. I thought they looked, when I first saw them, they looked like reskins of Paragon minions to me, but we asked and apparently they're not. Apparently they're, they're designed from the ground up, but they do kind of look like the Chonky old pair or the Chonky new Paragon minions, not the old Paragon minions, but I don't know. I think it would be smart for them to repurpose some of the Paragon assets, even if they want to use all their own intellectual property, but And for the image we saw, it looked like it was probably concept art of some kind. So maybe they just designed the concept art of that around Paragon minions and that's why we feel that that look is so similar. And that the actual in-game version may not feel that same way, just based on complete different aesthetics. Yeah, they may look completely different when rendered in game and once we see their animations and stuff, I don't know, it'd be interesting to see. I'm really happy they're doing the, they're, they're stepping up their development fun facts.  Which we have some news on that front and not release date necessarily, but the community, they updated the website to have a whole malware section that's a teaser with malware laughing and it's arrow 404 with his symbol in it. And from what the community can figure out from that page, it sounds like we might have an update as early as Wednesday of this coming week, December 2nd, which could for the website. So in theory, that could be really exciting to see all the new information for that. I had not heard anything about that. I guess I haven't been, I've been playing kinks on all weekends. So I haven't really been paying as much attention to the discord as, as usual. That's very interesting. I'm sure you can't tell us anything, Claire, or you probably just, the, I don't know. Do you always yell your lines into the mic? Kinda. Well, Kelly is just very loud. Yeah. Yeah. Let's talk about it. Let's talk about the voice acting part of it.  And how did you end up being the voice of Kalea? Worked with Try previously because we did a League of Legends voice pack for a character named Zoe. And a while later after that, he messaged me and said, Hey, there's this game that I'm working on and they're looking for a voice actor for this character who's kind of like Zoe and I thought of you, do you want to give it a shot? And I sent him samples of it and they were like, yeah, it's a hit. So yeah, that's basically how it happened. Yeah, right on. I think Mangus and I have our own personal question for you and is that, is Kalea an evil character that is just way too excited about killing people?  As far as I'm aware, her definition of fun does not include murdering people, but she's just a bubbly, fun character, youthful spirit and yeah, she's not a blood thirsty person. Well, now here's the hoping that we have voice packs for each character that we can get a blood thirsty Kalea voice pack that you do just because now it's my head cannon. So I've got to establish it in real life somehow. Yeah, that would be really fun. So when you're recording lines for Try, do you typically do a bunch of lines at once? Does he send you singular lines? Are you typically live with him? Do it not live in person? I mean live like in a discord or something like that. How does the process usually go down for recording new lines? I was doing like the samples and things and like the first round, I was doing that solo, but recently it's been more live direction and we usually get a pretty good chunk done, but if just timing isn't right or if there's just a lot of lines to do and obviously my voice can't keep up with that or it's getting late, then we set him aside and we pick another day to come back to them. So now it's mainly live direction unless there was like a small problem and he just needs me to like rerecord one thing, then I can just do that on my own. So is it like how do you get in character for Kelly? Do you have like do you have to get in character or can you just off the hip do it? Well, I've been like in acting classes since I was like 11 or something. So I'm kind of at that point where I can just like get into it because I like to think of myself as a relatively happy person, but so boys and Kaliya isn't too much of a struggle because she also has she's very, very high energy, which kind of makes me get a little tired sometimes, but getting into it initially isn't that hard. Are you ever afraid that you'll end up getting typecast into this certain type of character or are you just happy to be getting your foot in the door with voice acting? Dude, it's already happened. Like before even Kaliya, this was my typecast. It's usually not as bubbly or high energy, but definitely characters who aren't super smart and are probably just like there to have fun. I have voiced some characters that are a little more serious, but I'm happy that I get cast as higher energy characters a lot just because it is really fun and I always have a really good time doing it, but it is nice when I do a more like laid back character or someone who's a little more like brooding, which is weird to say, but it's like it's different and it's enjoyable still. Yeah, I imagine it's probably nice to just exercise a little bit of your craft outside of what you normally do, but I mean you did a fantastic job on these lines like just absolutely amazing Kaliya's voice lines are some of my favorite out of out of all the out of all the voice lines. Just great job all around. I don't think we've said that yet. 100% you guys are so sweet. I can't thank you. I mean, there was a reason that Kaliya's voice lines were the original website update that when you pressed enter like you had a voice line that was front and center because it was just enjoyable to listen to you and it just very nicely done and props to you for sure. Yeah, it definitely encapsulates what you think of with Kaliya with what with what they're going for with Kaliya what they wanted her character to sort of be. Yeah, pretty cool. Pretty cool stuff. If I remember correctly, last week, Mangoose and I both put Kaliya at five stars out of five stars for aesthetic and we're saying that your voice lines are great. So Kaliya is just like the perfect character coming out the gate here. Got good voice lines, good aesthetic. Now we just need good abilities. That's it.  Speaking of abilities, you know, Claire. No, I know I can't I can't ask you any of that kind of stuff. I wish I could but made me swear to be nice. Yeah, I can't give secrets of breaking my non disclosure agreement. So yeah, I don't even want to like comment on like what they're like or anything like I can't know. But how about what was your favorite line for Kaliya to record? I really liked the ultimate line the play time is over and I also really like the the butterfly one. Yeah, that is my favorite. That was my favorite. So good.  Yes, not a lot, but I have been getting into some more recently. Yeah, do you think you'll play Kaliya or Kaliya? How do you say it? Kaliya. Do you think you'll play Kaliya in an ethereal or do you think you'll gravitate towards one of the other myths? Myths. I wish I could play Kaliya, but I am not just like she's obviously going to be like more like as a mage more like attack based and stuff. I am not that I am your little supports just knock them down a few notches and let you get the like the last like the killer or whatever. Yeah, I'm not that kind of character. I probably be playing more like cleric classes or like support because that's just my play style. Yeah, me too. I'm a bit of a support support off lane kind of guy. So now we're going to see YouTube videos when ethereal comes out of Kaliya of Claire saying Nikolai's voice lines in Kaliya's voice. It's going to be the greatest thing. Can't wait. Yeah, that sounds like a really good idea. I want to hear you read Iran's voice lines in Kaliya's Kaliya's voice. That just like cold and cruel just like I want to watch the world burn, but like. What does he say blood and viscera my favorite when he takes a potion? Can you do that? Can you say blood viscera my favorite but in Kaliya's voice? All right, now even more so my head is going crazy for this idea officially happening. You weren't planning on it, but you are now. Okay, please. Oh, that's great. So you mentioned that I'll go ahead, jelly. One thing that I will ask you to do for us in Kaliya's voice because I don't think we'll ever hear the end of it. If we don't, can you do the Nico Nico need for us? I've done it like twice already about fine just for you. Incredible. I love seeing people just being like, God, please stop it. But I live to troll this community. Yeah, you just seem to live to troll jelly. So between the two of you, you know, it's fine. No big deal. You mentioned earlier you've been taking acting classes since you were like, what, 11 years old or something like that? Yeah, how much it like if someone wants to do voice acting, what how, how would they go about it? Like what should they expect? How much work should they expect to be able to put to have to put into it? It definitely does not happen overnight. It I started voice acting. I started taking it seriously more about when I was like 15, which is like three years ago. And it it takes a lot to, you know, get yourself on that path to where you're getting stuff consistently.  Like I'm still trying to like maneuver my way there because I am very young and inexperienced in it. But I would say like for getting into it. There are really good websites and resources. I know Twitter is a hot spot for like casting calls. There's other websites like casting call club and voice acting club. Those are really good to get yourself a foot in a door. But yeah, it takes a lot of patience because if you go into it and you're like, Oh, this is going to be easy and I'm going to be super successful. But you got you got to work really hard at it and it takes time. How much do you how much would you say is is natural talent and how much is just like hard work and practice? It's it's a pretty healthy medium because it's hard to teach people how to act. Not impossible, but some people just have it, you know, like they already have that confidence and that drive to just put themselves out there and it takes a lot to put yourself out there like that to be daring because it is a leap, you know, it but it does take a lot of hard work. You definitely should invest in like classes and like other resources and practice, practice, practice.  What's it called Fluffy and Tries are Best? Is that what it's called? And you have like a couple of like where you were voice acting like some anime and some other like cartoons and stuff like that. Is that something you do to practice is to try and emulate other voices? Emulate voices per se. Those are more for they call it ADR practices where you're just trying to match the lip flaps of the characters. That's what I was using it for and also just for like recreational. I thought it was just good practice to get into a character. I don't try to emulate their sound so much, but just having fun with it myself and I don't really do those anymore, but if I do have like free time sometimes like if I'm playing a video game and there aren't voice lines, I do sometimes fill it in myself just for fun. I think it's enjoyable to do that. So yeah, you can like practice anywhere really. All right on. Do you ever use any of the voices that you've curated in pursuing this in your everyday life outside of recording scenarios where you're talking to somebody and it just like pops out or something happens? Oh, yeah, I definitely had experience. I do have like low this low gravelly voice that one time I was using and my friend had to stop me with sentences and was like, dude, what are you doing? I'm like, I don't know. It just happens. And it's weird when I'm like, I'm talking, I'm talking and then it gradually slows down and it gets like this and then people are like, whoa, what is like, yeah. All right. Jelly, do you have any more questions for Claire? I'm out. I'm tapped. I don't think I have any questions necessarily, but I loved that she like casually used the term lip flaps because now that my favorite politically correct term like, oh, yeah, your lip flaps are moving, but I don't hear any sound. It's just I'm going to use that forever now. So thank you. It's like, oh yeah, you need a clicker while recording and it's like, why do you need a clicker while recording and it's like, but yeah. You need to click the lip flaps. Is that what you need a clicker for?  Oh, okay. It's like a marker. Okay. Interesting. Characters moving their mouths. Yeah, there's just there's weird lingo. That's pretty awesome. So is it a nice like are you guys like a true community? I mean, do you know a lot of the other voice actors and actresses that have worked on ethereal? I yeah, I do. We have like our own little group chat and everyone there is super nice and super sweet and it's not always super active, but when it is, it's just like it's super fun to be in there. And I and I I've known some longer than others and some of them some of them I'm meeting for the first time and everyone is really nice and welcoming and just awesome in general and super duper talented. I love every one of them. Oh yeah, all the voice lines are amazing. All of them. The ones that come to mind immediately are Noxus. I really really enjoyed Noxus's voice lines. Um, the shadow for ex-heal love love that. That's that's freaking awesome. If you if you could pick any other myth in ethereal to voice, which one would it be? Do you think this is this might just be the Kalea and me, but Nikolai. I think Josh Tunnelberg who did Nikolai's voice lines did an amazing job. But oh my God, if I could just like a fuzzy cute creature, that's what I find. Kalea is pretty much a fuzzy cute creature. True. You can't get all the fuzz. Can't get it all clear. Yeah, you got to pick somebody else. We original. Such a fuzz hog. With your clickers in your lip flaps. I feel like that has a whole other meeting, man goose that we just won't get into. Usually I'm the one with my mind in the gutter, but I don't even know why you would. I have no idea. What usually happens when we record ETE. True true true true. So Claire, I do have one final question for you. I don't know if man goose has anything else, but so we talked about kind of what you do for your thing. The the lines themselves. How what are the characters you'd like to voice and all that kind of stuff, but when the theory will coming up. Yeah, I knew that was going to get anywhere with that one. We're going to do this every time. We have somebody we know we have to. We need to put our heads together before the episode and like really springing on up to ask them. That's true. That is truly me. I mean, you know, I've had a page of questions for them. I got to I got to keep up my street crit. Jelly really is the voice of the community.  Pepe Silvia Pepe Silvia. 100% that's me. I may or may not a little enter the ether exclusive for everybody and you guys get to hear it first. I may or may not be recreating that exact scenario with a cork board and pieces of paper for a theory and the whole nine yards that will come out sometime in the next week. Oh my gosh. That's amazing. I can't wait for that. Alright, I think that's I think that's going to be about it for for this week though. Claire anything you any final words or anything you want to plug or anything like that. Follow me on Twitter. Claire Thomas VA that's my Twitter. And every time I come into the chat and y'all say nico nico me I appreciate it. Pretty sure you appreciate it but try color does not. Oh my gosh. Jelly going to plug this week. Just the same old same old jelly knees on YouTube jelly knees on Twitch. Hopefully this week we'll be able to stream some you know life but bankers what about you. I got nothing. I got nothing so I think that's going to wrap it up for this week folks. I hope you enjoyed it really enjoyed the conversation with Claire Claire. Thank you very much for joining us this week. But this is the end of the ether crew. Crew starting off you guys have a good one. You need to keep that exactly like that. Ain't no shame here man.


Welcome to my channel, I am Arvita Karwa and in this video I am going to talk about Mr. Sigmund Freud because just last night I realized the fact that I have made so many YouTube videos yet never did I talk about Mr. Sigmund Freud the great psychoanalytical thinker. I have been reading his book since a long time and I have been fascinated by the ideas by the theories given by him yet I find that these theories when applied in literature are going to make literature even more fun, even more engaging and even more entertaining. So let's talk about Sigmund Freud's theory of personality in this video lecture but before that I would like to talk about an important point. When I was going through the previous year papers I found that UGC net papers are set in a pattern and every time they are going to ask certain questions which are repeated year after year and the publication date of interpretations of dream is one such work. Interpretations of dream was published in 1900 and since it was a monumental work which changed the perception people thought about themselves, about human brain this is a book which you must remember. So always remember that interpretations of dream was published in the year 1900 and it's a monumental work written by Sigmund Freud. So now before wasting any more time let's dive into the topic and let's see what Mr. Freud has to say about personality. So Mr. Sigmund Freud believed in the idea that every person is different from the other because every person responds to the same situation differently. If I ask five people in a room to respond to a certain situation they all are going to react in a different way and this difference in their reaction is caused by their difference in personality. So if you remember the main concept of Sigmund Freud he believed in the idea that there's an internal conflict which is going inside us every time we face a situation. Remember Tom and Jerry in Tom and Jerry there were certain episodes in which Tom used to have these two figures on his shoulders on one side there was an angel and on the other side there was a devil and these angel and devil are going to have a debate over whether they should kill Jerry or leave him. This is exactly what Sigmund Freud meant by the three parts of human personality. According to Sigmund Freud everybody is having three parts in their personality id, ego and superego. Now the concentration of all these parts differ from person to person and therefore their reaction to the situation also differs. In order to understand this better I'm going to give you an Hindi equivalent to id, ego and superego. I'm pretty sure that if you are interested in Hindu mythology you must have come across the term Rajogon, Satogon and Tamogon. So these are the three things which everybody has in himself and this is going to decide how you are going to respond to a situation. So now let's understand what is id, ego and superego. The first component of our personality is id. What is id? Id is known as a pleasure principle. It works on pleasure principle that means the main concern of the id is to maximize pleasure. Id is that part of your personality which is very childish and very impulsive. Suppose my friend has baked a cake for herself and she had put that cake in the refrigerator. I know that the cake belongs to my friend yet I would never mind having a piece of that cake and very soon I might finish the entire cake. Why I do this action? I know that it's morally wrong yet that desire to have the cake, to have that delicious meal or to maximize my pleasure I cannot resist myself and I eat it. We all want to wake up early in the morning yet many of us put our alarm on snooze and go back to sleep again. Why does that happen? That happens because of id. Id is that part of your personality which is going to make you do actions that can give you maximum pleasure. It is not going to think about what is right, what is wrong, should you do it, should you not. It is just going to tell you that do this because you'll feel great after doing it.   The next component of our personality is superego. Superego is also known as morality principle. It's that part of our personality which is going to check our behaviors and see whether we are behaving in a socially appropriate manner. Superego in us is like our parents. It is always going to tell us you do this because this is correct. If a person superego is very strong then that person will never have any issue in waking up at 4 a.m. Even though it's a winter night it's a extremely chilly morning that person can get up because the person knows what is right for him. Superego is always going to keep a check on your actions and it is going to ensure that you act in a morally appropriate manner. You act according to the rules of the society. That's why superego becomes very important for making us civilized. Because if I want to become civilized I need to have a sense of superego in my personality. Finally we come on to the third part of our personality which is ego. Now this ego that I am going to talk about next is very different from the ego which we understand in our day to day language. Because that ego is a hankar whereas this ego is reality principle. It's a part of your personality which is going to make a balance between id and superego. We all know that extreme behavior is always harmful. In Hindi we say ati sarvatra vajyati that means don't follow an extremist path. If you look at id and superego they both are extremes. It says do whatever gives you pleasure whereas superego says that you need to be morally upright. Now if a person is not able to balance these two things he is never going to survive in this world. So ego is that part of your personality which is going to fulfill your id in a socially appropriate manner. So for example if you feel like eating a piece of cake from your friend's cake the ego in you is going to give you a very socially acceptable way to fulfill your desire. He is going to tell you that why don't you bake a cake and then eat it. So this is how ego is going to strike a balance between morality principle and pleasure principle. Morality principle says never eat a cake because it has sugar. It is going to say eat the full cake. Ego is going to tell you that you can have a piece of cake that would be good and then you can exercise to burn the calories. So ego is that part of your personality which is going to postpone the enjoyment but it is going to fulfill it in a socially appropriate manner. So balance personality is the best personality and if you look at literature you are going to have a lot of characters which have imbalance in their behavior and because of that imbalance in the behavior they suffered severe consequences. So that's how you relate the psychoanalytical theory of personality in literature. A classic example is madame bovary. Now in that novel madame bovary is a personality who is dominated by id. She does a lot of actions which are morally wrong yet she only cares about pleasure. She only cares about fulfilling her desires. So you can see the consequence madame bovary had to face. There would be a lot of characters in literature you will come across while reading that are there situated on the superego mode that means they are extremely moralistic. They would never do anything to satisfy themselves they are extremist. So even those personalities have to suffer. So if you apply the theory of edgo superego in literature you will be able to analyze the characters way better and you are going to get new insights from the text you read. So with that note I end my discussion on the topic theory of personality by Sigmund Freud. There are a lot of other topics which you must cover if you are preparing for UGC net English. You can get the list of all the important topics and writers on my website arpidakarwa.com. There's an online course which we are running exclusively for UGC net English aspirants. If you like the way I teach you can even think about joining that online course. Don't forget to subscribe to this channel because it's free. Also click on the bell icon so that you are notified every time I post a video. That's it for this video lecture. We'll meet soon in the next video lecture till the time we meet next. Happy learning, keep loving literature and stay tuned to arpidakarwa.com