8. It provides only a base infrastructure. End user have to
configure and manage platform and environment,
deploy applications on it.
AWS (EC2), GCP (Compute Engine)
9. It provides a platform allowing end user to develop, run,
and manage applications without the complexity of
building and maintaining the infrastructure.
Google App Engine, Heroku, AWS (Beanstalk)
10. It is sometimes called to as “on-demand software”.
Typically accessed by users using a thin client via a web
browser. In SaaS everything can be managed by
vendors. End users have to use it.
Gmail, GitHub
You should now more insight into why we built React and React Native. There’s a lot more to learn by visiting the project websites and getting involved with the community. The hope is that we’ll see you build some great projects with this tech and other projects we’ve shared.
Thank You!!
React is a new... declarative way to build UI
React is a new... declarative way to build UI
React is a new... declarative way to build UI
There were over a 720 thousand people with the dev tools installed in Chrome
This is especially crazy because I know plenty of engineers who develop with React every day that don't even know the React dev tools exist!
So… what’s so special about React?
There were over a 720 thousand people with the dev tools installed in Chrome
This is especially crazy because I know plenty of engineers who develop with React every day that don't even know the React dev tools exist!
So… what’s so special about React?
There were over a 720 thousand people with the dev tools installed in Chrome
This is especially crazy because I know plenty of engineers who develop with React every day that don't even know the React dev tools exist!
So… what’s so special about React?
There were over a 720 thousand people with the dev tools installed in Chrome
This is especially crazy because I know plenty of engineers who develop with React every day that don't even know the React dev tools exist!
So… what’s so special about React?
React is a new... declarative way to build UI
The imperative way of writing this might look something like this. This says, if I like this, and there’s no blue like on the screen, remove the gray like and add the blue one. And if I don’t like it, do the opposite. The focus here is on the transitions between the states. I have to check what’s currently on the screen, and then make API calls to manipulate it.
This can be a fragile approach, especially when we add more states, making the UI more complex. The number of transitions balloons quadratically with the number of possible states your application can be in. (We’ve probably all had bugs where users end up in states we didn’t expect by performing a specific sequence of actions).
The imperative way of writing this might look something like this. This says, if I like this, and there’s no blue like on the screen, remove the gray like and add the blue one. And if I don’t like it, do the opposite. The focus here is on the transitions between the states. I have to check what’s currently on the screen, and then make API calls to manipulate it.
This can be a fragile approach, especially when we add more states, making the UI more complex. The number of transitions balloons quadratically with the number of possible states your application can be in. (We’ve probably all had bugs where users end up in states we didn’t expect by performing a specific sequence of actions).
The imperative way of writing this might look something like this. This says, if I like this, and there’s no blue like on the screen, remove the gray like and add the blue one. And if I don’t like it, do the opposite. The focus here is on the transitions between the states. I have to check what’s currently on the screen, and then make API calls to manipulate it.
This can be a fragile approach, especially when we add more states, making the UI more complex. The number of transitions balloons quadratically with the number of possible states your application can be in. (We’ve probably all had bugs where users end up in states we didn’t expect by performing a specific sequence of actions).
The imperative way of writing this might look something like this. This says, if I like this, and there’s no blue like on the screen, remove the gray like and add the blue one. And if I don’t like it, do the opposite. The focus here is on the transitions between the states. I have to check what’s currently on the screen, and then make API calls to manipulate it.
This can be a fragile approach, especially when we add more states, making the UI more complex. The number of transitions balloons quadratically with the number of possible states your application can be in. (We’ve probably all had bugs where users end up in states we didn’t expect by performing a specific sequence of actions).
You should now more insight into why we built React and React Native. There’s a lot more to learn by visiting the project websites and getting involved with the community. The hope is that we’ll see you build some great projects with this tech and other projects we’ve shared.
Thank You!!
You should now more insight into why we built React and React Native. There’s a lot more to learn by visiting the project websites and getting involved with the community. The hope is that we’ll see you build some great projects with this tech and other projects we’ve shared.
Thank You!!