Laravel gives you many ways to do things. With controllers, it is no different. We saw that we can use explicit controller routing already, and now we are going to see that we can also implement Resourceful Routing with our controllers.
The most striking similarity was the use of a virtual DOM. Like Ractive, React had discovered that creating an abstract representation of the DOM allows for lightning-fast operations by minimising the amount of DOM manipulation (the bottleneck in most webapps) that needs to take place. It also facilitates server-side rendering without some of the crazy hacks users of other tools have had to employ.
Another was the focus on reactive programming. This is one of those phrases that threatens to become meaningless with overuse, but it's a useful concept. Put simply, in a reactive system where the value of bdepends on the value of a, if a changes then b will also change. Applied to user interfaces, that means that when your application state changes, your view also changes. With traditional MVC libraries you typically have to implement all your render logic manually and wire it up with a web of publish/subscribe events; with React and Ractive you're spared that (tedious, error-prone, hard-to-optimise) step when building your apps.
Finally, both libraries believe that the way to help developers build complex apps is to give them tools that encourage simplicity and composability and then get out of their way.
Having said all that, there are also some stark differences.
It had been a long time I wanted to try HTML5 WebComponents and this week I finally had the time. So I’ll explain, simply, how to create your own custom webcomponent.[[MORE]] However you need to know...
IntroductionToday it’s possible for us to author in ES6 and transpile our sources down to ES5 at build-time, regardless of whether we’re using Grunt, Gulp or Broccoli. With projects like Ember and Angular looking to ES6 as part of their...
Total.js follows the model-view-controller convention to much success. Simply place the relevant code in models/views/controllers folders and you’re good to go.
There is also the option to build your own modules by writing custom code which can hook into different events in the web application lifecycle.
This will be the last part of the AngularJS Polling Application Tutorial series. In this part, we will create a RESTful API using Laravel for the AngularJS Single Page Application that we had created in the previous parts of this tutorial series.