Hi,
Having flirted with vue, which is obviously useful, and even got to the point of building a few simple SPAs with vue router and vuex, via some excellent courses on Udemy, I've realised that most of my app could, in fact, be built with hardly any javascript at all, which is how I kind of set out to do it in the first place in any case, following all that I've learnt here on laracasts.
In fact, I think I've decided to build it so it at least works in a basic form with javascript turned off. I could argue that I've wasted a lot of time starting with php then exploring how to do similar things with javascript.
What kind of personal guidelines do people use to help them to reduce the bamboozlement over multiple ways to achieve the same thing?
Obviously some things can only be achieved in javascript; but with that aside javascript can also take over large parts of what laravel does for us - so how do you choose when to stop?
I think I'm just going to be very old fashioned - if I can do it in php, then I will. That has the simple merit of being a discipline that I seem to be able to get a handle on. Then javascript is added but only under the assumption the site will still work without it, albeit be a bit less pretty
(some call this 'progressive enhancement').
How do others deal with the profusion of choices available when using laravel with vue.
One position would be argue for the taking of one of two extremes: either use php anywhere you can with mere sprinkling of js on top; or the reverse, go for a full SPA and have laravel provide no web routes at all.
Is that a good way to start? It's where I am now...
In saying this I have the feeling there may be a few valid 'middle roads', but I'm not entirely clear on (a) what those are and (b) how clear one can really expect to be in setting them out (e.g. use vue components but without vue router; and plenty of laravel web routes - which seems to be a natural middle way).
Not sure if any of this is all that useful but wondered if anyone had any thoughts.
Cheers
Mike
