Hello everyone and welcome back.
In this lecture we're going to make a short but very important introduction to you.
Yes.
So what is viewed.
Yes future yes is an open source javascript framework for building user interfaces reactive components
and single page applications.
It is called the Progressive framework because of its specific design that makes it easy to create both
simple and complicated projects.
It was released in 2014 by Evan Yu a former Google employee and each version 1.0 only by the end of
2015 with their 2.0 released at the end of 2016 that made its popularity grow considerably despite its
young age.
The framework is in a short time been able to gain broad consensus and a wide adoption by companies
and developers all over the world.
Despite being developed by an independent team alike react in Angola for example it has become so popular
that it is currently the most starred javascript framework on github.
We can appreciate view's great power combined with its easy views community support excellent documentation
and the progressive approach to development made possible by a large number of official support libraries.
When talking about why they chose to call view a progressive framework ever you said something on the
line of you would probably feel a bit guilty if you're using a framework like angular in a static page
to just display a list of people but at the same time you would probably feel sorry trying to build
an app like mail.
We've only vanilla javascript and so this progressive approach to development provided by Voyager yes
can be explained by looking at this graph.
You can easily integrate refugees in an existing project for example using a CDM.
You just have to place a link like you would normally do for example for Jake Whaley in your HDMI file
to get access to future yes code components such as declarative rendering and a component system.
Then if the requirements for your project increase you can start using views complementary official
libraries to get for example client side routine lot of scale State Management Bill system and so on.
The View ecosystem is formed by a series of complementary official projects which allow us to extend
its capabilities far beyond debt court view lay year according to our needs.
And so we got a few router which provides single page application or routine view access which provides
large scale state management UCLA project scaffolding for a rapid development view low which is basically
the view file loader for Werbach which allows us to use single file components in our projects.
We've got a browser dev tool extension called The View dev tools and other projects such as view set
of renderer view class Component.
If you add access it is important to highlight one more time that these are all complimentary official
projects and therefore because they are fought to be used a weave in future.
Yes you can in fact think about them as different components of the same framework.
So now that you've understood the frameworks philosophy and approach to development it is finally time
to start writing practical examples.
Let us quote.