Hey... I do use Laravel framework professionally since 2013 up to nowadays, and I really like and recommend this framework. It is the best. Go for it! But, sincerely, this enthusiastic merchandise of it makes me laugh. Even myself can't take it seriously. Pardon me, I'm just being sincere: it really made me laugh. Sorry. Let me pick as concrete example this snippet of three things in a row: Laravel Scout: Driver based full-text search for Eloquent, complete with pagination and automatic indexing. With laravel Scout, you can do: $orders = App\Order::search('Star Trek')->get(); Laravel Echo: Event broadcasting, evolved. Echo brings the power of WebSockets to your application without the complexity. Laravel Passport: API authentication without the headache. Passport is an OAuth2 server which you could get ready in minutes This sounds like pure marketing. Laravel Echo does not remove the complexity of having WebSockets in your app. It facilitates several functionalities with handy helper stuff - that's it. Please don't tell anyone they'll have their Web Sockets and no complexity. Sounds like Symfony framework merchandising saying how simple is to use their framework! Laughing out loud. Same thing is valid for all others: Queue, oAuth, text-search - these Laravel features certainly are of high value and drastically decreases development difficulty and time. But these wordings are misleading: "without the headache", "Event broadcasting, evolved" (meaningless), "without the complexity", "you can do App\Order::search('Star Trek')->get(); "... It looks like all will be magical, fairies will appear and delight you while the app development runs on its own, automatically by Laravel. Why all these lies? Are you trying to sell Laravel for kids? You will have headaches. You will face complexity. You will have to configure full text search. You will have to act as a professional developer. That being said, I confirm I greatly admire and appreciate Laravel. It boosts productivity. it really has tons of useful features, and it really does not block your way. I agree with the article point. I just think the article lost its tone and beyond a certain point it started to decrease its own value by sounding like a cheap marketing piece. So: thanks for the effort on putting this article and publishing it. I support it, and I support Laravel. I just wanted to point out this "room for improvement" on it.

I really enjoyed the read. My first thought was kind of "hey... these tools are designed for building web applications in development teams... how many of these tremendous creative work beautifully realised need to interact with a database or handle realtime updates?" Many of these tools grow in-house and then are open sourced. Facebook uses React. They developed it for their own needs and then released as open source project. So, it really depends ... for super-creative-engaging-special-effects, these frameworks and tools may be bloated roadblocks. To wrap a front-end layer (ie, JavaScript + HTML + CSS) on top of a database-centered product, say, interacting with its REST API... there is a huge difference from Backbone to Vue... ...and JavaScript in the server-side (backend), is kind of new and started a tectonic shift, together with tons of simultaneously moving pieces... devices, browsers, protocols, sockets, spdy, etc... it is overwhelming and I can only imagine how confusing it looks like for nowaday's beginners if it is hard to keep even for those following the trends from decade or decades ago. While the crowd / mass / userland / us in the open are fed with breadcrumbs from multiple sources, each one wanting to market/attract followers, mixed with some genuine geniuses, there is the need for good developers (yes, they strive hard to hire the good ones)... because it is easy to have app ideas but hard to get them well done... so they hire the cheapest (there are plenty), and then they eventually hire the not-so-cheap to fix the mess the cheapest did... the development workplace is huge and to get those type of things done these frameworks not only help but knowing them is a requirement. So... one of the best ways to move forward on opening your own path in this landscape is having something to do . Either by someone paying/hiring you to do. Or doing voluntary work. Or developing your own idea. I began in web development area because people from a spiritual organization asked help for their website. They wanted to send a daily message through e-mail. They wanted people to send their e-mail address through their website, and receive a daily spiritual message in their inbox. They asked me to do it. As a volunteer, of course. If you do not have something better, then start with this: "receive a user email address and send to it an automated email daily". I worked happily as volunteer for almost three years, and then they were willing to pay me, and hired me. I felt guilty on receving money (that organization is for helping the needy). All this is around 10 years ago... Nowadays, I can't volunteer anymore. I need to pay bills, feed the kids. One thing led to the other. Having experience and knowledge by building the previous stuff, it hooked me to the next opportunity. So... I do not have any answer or conclusion, and I didn't know I was going to write all this. I just wanted to share my first thought when I started! :-) I won't even review what I wrote above, so forgive me typos or anything else. Good luck! And thanks for sharing your thoughts.

I have switched from Angular to Vue one year and a half ago. Being so satisfied with Vue, I've never needed to move away from it (to React, for example). (But I have evaluated React code of other developers.) The recent version 2 release is lightweight and makes Vue perform faster than both React and Angular. Just like Redux makes it easier to scale apps in React, the Vuex library helps on scaling apps in Vue. In fact, in my humble opinion, the "scalability" factor depends more on how well the developers will structure the application than the view-layer-library choice (React or Vue). Angular provides its own opiniated way to structure the app; it may favour scalability if you stick to it, or it may difficult scalability if you later find out the app needs a better, more flexible or different structure. Finally, ease of use : it's tons of times easier than Angular. I can't compare to React. What I have to say is that it is a joy to work with Vue - it is not only "easy", it is fun, it is smart, it has what you need, when you need. Documentation, community, gitter chat, forum, github issues - you will always get support it the trickiest moments. I really like Vue.

As far as I understood, even having only 1 CPU core, the cluster stills brings to you the benefit of having no downtime when reloading the application on a specific server. Yeah, I know... you already have other 9 servers to take care when 1 server is restarting the app... It may be a "micro-benefit", but it is still a benefit. (Specially if you start with one server alone before adding the others.)