Menu
Community /Pin to ProfileBookmark
@NogDogFeb 17.2017 — #First question I'd ask myself: "Do I really need JavaScript?" (or at least, do I really need lots and lots of JavaScript?). Are you thinking of something like VueJS because you want all sorts of eye candy that at best no users care about and at worst annoys them, or is there some [i]business[/i] reason for using it? Or do you have a good reason to make a "single page" app chock-full of JavaScript to handle it -- in which case it probably becomes its own project, which then utilizes your Laravel application purely as an API (all your Laravel views would then just be JSON output)?@NogDogFeb 17.2017 — #Take everything I say with a grain of salt, as I find the current status of the client-side world and the dozens of "new, best, fastest" JavaScript frameworks so confusing, that I just focus on server-side stuff. ? My very limited understanding of VueJS is that it's sort of a use-as-much-as-you need thing; so it doesn't have to be a single-page app to warrant using it -- but if you [i]do[/i] want to pursue the single-page app architecture, then I probably would want to use it, or AngularJS, etc., and treat it as a separate application that consumes data from your Laravel application.
Or not. ?
Is vuejs recommended for the frontend for a big website
Hello
I am developing a website similar to [url]http://www.magicbricks.com
The backend APIs are developed in laravel. For the frontend I am confused whether to use VueJS (all html files to be converted into .vue and use the power of VueJS) or use Laravel’s Blade templates and use VueJS for the reactivity part.
What is the recommended approach?
PS: I am fairly new to VueJS and this would be my first application in VueJS.
Sign in
to post a comment7 Comments(s) ↴
0
@NogDogFeb 17.2017 — #First question I'd ask myself: "Do I really need JavaScript?" (or at least, do I really need lots and lots of JavaScript?). Are you thinking of something like VueJS because you want all sorts of eye candy that at best no users care about and at worst annoys them, or is there some [i]business[/i] reason for using it? Or do you have a good reason to make a "single page" app chock-full of JavaScript to handle it -- in which case it probably becomes its own project, which then utilizes your Laravel application purely as an API (all your Laravel views would then just be JSON output)?0
@NogDogFeb 17.2017 — #Take everything I say with a grain of salt, as I find the current status of the client-side world and the dozens of "new, best, fastest" JavaScript frameworks so confusing, that I just focus on server-side stuff. ? My very limited understanding of VueJS is that it's sort of a use-as-much-as-you need thing; so it doesn't have to be a single-page app to warrant using it -- but if you [i]do[/i] want to pursue the single-page app architecture, then I probably would want to use it, or AngularJS, etc., and treat it as a separate application that consumes data from your Laravel application.Or not. ?