Desktop application developers
When you compare that to the progression of the PHP developer jobs.
This just names a few of the frameworks. Which one do you choose? I asked this question on Twitter, but I didn't want to just say what framework should I learn? I did some research and saw that the 2 main frameworks used are Angular or React. As these were the biggest with the largest communities and with the highest job prospects I wanted to go with one of these. Therefore I asked the question which framework should I learn Angular or React? > Looking to learn a JS framework what do you suggest Angular or React? #js #webdev
— Paulund (@paulund) September 8, 2016
The replies I had to this tweet were very surprising, there was a mix between Angular and React with React coming slightly ahead. The surprising part was with the amount of people suggesting vue.js over any over framework. Looking into Vue.js on github you can see how quickly this is gaining popularity and should be taken seriously. But looking at employability the main contenders are between Angular and React.
While searching for a comparison of the two frameworks I found this project TodoMvc which is a Github repository that builds a simple To-do application using multiple different frameworks, this is a great way of comparing the different frameworks while they're performing the same actions. TodoMvc To see the code of the React Todo project you can view it here. React Todo App To see the code of Angular2 Todo project you can view it here. Angular2 Todo App To see the code of Vue.js Todo project you can view it here. VueJs
As I'm not in a good position to compare these two frameworks so I've linked to the resources I used to make my decision.
Vue (pronounced /vjuː/, like view) is a progressive framework for building user interfaces. Unlike other monolithic frameworks, Vue is designed from the ground up to be incrementally adoptable. The core library is focused on the view layer only, and is very easy to pick up and integrate with other libraries or existing projects.
On the other hand, Vue is also perfectly capable of powering sophisticated Single-Page Applications when used in combination with modern tooling and supporting libraries. If you are an experienced frontend developer and want to know how Vue compares to other libraries/frameworks, check out the Comparison with Other Frameworks.
As you can see from the image above Vue is 3rd most popular framework on Github behind Angular and React. When you consider the fact that Vue hasn't been around as long as the other two you can see it's going to catch up quickly. Another point you need to look into when picking a language/framework is the progression of the product, if it hasn't been updated for a couple years then you don't really want to be using it. Vue have recently released version 2 of the framework increasing the speed of the framework. Vue 2.0 Changes
From Laravel 5.3 Vue is being included in the build and will be the focus to creating the front-end of your application. This is just the start of using Vue but this could mean the move away from Blade to be replaced with Vue. This makes laravel a very good choice to use for the API of your app and use Vue to consume the API. With Laravel making this move to include it in the build you will see a lot more people taking up Vue for their applications as opposed to React or Angular. For these reasons I've chosen to start learning Vue as I believe in the next coming of years it will gain more and more popularity in front-end development. What's your opinions on the different frameworks?
If you've been following my blog recently you would be aware that most of the posts lately have been about creating a WordPress theme using VueJS and the WordPress REST API. I've had a lot of great feedback from people really interested in learn more about using VueJS with WordPress. One of the most interesting questions I've had is Why? Why spend the extra effort in building your theme using VueJS when you could just use the standard WordPress theme. I thought this was a very interesting question as most articles around development go over the how you do something but not many people discuss the why you would do it this way over the previous way. Some of my main points to learn how to build a WordPress theme with VueJS are:
This type of development (I find anyway) helps improve the efficiently of your application, it makes you think more about the data you're fetching and if you actually need to get this data or not. For example on a WordPress Single.php page, behind the scenes, WordPress could be performing multiple queries without you really knowing about it. It will perform a query to fetch the post data, a query to fetch the custom metadata, a query to fetch the category data, a query to fetch your author data and queries to get the comments. Plus there may be multiple queries from any third party plugins you use. Developing with an API-first approach makes you think more about what data you need and the best way of getting your data, for example, we could get all the data mentioned above using a single query with database joins. Now I can make one HTTP request, one DB query and have all the data I need to run on the page. Reducing the load on the server and improving the experience to the end user.
When you build with a API driven approach you can have more flexiblity on the technologies you use. For example if I build a site using WordPress as the back end and a VueJS front-end if I want to I could switch out WordPress with a new CMS or custom built API and I won't have to change the front-end at all. This gives the project more freedom to continue to progress with the new techonologies being released to improve the flow of the website and speed up performance.
Get weekly updates to your email