This is a video of someone trying to learn an entire language and framework in 20 minutes without reading any docs, getting almost everything wrong, and then making conclusions based on those mistakes.
@@RawCoding try Symfony framework Laraval is great but it's like swiss army knife it even uses Symfony packages, Symfony is lighter and faster and easy to learn because you can add packges/modules with you need like you can have symfony app running even without DB adapter package
I’m sorry, but what an awkward attempt to get simple stuff done. I did .NET back in time. Today I earn my money with Laravel. From the looks of this video, you just glanced the docs. This tells us you did not go into this project with a serious attempt in mind. But I might just mistake you, for running a bit too fast ahead of yourself - but I feel you wasted your time, to give an opinion on a very small basis. I do not want to sound rude. But honestly, I don’t see the point of this video. Anyway - merry Christmas 🎄
I liked your video, in the sense that it would teach Laravel lovers how other people approach to it and how to close the gap correctly when bringing people from another languages to use Laravel. Its very insightful to know what are the first steps a senior in another language/framework would take and how to prevent them from getting frustrated when they use it for the first time. Thank you.
Anyone trying to assess something like this in 4 hours can definitely give their personal take. However, that take should be taken as it's presented--4 hours learning a language and framework. A trivial amount of effort insufficient to do anything remotely productive. Any serious consideration or conclusion is much better rendered by someone who has devoted a non-trivial amount of time to learn the tool. I would suggest watching someone on here who knows Laravel do something from scratch to get a better understanding of what a productive tool it truly is. I do think "stay with .NET" is good advice to our .NET friends if that's where they're proficient. Heck, stay with Rails or whatever else you use unless it's server-side JavaScript... then hey, come on over the water is fine.
I don't code in PHP much anymore, but Laravel really is quite amazing how much it does, and with how many amazing community tools/plugins there are. I often consider giving it a shot again after battling with Node and all the complexities that come from building a large, modern, performant full-stack site with it.
@@thelostrider1 you're right. I just checked, and now I see. Well, some chaos is happening in PHP world. It's good I switched to .NET several years ago.
@@handlez411 так вас же никто не заставляет PHP употреблять! Здесь человек собрался страдать за вас. А вы садитесь и наслаждайтесь. Я так и сделал, было круто.
The only part I agree with you on in this video is the fact that Laravel does not use the inference approach to generating migrations is disappointing. Not a big deal though. That being said, if you'd legit taken 5mins to read through the actual guide in the docs you'd have a much better experience... Legit bashing my face against my keyboard watching you try to guess stuff in a framework you're not familiar with whatsoever.
Every other "X developer tries Laravel" video out there read the docs and ended up loving it. You on the other hand made a video fiddling around aimlessly doing everything wrong (on purpose maybe?) and your conclusion was "Laravel is bad"... what a waste of time this video is. Just delete it man, it offers nothing of value. Even your opinion doesn't matter at this point.
Having used most frameworks over just sbout every language other than rust (yet), Laravel is an absolute joy to work with to just get stuff done. Trying it out with zero knowledge of the php language or ecosystem does it no justice.
I refuse to believe you spent the 4 hours you claimed you did reading docs. I don't use PHP anymore, not for years, but the Laravel docs is amongst, if not, the best docs out there. You were struggling where the views where, so you resulted in global search across the app. But when you type 'view' in the docs search bar, 1st result, 1st paragraph tells you where they are. You saw Laravel heard as an easy way to manage PHP installs, but you went the convoluted route of using brew. You're trying to figure out how the API works, but again, first page tells you pretty much everything when you search and click the first result. If you did spend 4 hours, what did you actually learn from it?
Ehm so you picked out “views” and installing the tools which were the easiest… (brew install php is as simple as it gets I could’ve probably tried that without doing any googling) Anyway I dont like tools like herd because its an app that is a fix for where someone made an installer of an installer for an setup of an app. (And if things go wrong you don’t actually understand any of the moving parts)
@@RawCoding Easiest? Yes, easiest, and yet, after 4 hours of reading docs, apparently it was still not so easy. Did you want me to fine-grain anaylse everything in the video you're questioning and put a 'search for X, and its there in the first paragraph' comment for each one, to eliminate 'easiest' thing? I picked those out as quick things that came to mind, and I didn't go any further than about 20mins IIRC because just like many others have expressed, it's mildly infuriating to watch you try to do this, in this way, when all your answers are so easily found in their docs. But my question still stands: If you did spend 4 hours, what did you actually learn from it? Because you hit a roadblock at every point when it came to framework knowledge.
Am I getting trolled here? You said I was struggling with x and y, I said actually no those parts were easy. As for hitting roadblocks when learning something new? sorry mr perfect ill try to get it right the first time. And what did I learn from the docs? Cant say I learned anything from any docs alone as I am a very hands on learner, ive read many oauth related rfcs and had to experiment with a running system for a long time before I really understood what the docs were talking about. So take it easy pal.
@@RawCoding My apologies on that part, for I had misunderstood by what you meant by easiest. I had thought you meant I had picked out the easiest things to criticise in the video, and in that context, it came across a little.. ironic? Reading RFC's are typically 10x much more challenging because they're usually just blocks and blocks of raw text. So, I understand you, and I'm with you on that one. The Laravel docs however, give you everything you need to know, in a digestible, easy to find, and understandable format to get running and building an application within lets say 10-20 mins, provided you actually read it.
Big fan of your videos! I also knew how this video was going to go before I even finished watching it, lol. I'm a .NET developer in my day job, and a PHP/Ruby/Go/etc. developer at night, and Laravel is actually *really* nice. Someone correct me if I'm wrong, PHP is inherently stateless. It loads everything per request and tears it down after the request is finished. So the global state thing you were trying wouldn't work. This presents some problems, but also has a lot of benefits too. There are tools like Roadrunner, Swoole, or Octane (which uses the aforementioned tools), which will run your Laravel code in a process-like model. You could also use one of the many cache providers built-in for this purpose as well. Not sure why global state is something important in a demonstration like this, but there are options if you need to do it. Not sure what the issue was around the components/CLI or the comparison to Angular? You can certainly create multiple things, all at the same time. Laravel has command line flags to generate controllers, models, migrations, etc. in one go. You can also do it piecemeal if you'd like as well. There's a lot of things you didn't touch on, which I think are important for consideration. Laravel has a lot of first-party tools, for virtually everything, and while not everyone likes them, in my opinion they are all awesome and well designed especially in regards to UI. Things like Jetstream, Breeze, Horizon, Spark, Forge, Vapor, etc. Laravel also has a very strong third-party community with things like Tinkerwell, Livewire, Inertia, etc. Laravel's testing tools are only rivaled by Rails, in my opinion, and there's even a first party UI-testing framework built on Selenium. The same goes for it's job system which rivals a lot of the things you'd find in something like Sidekiq. And almost all of this stuff is *free*. Different strokes for different folks of course, but the only thing I can think of that's significantly better in ASP.NET versus Laravel is the performance. I think you gave it a fair shake, but I implore you to give it another shake and everyone else as well. Laravel is really awesome.
In contrast to you, I'm Laravel developer trying to learn .NET Core. Is there any alternative to Inertia for .NET? The community adapter for it doesn't seem to be maintained anymore.
42:07 You'll definitely try everything again if you read the documentation 🤣🤣🤣 3 weeks ago I tried Laravel for the first time and wondered why I hadn't been using it.
44:22 It is happening to you because you don't understand anything bout how it works, you have picked up a tool and expect it to work like every other tool without taking the time to read the manual 🤣🤣🤣
I hope this video was ment as a joke, cause this was the most painful thing I've ever watched when it comes to programming. If this was actually serious, then you should probably take a look at the docs. I don't use Laravel, but even for me this was like watching someone who has never ever touched code before trying to make something work.
42:49 Everything you've done here means that you've just done this for the video and don't care bout learning how Laravel really works. Just read the docs
That was my first language. And for me living without global state that was nothing special. PHP was borne to die, remember? Then I moved to C# and that was a very big surprise when I finally got a normal runtime.
"Even though I used a command to generate migration I still have to add this shit (columns)" lmao were you really expecting it to write all the database schema from just the model name you gave?
I get that this video is for the memes and trying to get something to work ASAP and I love it but for those that don't, Laravel has great documentation that will help you understand how to use the framework for the things he tried in the video. He tried a couple of things in the video in a C#/.NET way, which isn't really a good approach to learning an opinionated framework, even more that it's written in a different language. Love the torment in this video. Looking forward to the RoR one next year!
Thanks for the video, but it's actually surprising how you managed to do everything wrong haha. Maybe it's the familiarity at this point, but for me it feels so intuitive...
Great vid! I believe that when you start learning a new language or framework, setting a clear goal or project tod do will help you eventualy acquire the necessary skills and knowledge along the journey. As many devs out there I usually start with Blog or portfolio then move to higher more complicated things. I would love to see same vid using Go, Rust and Node.
All good things look scary at first. You might need to look again. I have both of them and while I wish The .NET and EF could be as intuitive as Laravel and Eloquent I wish the latter could reach the speed of the .NET and EF and then i will switch completed to Laravel and Eloquent .
I have 6 years of laravel experiences but I enjoyed with your process map so if I want to learn a python or something I'm not gonna be afraid about that
I'd thought people should've already concluded by now that behaviour driven by convention is not really a good thing. That's why frameworks are so hard to adopt and it's so damn hard to get out of that mentality. These kind of frameworks really mess with your head, they are like a cult.
😂 this is scary so I am not gonna go into that… migrations are actually same as ef migrations with up and down. Spend a bit more time reading things. You did well getting to where you are but skipping a lot meant bad experience at the end. Try again coming with MVC pattern hat.
That is funny... When I used to code in PHP I did a lot of "decompilation" investigation and that kind of stuff with PHPStorm. That was actually what taught me so much stuff about design patterns (back in the day I used Zend Framework). Not sure why it doesn't work for u.
22:48 "...where I can just take off the hood and take a look at the source code." The source code doesn't really help much. A lot of things are abstracted via Laravel's "Facades". Laravel is a framework built with development convenience first in mind and I think it does an excellent job at that. Initial setup definitely sucks but I'll choose this mess over most JS backends. Those string arguments in facades are really annoying for me, how is a beginner supposed to know what they mean or where to look for the valid values for them? Currently learning .NET Core, I do miss some of the convenience Laravel provides but I like that it's easier to understand what's happening under the hood.
This is a video of someone trying to learn an entire language and framework in 20 minutes without reading any docs, getting almost everything wrong, and then making conclusions based on those mistakes.
I think the only thing thats disappointing me here is that I did read the docs and it took me almost 4 hours, and I still got everything wrong.
@@RawCoding Then you should go back to basics
I think you’re right sir what do you recommend?
@@RawCoding Ask chatgpt
@@RawCoding try Symfony framework Laraval is great but it's like swiss army knife it even uses Symfony packages, Symfony is lighter and faster and easy to learn because you can add packges/modules with you need like you can have symfony app running even without DB adapter package
I’m sorry, but what an awkward attempt to get simple stuff done.
I did .NET back in time. Today I earn my money with Laravel.
From the looks of this video, you just glanced the docs.
This tells us you did not go into this project with a serious attempt in mind. But I might just mistake you, for running a bit too fast ahead of yourself - but I feel you wasted your time, to give an opinion on a very small basis.
I do not want to sound rude. But honestly, I don’t see the point of this video.
Anyway - merry Christmas 🎄
I liked your video, in the sense that it would teach Laravel lovers how other people approach to it and how to close the gap correctly when bringing people from another languages to use Laravel.
Its very insightful to know what are the first steps a senior in another language/framework would take and how to prevent them from getting frustrated when they use it for the first time.
Thank you.
You gotta read the documentation. Who learns how to walk by doing cart wheels ???
17:52 Just read the documentation 🤣🤣🤣
Anyone trying to assess something like this in 4 hours can definitely give their personal take. However, that take should be taken as it's presented--4 hours learning a language and framework. A trivial amount of effort insufficient to do anything remotely productive. Any serious consideration or conclusion is much better rendered by someone who has devoted a non-trivial amount of time to learn the tool. I would suggest watching someone on here who knows Laravel do something from scratch to get a better understanding of what a productive tool it truly is. I do think "stay with .NET" is good advice to our .NET friends if that's where they're proficient. Heck, stay with Rails or whatever else you use unless it's server-side JavaScript... then hey, come on over the water is fine.
🫡
I don't code in PHP much anymore, but Laravel really is quite amazing how much it does, and with how many amazing community tools/plugins there are. I often consider giving it a shot again after battling with Node and all the complexities that come from building a large, modern, performant full-stack site with it.
PHP is fun.... that was my main language 15 years ago.
Thank you Microsoft for incorporating all the tools i need in one area. Was completely overwhelmed but im fine now.
here i am a Laravel developer trying to learn .net
I have been working on Laravel for 6 years and still loving and never used Route::cache, pretty amazing how poeple are annoyed with php :D
Wanna have a small template without the stuff? Try Lumen. From the same author but without the redundant stuff.
Laravel Lumen is not recommended since a long time. It even says in the installation guide
@@thelostrider1 you're right. I just checked, and now I see. Well, some chaos is happening in PHP world. It's good I switched to .NET several years ago.
охохохох!!! Да ну нафиг! Сразу лайк! Пошел чай себе заваривать! Прикольно, у тебя, похоже, рубрика "страдаем фигней в крисмас тайм"))
Я бы с удовольствием выпил чашку чая, только без php!
@@handlez411 так вас же никто не заставляет PHP употреблять! Здесь человек собрался страдать за вас. А вы садитесь и наслаждайтесь. Я так и сделал, было круто.
Это было круто, но было ужасно смотреть, как он так страдает!@@ИванИванов-я5э9к
Laravel is a waste of time. Just use Raw PHP like God intended.
I don't know how you managed to do everything completely wrong!
The only part I agree with you on in this video is the fact that Laravel does not use the inference approach to generating migrations is disappointing. Not a big deal though.
That being said, if you'd legit taken 5mins to read through the actual guide in the docs you'd have a much better experience... Legit bashing my face against my keyboard watching you try to guess stuff in a framework you're not familiar with whatsoever.
Every other "X developer tries Laravel" video out there read the docs and ended up loving it. You on the other hand made a video fiddling around aimlessly doing everything wrong (on purpose maybe?) and your conclusion was "Laravel is bad"... what a waste of time this video is. Just delete it man, it offers nothing of value. Even your opinion doesn't matter at this point.
*Opens file*
"That looks scary, I'm gonna ignore that"
Basically my whole work day.
Having used most frameworks over just sbout every language other than rust (yet), Laravel is an absolute joy to work with to just get stuff done. Trying it out with zero knowledge of the php language or ecosystem does it no justice.
I refuse to believe you spent the 4 hours you claimed you did reading docs. I don't use PHP anymore, not for years, but the Laravel docs is amongst, if not, the best docs out there. You were struggling where the views where, so you resulted in global search across the app. But when you type 'view' in the docs search bar, 1st result, 1st paragraph tells you where they are. You saw Laravel heard as an easy way to manage PHP installs, but you went the convoluted route of using brew. You're trying to figure out how the API works, but again, first page tells you pretty much everything when you search and click the first result. If you did spend 4 hours, what did you actually learn from it?
Ehm so you picked out “views” and installing the tools which were the easiest… (brew install php is as simple as it gets I could’ve probably tried that without doing any googling)
Anyway I dont like tools like herd because its an app that is a fix for where someone made an installer of an installer for an setup of an app. (And if things go wrong you don’t actually understand any of the moving parts)
@@RawCoding Easiest? Yes, easiest, and yet, after 4 hours of reading docs, apparently it was still not so easy.
Did you want me to fine-grain anaylse everything in the video you're questioning and put a 'search for X, and its there in the first paragraph' comment for each one, to eliminate 'easiest' thing?
I picked those out as quick things that came to mind, and I didn't go any further than about 20mins IIRC because just like many others have expressed, it's mildly infuriating to watch you try to do this, in this way, when all your answers are so easily found in their docs.
But my question still stands: If you did spend 4 hours, what did you actually learn from it? Because you hit a roadblock at every point when it came to framework knowledge.
Am I getting trolled here?
You said I was struggling with x and y, I said actually no those parts were easy.
As for hitting roadblocks when learning something new? sorry mr perfect ill try to get it right the first time.
And what did I learn from the docs? Cant say I learned anything from any docs alone as I am a very hands on learner, ive read many oauth related rfcs and had to experiment with a running system for a long time before I really understood what the docs were talking about.
So take it easy pal.
@@RawCoding My apologies on that part, for I had misunderstood by what you meant by easiest. I had thought you meant I had picked out the easiest things to criticise in the video, and in that context, it came across a little.. ironic?
Reading RFC's are typically 10x much more challenging because they're usually just blocks and blocks of raw text. So, I understand you, and I'm with you on that one.
The Laravel docs however, give you everything you need to know, in a digestible, easy to find, and understandable format to get running and building an application within lets say 10-20 mins, provided you actually read it.
Big fan of your videos! I also knew how this video was going to go before I even finished watching it, lol.
I'm a .NET developer in my day job, and a PHP/Ruby/Go/etc. developer at night, and Laravel is actually *really* nice.
Someone correct me if I'm wrong, PHP is inherently stateless. It loads everything per request and tears it down after the request is finished. So the global state thing you were trying wouldn't work. This presents some problems, but also has a lot of benefits too. There are tools like Roadrunner, Swoole, or Octane (which uses the aforementioned tools), which will run your Laravel code in a process-like model. You could also use one of the many cache providers built-in for this purpose as well. Not sure why global state is something important in a demonstration like this, but there are options if you need to do it.
Not sure what the issue was around the components/CLI or the comparison to Angular? You can certainly create multiple things, all at the same time. Laravel has command line flags to generate controllers, models, migrations, etc. in one go. You can also do it piecemeal if you'd like as well.
There's a lot of things you didn't touch on, which I think are important for consideration. Laravel has a lot of first-party tools, for virtually everything, and while not everyone likes them, in my opinion they are all awesome and well designed especially in regards to UI. Things like Jetstream, Breeze, Horizon, Spark, Forge, Vapor, etc.
Laravel also has a very strong third-party community with things like Tinkerwell, Livewire, Inertia, etc.
Laravel's testing tools are only rivaled by Rails, in my opinion, and there's even a first party UI-testing framework built on Selenium. The same goes for it's job system which rivals a lot of the things you'd find in something like Sidekiq. And almost all of this stuff is *free*.
Different strokes for different folks of course, but the only thing I can think of that's significantly better in ASP.NET versus Laravel is the performance.
I think you gave it a fair shake, but I implore you to give it another shake and everyone else as well. Laravel is really awesome.
In contrast to you, I'm Laravel developer trying to learn .NET Core. Is there any alternative to Inertia for .NET? The community adapter for it doesn't seem to be maintained anymore.
@@fyodor2540 Not that I'm aware of. I wasn't even aware someone made an adapter for .NET.
@@fyodor2540 Interia is trivial to adapt to your usecase.
This is why people hate PHP/Laravel because these people don't know how to read docs and just making assumptions.
he just need reactions from PHP community to gain views brother 😂😂🤣🤣
42:07 You'll definitely try everything again if you read the documentation 🤣🤣🤣
3 weeks ago I tried Laravel for the first time and wondered why I hadn't been using it.
44:22 It is happening to you because you don't understand anything bout how it works, you have picked up a tool and expect it to work like every other tool without taking the time to read the manual 🤣🤣🤣
.Net Jesus turning into .Net Santa 🎅
just read the documentation please, instead just going from what you think
a php server starts a new instance of the app on every request. that's why the state wasn't updating.
47:23 No, you disappointed Laravel 🤣🤣🤣
If it was easy everyone would have a lambo 😏
please read docs
Very unpleasant to watch this video :D
Trying a new language and framework with old unfashionable and bad habits ..
I hope this video was ment as a joke, cause this was the most painful thing I've ever watched when it comes to programming. If this was actually serious, then you should probably take a look at the docs. I don't use Laravel, but even for me this was like watching someone who has never ever touched code before trying to make something work.
This is such a poor attempt!
You must learn from another programmer dude.... if you do that like you did it you will make a lot of errors and trash
42:49 Everything you've done here means that you've just done this for the video and don't care bout learning how Laravel really works. Just read the docs
That was my first language. And for me living without global state that was nothing special. PHP was borne to die, remember? Then I moved to C# and that was a very big surprise when I finally got a normal runtime.
Anton, maybe fuck all these web frameworks? They are +/- the same. Maybe next year u try to make a game with Unity?
"Even though I used a command to generate migration I still have to add this shit (columns)"
lmao were you really expecting it to write all the database schema from just the model name you gave?
Yeah, .net has entityframework which does that. (Spring orm does it too)
We also have Marten in .net which will update the database on the fly.
I get that this video is for the memes and trying to get something to work ASAP and I love it but for those that don't, Laravel has great documentation that will help you understand how to use the framework for the things he tried in the video. He tried a couple of things in the video in a C#/.NET way, which isn't really a good approach to learning an opinionated framework, even more that it's written in a different language. Love the torment in this video. Looking forward to the RoR one next year!
Imagine writing all that documentation and then watching this video. DUDE reads the docs and stop hurting yourself lmao
Lesson learned: RTFD
Arrive here for dotnet videos... Leaving without looking back after this crap
Almost all the problems you faced, would be a piece of cake if you read the documentation.
But, good video from a .NET developer.
Maybe you could try Ruby on Rails next? I have little knowledge of it but some of my colleagues are Ruby enthusiasts and they keep praising it
Good idea, next year ))
I do write api in laravel(php) as well as in c#(.net). you have gone quite well. but you been funny as you over look and over kill lot of steps.
Laravel is good, stuff just happens under the hood but when you get the knowledge from docs how things work it's really powerful
Thanks for the video, but it's actually surprising how you managed to do everything wrong haha. Maybe it's the familiarity at this point, but for me it feels so intuitive...
Great vid! I believe that when you start learning a new language or framework, setting a clear goal or project tod do will help you eventualy acquire the necessary skills and knowledge along the journey. As many devs out there I usually start with Blog or portfolio then move to higher more complicated things.
I would love to see same vid using Go, Rust and Node.
Once you go php you never go back
ugh, I tried to like PHP for a long time (years, actually) - it is abysmally bad. The fact it is liked by so many people gives me no hope in humanity.
It’s terrible other than for folks who have no formal cs education and need to pay bills or buy lambos (1 every 3 million)
I love all this hardcoded shit... makes sense
raw coding with raw beard? I like it!
48:08 yes it is a monolith framework dude !
for the views?
All good things look scary at first. You might need to look again. I have both of them and while I wish The .NET and EF could be as intuitive as Laravel and Eloquent I wish the latter could reach the speed of the .NET and EF and then i will switch completed to Laravel and Eloquent .
I have 6 years of laravel experiences but I enjoyed with your process map so if I want to learn a python or something I'm not gonna be afraid about that
I'd thought people should've already concluded by now that behaviour driven by convention is not really a good thing. That's why frameworks are so hard to adopt and it's so damn hard to get out of that mentality. These kind of frameworks really mess with your head, they are like a cult.
😂 this is scary so I am not gonna go into that… migrations are actually same as ef migrations with up and down. Spend a bit more time reading things. You did well getting to where you are but skipping a lot meant bad experience at the end. Try again coming with MVC pattern hat.
Trying to build instagram clone with .Net and pure javascript, do you have any video recommandations in your channel?
That is funny... When I used to code in PHP I did a lot of "decompilation" investigation and that kind of stuff with PHPStorm. That was actually what taught me so much stuff about design patterns (back in the day I used Zend Framework). Not sure why it doesn't work for u.
Try Symfony, a php framework, it will satisfy you.
PHP makes me cry, the arrows are so ugly
bro watching you is soo entertaining, this is gold
what extension are you using for the readme.md file?
Try Rails now
php + artisan = partisan
please try Elm or F# :)
The problem with senior developers is that they think they know everything, and start doing the way where they are senior at.
12:30 No law says you have to close it, man 🤣🤣🤣
In fact you should never close it, cause any characters after closing tag are not code, but printed out and may cause problems.
It was great watching you suffer. Long live .NET!
Looks like you really have not tried express.js, if you think Minimal APis was influenced by Laravel.
Php😅
laravel is the beast
but php is the worst
worse than javascript? @@ИванИванов-я5э9к
Cool video. Beard looking great btw haha
Thank you boss )
Yup, tried laravel once. I had ptsd after seeing the amount of config and gymnastics you had to do for simple stuffs
So then I know you lied, cause its actually the opposite
I he had follow the DOC it would have been ready in 3 min
Yeah, good luck coming from a single fille application with no dependencies to what you call a framework
I know a lot of people love Laravel, but I think it is too bloated. Vanilla PHP + Composer for the win.
try with Next.Js 14 may be better than PHP
Nextjs is poopie
22:48 "...where I can just take off the hood and take a look at the source code." The source code doesn't really help much. A lot of things are abstracted via Laravel's "Facades". Laravel is a framework built with development convenience first in mind and I think it does an excellent job at that. Initial setup definitely sucks but I'll choose this mess over most JS backends. Those string arguments in facades are really annoying for me, how is a beginner supposed to know what they mean or where to look for the valid values for them? Currently learning .NET Core, I do miss some of the convenience Laravel provides but I like that it's easier to understand what's happening under the hood.
beginner will just follow the doc first, not click on everything and hope to understand
The source code absolutely does help. A Facade is just a static proxy, and it isn't used internally -- services are injected or located.
Ok, I am about to start watching this video, but I just have one very simple question, .... WHY???.... lol
why not?
Nah bro aged 10 years with that beard
Do .net MAUI