I am a junior backend web developer who is mostly fluent in django and to some extent pure PHP. As far as I know and experienced, I feel like Django's structure makes more sense to some extent, but since I have to use laravel on my new job I have no choice but to learn it. Is anyone aware of a cheat sheet of sorts? If not can someone guide me on how laravel works compared to django, because I have had a hard time going through laravel's documentation and "translating" django's concepts to laravel
#I want to learn laravel, but know django. Can anyone help me understand the differences between them
junior plover
vapid radish
Don't try to translate django to laravel, just learn laravel.
junior plover
If I didn't have to learn laravel for my job you just told me "keep using django, you already figured that out"
sullen moth
If I didn't have to learn laravel for my job you just told me "keep using django...
I think they were merely referring to your statement about "translating django concepts to Laravel". They're different frameworks, so they work differently, they do things differently. So yes, learning how Laravel works would make you more efficient than trying to do things "the django way"
Good resources would be Laracasts (there's quite a few free courses) or the Laravel Bootcamp (https://bootcamp.laravel.com)
junior plover
Ok then, I'll check these resources out.
junior plover
I think they were merely referring to your statement about "translating django c...
Also, what I meant was a more general translation of what is what between laravel and django. As in what a view in laravel means to django so on and so forth
sullen moth
Aren't they both MVC's? No experience with django, but I see they use a slight variation, MVT. So in django a view would be somewhat similar to a controller in Laravel. A template would be similar to a view in Laravel (blade, the html)
junior plover
Seems like so, at least from what I see in the bootcamp project