 So, hello everyone. I'm super excited to be here at India's first large-scale new conference. And we have been pushing for this to happen for quite some time now. As I mentioned, we have done a lot of effort in getting the word out, getting dog proposals and getting view, view lovers from different parts of the country. So, let's start by taking a look at the current state of the view ecosystem. Its community aspects and some of the recent technical developments. So, sit back, relax and enjoy the view. So, a brief history. View was created by Evan Yu. He was working for Google in AngularJS for a number of projects. So, in his own words, he figured what if he could just extract the part that he really liked about Angular and build something really like we don't talk about it. And voila, view was born. So, views are JavaScript-based. Yes, it's also progressive in nature. So, if you're building user interfaces, it proves to be a great choice. And you don't have to take a word for it. If you go anywhere in the community, you just go ahead, give it a try. You'll always hear positive things about views. And by design, it's very easy to pick up. And this comes with contrast to other monolithic frameworks where typically you would have to do a full migration. So, as we've seen the upcoming talks today, view is not just suited for quick prototyping. It's perfectly capable of powering large-scale applications as well. So, what's the buzz around ViewJS anyway? In mid-2018, View became the most-starred JavaScript framework on GitHub. And earlier this year, View became the second most-starred project on GitHub that is across all languages. And that's just only behind free code camp. So, booyah! Now, I'm not saying that more GitHub stars equals more usage. It's just that View is no longer the new kid on the block and it's definitely worth checking out. Let's see some of the adoption numbers. View has over a million weekly downloads on NPM. And not only that, it has more than 900,000 weekly active DevTools users. So, DevTools is a browser extension which helps you in debugging. This number really represents the large group of the developer community. And from my point of view, pun intended, this is more significant than the first number. Because NPM downloads can include a variety of use cases, right? It can include numbers, downloads from automated CI builds, robots, downloads of packages for their analysis purposes, etc. But DevTools provide a leading indicator of what's going to come. So, these 900,000 users are using View in their day-to-day development work. And a significant number of them are going to write more of their future applications in View. Now, these are the number of hits on the JS Deliver CDN. So, if you see the eighth place, View has over 900 million hits in the last 30 days. That's more than 30 million hits a day. That's pretty huge, right? And if you compare it with the NPM downloads number, this is like way, way higher. And that is because View provides a drop-in solution as well. You could just add the CDN file, the script app and any application, any application, you're ready to use the power of View. Now, the two other numbers to note here are the jQuery and Bootstrap numbers, the seventh and eighth places here. And if you compare the numbers, that's pretty close, you think? So, okay, no more numbers now. Let's move on to something real. Who uses View in it? So, for starters, Laravel is the one who started View's adoption. Then we have GitLab, who was again one of the early adopters of View. Behance uses View, Apple is using View, and the list goes on and on. Now, one of the other frequently asked questions is that, is anyone using View in India? Yes, the answer is yes. We have started seeing adoption in India and some of the companies using View are your story, Zoomcar, SoulStore and many more. So, the key point I'm trying to make here is that View is now already being used by many of your peers. And this makes the case, like if you're considering moving to View, this case, this makes the case for using View in your organization a lot easier. But does it have an active community? So, I'm proud to say that View's back, View Backloads community is now two years old. In over 900 members, you can find the link at blr.view.community. I'm hoping we hit the thousand-member mark by the end of today. And we host regular monthly Meetups covering a variety of topics. And more importantly, this means that if you face any problem in your day-to-day development, you have people you can reach out to for help. And that's pretty powerful. And other cities like Hyderabad, Delhi and Tune are falling short and have growing companies. Future looks right. Let's move on to the technical side. So, Macross is the core name of the latest release of View, which is version 2.6. And there's an interesting naming convention here. So, every big release is named after an anime with the X letter of the alphabet. So, like in the past, we have had Ghost in the Shell and Dragon Ball as well. So, you're welcome to place a bet on what the next one might be. And if you're just getting bored someday, you could just want a curated selection of anime to winch watch, open the releases and go through that. So, let's see what it brings. One of the most important things that was released in View 2.6 is the new slot syntax. We had an RFC for it and we'll talk more about it a bit. It also comes with an improved asynchronous error handling. So, if you are using sync functions in your life cycle books, the errors during those processes will now be captured by View's error handlers now. And you'll also be able to send these numbers to, like you can handle them, you can monitor them, maybe send these numbers to sentry, do anything. This also releases, this release also improves the compiler error messages. So, now, if you're making any syntax error in your template, View actually points you to the code frame where you have made the mistake. And for a point worth highlighting here is that this feature was contributed by a community member. Finally, we have the built-in data prepared support during server-side rendering. And this is pretty important for solutions because up until now, there was a restriction that can only place your data fetching logic in the top-level route component or in the specific component. Otherwise, that will be a skill. And in View 2.6, we have removed that. You can place your logic anywhere in your component tree. And this also allows higher order solutions like Nuxt to leverage this to simplify their implementation and make things easier for you. So overall, it will result in a better development experience for anyone using server-side rendering applications. So we talked about RFC. What's an RFC? RFC is a request for comments process. This is a framework for proposing changes in View. So you can just look. For beginners, this is a way to get involved with the community. You can go visit this link on GitHub and propose any ideas you have on how we improve View. There are open proposals as well where you can participate in discussions and continue. So this makes things open in the sense that now you have an opportunity to voice your opinion. If the coding, let's say, misses an edge case, you can point it out. And now, like from now on, all of the breaking changes go through RFCs. So it's a very good place to keep an eye. Now let's take a look on some of the recent RFCs. So the new slot syntax that was introduced in 2.6. So let's see what it brings. So for scope slots, it brings more clear syntax. We'll see some examples on what that means. And when you're using name slots, this brings a uniform experience. That's also in line with improving DX or development experience. So let's see some examples on how this unification looks like. So this is how... So the first put block shows how we used to define a default slot with text before. And the bottom one shows the new proposal. So when you even wanted to just pass a text in a slot, you would have had to wrap it inside a template attribute and then you would have named it. You are passing the props. And now with the introduction of vslot directive, you can just bypass that altogether. You can just add that vslot directive on the full component itself. And this makes things easier. Now if you don't have text, if you have an element inside. So here is an example where the message is rendered inside a div. So this also makes things similar to the previous one where you just put the directive on the component and using the template syntax, the prop gets rendered inside the div attribute. And here's an example of named slots. So notice how we have had to define two attributes, one slot, one slot equal to one defines the name, and the slots go. This is now replaced by vslot colon the slot name. And this is where I was talking about the unification and more consistent experience. Everything else is the same. Now let's move on to another RFC. This is a bit of a controversial one, because this has made some headlines recently and some even called it use darkest day. So let's see what happens. So this is an example of a component where the logic is you have a count variable, you have a double variable, which is supposed to include show store the count into two and you have a button where on click, it has to increment the count variable by bar. And this is how we are used to writing the script right now. We export it in a data variable. We write the material increment and we add a computed property double. This is what was proposed. You define the constants count double and increment and just return everything and the initial reaction including mine was this is quite complicated. And it goes against the principle of the whole point of view is like it's simple and this is not simple. And the best part about RFC is that they are not set in store. So we had a lot of discussions and this is some modifications made and there are some key things which I want to clear. This change is purely additive to 2.x. It doesn't break anything. You don't have to rewrite anything if you don't want to. I just keep using view the way you are using and there's no plan of duplicating the object right now. It stays for the foreseeable future. And here is the revised RFC. This is how the view had taken suggestions from the community and discarded the previous RFC and this is the revised RFC. And it makes things simpler by retaining the benefits of logic views and better type inference. And this is the RFC that was closed where you have everything count double and increment different and this is the new proposed RFC. It was opened quite recently like 2 weeks back and to emphasize again this is an open state and you can join the discussion on GitHub right now. So this is like more in line with the current syntax where you have a state object which includes everything your data and configurable you have a function and you return that. So let's quickly take a look at some of the other things everyone needs a mobile app nowadays. So for building those we have solutions like native script view and weeks. And we are also maturing portable based solutions like Prasar, I think 4 and also new one. Prasar recently released a 1.2 version earlier sometime this year and it's really impressive you should check it out. We are moving on to server side rendering. It's been on the rise in recent years and happily so because of the benefits it provides better SEO and faster time to model. And the view system is also sorted on SSR extend the pnds people again are the most popular choices for achievements. Coming to sustainability as GitHub stars don't pay the bills and the major one of the major difference which makes you stand out is that it's not backed by any corporate. So but the challenge that comes with this is that sustainability on like how do we get people to continue working on this and making sure the quality is not compromised. So even as a patient to fund this full-time work on view and there's also an open collective which is backed by the community which fund the work by the whole team members. So in terms of sustainability I would say it was a pretty good shape and it's going to stay. So to summarize. View is getting more popular day by day and has started getting adoption. People around you are either already using view or learning view. The latest release of 2.6 has brought some performance improvements as well. It's views flexible. Now there's an important point. The flexibility is in the sense that it doesn't force you to use any particular template syntax or even TypeScript. You can just use again stylus if you don't like closing HTML tags. It's very flexible in that. The mobile ecosystem is quite mature now and is ready to take on your requirements. Thus it's sustainable. So it's here to stay for a long time. And view 3 is coming. So despite what you may have heard it doesn't force you to use TypeScript. It's your choice as development experience has always been one of the most important views books and today's closing talk will do more details about it. So stay tuned. And that's all from my side. My name is Swapnil and you can find me at Swapnil.net. Thanks everyone for being here and have a beautiful day.