I'm starting to look into how a Single Page Apps work, building an API etc and I've been reading a lot of praise for Dingo API (and others, but that seems to hold a majority in terms of interest). I don't understand the benefit of using it over just using Laravel though. I don't get what it gives me that everyone seems to love. Can anyone help my understanding?
First off a single page website, using a framework like Laravel may be overkill even lumen. As with anything though, it all depends on your requirements.
Laravel and learning it has been able to pay my bills and I love what I do. But for a lot of single and/or very small apps I lean towards meteor a JavaScript framework very similar to Laravel as far as ease of use. Vue on steroids if you will.
I have looked at Dingo but never used it as api end points in Laravel and lumen are stupid easy right out of the box. Granted everyone is different and obviously have their own opinions on what is needed and easier. Dingo to me just seems to complicate an already easy task.
I think using Dingo is a great start instead of writing all the boilerplate code yourself, the more you use it, you will be able to understand how API should be done.
I used Laravel for many APIs (as well as Lumen) and it is great as it is very mature and well documented.
@jekinney I used MeteorJS and it was still very immature, sometimes you hit a wall with basic stuff, plus it requires to learn NodeJS and understand publish/subscribe logic, which most of the cases is overkill. It looks to me as you use comments just to promote other frameworks, the question was clear - what is the benefit of Dingo - not what frameworks should be used. It is fine you write your opinion but if you never used Dingo, maybe it makes sense to not write anything :)
Can someone please explain just a little more about the benefit of using Dingo is, with Laravel 5.2? @ortho - what "boilerplate" code would I need to write for example if were to just use Laravel 5.2 "as is" for an api? My situation is that I already have an api app built with Laravel 5.2 and Dingo, and it works fine. But I'm still rather new to web apps, I'm not so sure that Dingo is still needed with 5.2 or what it gives me that I might need down the road. I started with Dingo when my app was in Laravel 4.x. And I'm wondering if I still need Dingo? Does Laravel 5.2 have more api requirements built in? So that perhaps Dingo isn't really necessary with Laravel 5.2+ ? I just would rather not use a package and worry about whether the author keeps up to date with future Laravel versions, if the package doesn't really add anything that Laravel 5.2 already provides. Thanks for any help to my quandary?
