I think as a backend engineer, learning your first framework is the hardest part. After that, it will be much easier to switch to another framework if your company asks you to. However, it is important to choose a framework that is in demand in your area. For example, if most companies in your area use Express, it would be a waste of time to learn Symfony. It is better to focus on learning a framework that will help you land a job. Once you have a job, you can learn whatever framework you want. There is no competition between frameworks, and they all have their own purpose.
Django Rest api is almost as built in package its has part of Django documentation also if just add Django rest api you would get ur rest api. All CRUD and authentication done ✅ for all models. Unlike laravel you have build routing and controller for each model
To me Laravel and Django as FRAMEWORKS are the same in terms of difficulty, maaaybe Laravel a bit harder since the file structure is not as intuitive and simple as Django. Language wise, yes PHP is harder than Python purely by how Python writes syntax so cleanly, but is mostly that, a harder language would be C since there you have to declare everything.
choose django. Because you would have to learn python and python is a better and more complete language.You can build anything you want with python. If you want to code a blockchain app you can do it, a console app you can do it etc..
Who needs speed my friend? Both frameworks can handle the load 95% of the websites today get. If you think your app will be a new facebook you are delusional, and if you really can get there, you’ll have a lot of money to hire someone to fix the problem and you won’t even care
Sorry, cannot agree with this any less and the business use case shown isn't valid for comparison as it wasn't a fair comparison, clearly not knowing Python well enough to know it could do all Laravel could and then some. I like both Laraval and Python and both are really great, but if you don't know what you should know about what there is to know then you won't know what you're missing out on. This is by no means a true comparison.
Php8.1 onward versions have execution time way faster than python. Now, all of most popular and stable php frameworks have not yet caught up with the latest php language features.
"most popular and stable frameworks" is just Laravel and Symfony anyway... Both of them had integrate a ton of new php 8+ to their ecosystem. Most notably 8.1 enum and return type
@@khangle6872 at the end of the day you most likely do not need a framework. I used to have that mentality but contrary to what most people would argue, less is more. Why add an extra layer of complexity?
@@botcontador3286 time efficiency and consistency Back when i first learned web development, i built a system in pure java, spent months writing my own router, password hash, directory structures, etc. It was fun figuring out stuff but took way too long, i can accomplish everything i had done in those months in literally 10 minutes with Laravel. In a company, time spent is critical. It is money and the quick kickstart of framework is quite frankly indispensable. If we stop working with frameworks we would be gone in less than 6 months You could argue that i can write common components that can be copy-pasted between projects to save time. But that is literally what a framework is, if i am creating my own custom framework. I'd rather use a battle-tested one Then we also have coding style. Custom code is by default hard to onboard. We contracted a legacy Java codebase written in a custom internal framework not so long ago. There is absolutely NO document and we spend almost 2 months to figure out wtf it is doing and what belong to what. In contrast, a recent Laravel contract took us about 2-3 days to know the ins and outs, with the official documents already explain like 60-70% of the code base
Laravel hosting is more readily available compared to Django. And maybe knowing a bit more PHP is required for Laravel the environment setup for Python I always found to be pain. Especially on a Mac
guys tbh with u don't ever listen to this thing i can't believe if he knows what he's taking about . 1- django is slower cus of python 2- django has django rest framework for api support 3- django is heavy weight framework
I personally think Laravel is way easier to learn, and based on what I’ve seen recently, it’s way more feature packed than any other framework, it’s got pretty much everything you could ask for. Maybe it’s true for Django as well, but I’ve given up learning it years ago.
rest_framework in combination with drf_spectacular and djangorestframework_dataclasses is a great experience in django. You get serializer generation based on typed dataclasses full openai specifications generated for your api's and quite quick and flexible api development using function or class views, everything customizable to the core but with sensible default inital setups.
I used Octane with Swoole and my API become blazingly fast, i have compared it with Golang Fiber, and the result is very very slight difference, sometimes Fiber faster and sometimes Swoole faster. But i never Benchmark it with Jango, so curious
What's with the violent reaction with laravel has more steep learning curve than django? Probably because schools teach you php as basic starter language but for people who just started with both from scratch and no IT degree it's probably true that django is easier to learn than laravel
My school taught me C as a starter language to force to have fundamental levels of programming lol. I thank them so much, after learning C, everything was a smooth ride.
This video is full of lies. Almost every take is wrong. I don't know where to start. PHP has been faster than Python for a long time. And Laravel is by far easier to learn. The only reason Django would be easier is if you are already a python dev. Laravel has also has full stack sub-frameworks like inertia and livewire so saying its only better for API's is just a weird take.
I am quite offended by this title. Coz these apps are the same and yet so different. If you want to make yourself suffer, learn Laravel but if it's what you need to land a job, then I get you. But Django is like Laravel but like awyyyyyyy easier.
I don't necessarily think you need to shift to one or the other. Just learn the two frameworks, more power to you. Plus frameworks evolve over time, keeping pace with both them should help you as well. Plus, sometimes I think one can come up with new breaking features and you can easily pick it up since you have basic knowledge of both.
Keep learning Django. Once you get a grasp on it, learning Laravel will be way more easier as it will be a matter of comparing the different ways to do things in Laravel to Django (which you already know).
I work with Laravel. it's great and all but not a lot of job opportunities compared to Django. I'll start learning Django next because that's where the money is!
![[UNCUT] “บอสณวัฒน์” ลากไส้!! ใครหนุนหลัง "แม่ตั๊ก ป๋าเบียร์" I คนดังนั่งเคลียร์ I 30 ก.ย. 67](http://i.ytimg.com/vi/QlD7mU2KKRk/mqdefault.jpg)
the fact that he said that laravel is harder to learn than django broke my heart django is a pain for me
It's also just very much not true
it is not true. Laravel is easier to learn if you are already good with php
I think it is subjective, you can learn django faster if you have solid knowledge about python.
Coming from someone who both doesn't know python and php when i started django is easier. Don't quit tho
Why Django is pain it's just python function and tuple
I think as a backend engineer, learning your first framework is the hardest part. After that, it will be much easier to switch to another framework if your company asks you to. However, it is important to choose a framework that is in demand in your area. For example, if most companies in your area use Express, it would be a waste of time to learn Symfony. It is better to focus on learning a framework that will help you land a job. Once you have a job, you can learn whatever framework you want. There is no competition between frameworks, and they all have their own purpose.
Django Rest api is almost as built in package its has part of Django documentation also if just add Django rest api you would get ur rest api. All CRUD and authentication done ✅ for all models. Unlike laravel you have build routing and controller for each model
Python has never been faster than php
It is faster, stop your lie probaganda.
Python still remains the fastest language so far! What??? Since when 😂
Python is slowest ever.
i love python and it is the first time i heard someone said that 🤣🤣
I've not seen any language slower and sluggish than python.😂
"Steep learning curve for Laravel" - Nah
It surprises me
Coming from non IT grad. Laravel and php has steep learning curve than python and django
To me Laravel and Django as FRAMEWORKS are the same in terms of difficulty, maaaybe Laravel a bit harder since the file structure is not as intuitive and simple as Django. Language wise, yes PHP is harder than Python purely by how Python writes syntax so cleanly, but is mostly that, a harder language would be C since there you have to declare everything.
choose django. Because you would have to learn python and python is a better and more complete language.You can build anything you want with python. If you want to code a blockchain app you can do it, a console app you can do it etc..
Django is easier than Laravel...??
Brother seriously ???
Do you know Django really??
Based on your personal experience, which one was easier to learn, python or php?
Both languages was easier for me, and I started with PHP before learning Python.
@@lejames5987 python
Wtf
Do you know anything about Drf?😂😂😂
If speed is what you need, use octane
Who needs speed my friend? Both frameworks can handle the load 95% of the websites today get. If you think your app will be a new facebook you are delusional, and if you really can get there, you’ll have a lot of money to hire someone to fix the problem and you won’t even care
@@cristianbilu I see people naively saying django is faster than laravel
Speed shouldn't be a reason to use 1 framework over the other
Django is way to go. Soo happy using it and it much mature and stable than laravel. In built automatic admin creation, ORM makes it perfect.
Sorry, cannot agree with this any less and the business use case shown isn't valid for comparison as it wasn't a fair comparison, clearly not knowing Python well enough to know it could do all Laravel could and then some. I like both Laraval and Python and both are really great, but if you don't know what you should know about what there is to know then you won't know what you're missing out on. This is by no means a true comparison.
Php8.1 onward versions have execution time way faster than python. Now, all of most popular and stable php frameworks have not yet caught up with the latest php language features.
"most popular and stable frameworks" is just Laravel and Symfony anyway...
Both of them had integrate a ton of new php 8+ to their ecosystem. Most notably 8.1 enum and return type
@@khangle6872 at the end of the day you most likely do not need a framework. I used to have that mentality but contrary to what most people would argue, less is more. Why add an extra layer of complexity?
@@botcontador3286 time efficiency and consistency
Back when i first learned web development, i built a system in pure java, spent months writing my own router, password hash, directory structures, etc.
It was fun figuring out stuff but took way too long, i can accomplish everything i had done in those months in literally 10 minutes with Laravel.
In a company, time spent is critical. It is money and the quick kickstart of framework is quite frankly indispensable. If we stop working with frameworks we would be gone in less than 6 months
You could argue that i can write common components that can be copy-pasted between projects to save time. But that is literally what a framework is, if i am creating my own custom framework. I'd rather use a battle-tested one
Then we also have coding style. Custom code is by default hard to onboard. We contracted a legacy Java codebase written in a custom internal framework not so long ago. There is absolutely NO document and we spend almost 2 months to figure out wtf it is doing and what belong to what.
In contrast, a recent Laravel contract took us about 2-3 days to know the ins and outs, with the official documents already explain like 60-70% of the code base
Laravel hosting is more readily available compared to Django. And maybe knowing a bit more PHP is required for Laravel the environment setup for Python I always found to be pain.
Especially on a Mac
Php 8.1 is 3 times faster than python
yes
guys tbh with u
don't ever listen to this thing
i can't believe if he knows what he's taking about .
1- django is slower cus of python
2- django has django rest framework for api support
3- django is heavy weight framework
I personally think Laravel is way easier to learn, and based on what I’ve seen recently, it’s way more feature packed than any other framework, it’s got pretty much everything you could ask for.
Maybe it’s true for Django as well, but I’ve given up learning it years ago.
rest_framework in combination with drf_spectacular and djangorestframework_dataclasses is a great experience in django.
You get serializer generation based on typed dataclasses full openai specifications generated for your api's and quite quick and flexible api development using function or class views, everything customizable to the core but with sensible default inital setups.
Pretty sure the speed is faster on Laravel, due to new PHP 8 that is faster than Python, and combined with FPM or Octane which is blazingly fast
after python 3.11 maybe not.
nope
Nope and the annotation in python makes it better
I used Octane with Swoole and my API become blazingly fast, i have compared it with Golang Fiber, and the result is very very slight difference, sometimes Fiber faster and sometimes Swoole faster. But i never Benchmark it with Jango, so curious
Tech discussions aside, Damn I love the art style and the animations =) thumbs up!!
for APIs, Django has Django Rest Framework.
I was thinking that the entire time. Django Rest makes handling APIs as easy as in Laravel imo.
And FAST API
Django's license only needs M to be NSWF
Horizon actually is a queue manager
Author of the video: "Django good because it on Python. Laravel is worst because it on PHP". Level of competence is very low.
What's with the violent reaction with laravel has more steep learning curve than django?
Probably because schools teach you php as basic starter language but for people who just started with both from scratch and no IT degree it's probably true that django is easier to learn than laravel
My school taught me C as a starter language to force to have fundamental levels of programming lol. I thank them so much, after learning C, everything was a smooth ride.
how do you animate your videos which all are awesome🤯
Thank you. I do the animations in Adobe After Effects. 😊
Laravel is awesome!
This video is full of lies. Almost every take is wrong.
I don't know where to start. PHP has been faster than Python for a long time. And Laravel is by far easier to learn. The only reason Django would be easier is if you are already a python dev. Laravel has also has full stack sub-frameworks like inertia and livewire so saying its only better for API's is just a weird take.
I am quite offended by this title. Coz these apps are the same and yet so different. If you want to make yourself suffer, learn Laravel but if it's what you need to land a job, then I get you. But Django is like Laravel but like awyyyyyyy easier.
Is Laravel only backend?
Well, not anymore with livewire
@@hsemix yes livewire is the best
I have worked in both, but each one has their own goods and bads
guys debating why one is better than the other, POV: asking whether I can use both
Absolutely wrong comparison
As a django developer.
One thing that is missing in django is vite for frontend building
vite is amazing
That will come up in the future.
Huh? Im pretty sure you can use vite with Django just serve the main html as template
Use htmx. And tailwinds you don’t even need js 😂
@@Yarkanlaki agree
i was learning Django now i think i need to shift to laravel 😢😢
Django is good enough to create any project you dream of
@@RaefetOuafiqo but so many drawback of django 😢😢
@@kapilpoudel8452 nah it's good, ive been using it for so long, and created many high products.
I don't necessarily think you need to shift to one or the other. Just learn the two frameworks, more power to you. Plus frameworks evolve over time, keeping pace with both them should help you as well. Plus, sometimes I think one can come up with new breaking features and you can easily pick it up since you have basic knowledge of both.
Keep learning Django. Once you get a grasp on it, learning Laravel will be way more easier as it will be a matter of comparing the different ways to do things in Laravel to Django (which you already know).
I work with Laravel. it's great and all but not a lot of job opportunities compared to Django. I'll start learning Django next because that's where the money is!
Really? I've seen many more job ads about PHP than Python for Web development, especially in freelancing.
I've been bombarded by offers for laravel devs, I've yet to find one for Django.