Testing a Vue.js and Laravel Todo App | Hacker News Reader

Testing a Vue.js and Laravel Todo App

nick-basile.com

11 pointsnbasile9 comments

That newsletter popup made me not want to read your post, nick. It's quite an annoying one.

I really enjoy the laravel and vue.js combo. The documentation is great, Taylor Otwell is a benevolent, benevolent dictator, and there are lots of pretty simple yet featured demos available written for humans. It just works.

With the PHP 7.1 and 7.2 performance upgrades, I think it is getting harder and harder to hate on PHP. Not to mention that while many of the quirks of the language still exist for legacy reasons, many of the newer updates provide modern methods for today's programmer. (And you don't have to do it the wrong way)

I had an older system running PHP 5.3 and after a day of refactoring, it was ready for 7.1. The CPU usage literally dropped by 50%. Pretty amazing!

Not to mention laravel is quite pleasant to use and has got to be one of the fastest routes to building a good saas app backend with any language.

I've got a new project coming up and I think I will be going with laravel and reactjs.

I’m wondering.

I also have a new project to work to, and I want to try laravel, as I am not using frameworks generally, despite some Magento work.

I played with VueJS and it looks like the good combo to start with.

And then I found this [0], benchmarking PHP frameworks. Of course we can’t tell (or I haven’t found) if the tests were in production mode, and if it’s relevant.

Do you have any experience with this ? Because in my project, the routing aside, it’s just a CRUD app.

Thanks if you can answer.

[0] https://medium.com/@asked_io/php-mvc-framework-showdown-7-1-...

CRUD is what php does best. Framework overhead is not significant part of the request time so unless you're serving millions of requests it doesn't really add up compared to i/o and dB. So I think benchmarking is meaningless.

Thanks

Even for simple CRUD, I would use laravel. And if it really is simple, use Laravel's Lumen, which is a streamlined version of the framework specifically for API development.

I used to worry about overhead. I stuck with codeigniter for that reason. But in reality, the difference in overhead is indistinguishable even at large scale.

Save yourself developer time and throw a few extra vCPUs at your project. CPUs are WAY cheaper than developer time (even if it's your own unpaid dev time).

In short: How to test Vue.js + Laravel API? Just test them separately...

Now if you mistakenly change something in your API and not in the SPA, your tests won't catch that.

Laravel + Vuejs stack works... extremely well - it's such a pleasant experience.

Reply on news.ycombinator.com