I've watched a lot of videos and tutorials, and read a lot of resources online. This is the best explanation of MVC that I've come across. *subscribed*
I guess Im randomly asking but does someone know of a tool to get back into an Instagram account..? I was dumb forgot my login password. I would love any assistance you can offer me
I rarely like or comment on a youtube video but this video is an exception. I watched over more than tens of MVC videos and I never understand them but after I watched this I really understand WHAT THE HELL IS MVC lol. Really thanks man I appreciate your simple explanation. Now I can do my own framework in peace :)
You've got to be careful when you watch this video as terms are not used rigorously but loosely. Structure, Process, workflow... The database is NOT the model. The view is Not the client and the server is NOT the controller!!! i would recommend watching other videos on this subject too and comparing them but don't use this as just one video to understand the concepts!!!
Note for others on what he said at 16:30. I was really confused by this as I found in some other explanations that the model can communicate with the view directly. MVC can be implemented in many ways. One of them is where the model communicates with the view directly. Is it the neatest way? I don't know. So, don't get confused when you find different explanations for the MVC. For example, some will call it a design pattern, others will call it an architectural style. It all depends on the context you're using it.
Great vid man I've been using MVC so long but didnt realize its called this...I've always programmed in this way because it makes things flow so much better
I'm 13 minutes in, and he still haven't really started yet... He's just talking about web servers and databases and programming languages. Nothing yet that helps me understand MVC at all.
Thanks for putting this together. It's a great starting point for those just beginning to look at MVC, like me. It takes existing client-server concepts and relates them to MVC, which I found useful. We'll done.
Your video said the model never talks to the view and the view never talks to the model. That does not fit the standard MVC UML diagram logic. It is more akin to the 3-tier architecture. I think the view does talk to the model when instructed to do so by the controller. [Happy to be corrected in my thought, as I am still learning]
Yes it's definitely not the MVC pattern described in my uni text books. The Controller isn't supposed to be an Adapter for communication from Model to View, but only (for user input) from View to Model. Oh well, as long as one uses the pattern to solve a problem and not just to use a pattern for the sake of using patterns, it should be fine.
Yes he is explaining the MVP pattern design. This stack overflow link explain the difference stackoverflow.com/questions/2056/what-are-mvp-and-mvc-and-what-is-the-difference
your explanation is just more than awesome :D I finally understood mvc why dont u make a video to explain what is framework programming . I'm sure I will understant it from u !!!!
Mr. Curtis, great job! Beautifully made video; good slides, great graphics and certainly good instruction. There were a few times where you seemed to talk yourself out on a limb though, and I would say do less of that. Maybe keep flashcards or something! Certainly have the best MVC video though, and I really appreciate all I was able to gain from it. Keep it up! Great job!
5:00 starts explaining web (recommended for beginners) 15:50 starts explaing mvc (here it begin) 19:00 quick recap i would still recommend beginning at 0:00 for the sake of great effort what is here made . Thanks you very much for the explaination devMarketer!
Yeah, it's a bit confusing when the recap adds route processing and has the view interacting with the user before the controller actually receives the dynamically processed view response. Kinda like saying it goes to all the trouble of finding the correct controller to just toss it out of the equation after the view is hit with a request. It's a stupidly simple concept though, so it doesn't really matter. The only thing to remember seems to be User->Controller->Model->Controller->View->Controller->User. Basic "pipeline" or "black box" architecture that allows things to interact in a way that gives you less and less job security the better it's implemented. But luckily you're always working to impress the next guy that pays you more money to do a thing and gaining practical knowledge along the way to make sure there's an ample supply of those.
That's one of the best Web Development classes I ever watched! It made me understand how MVC works in less than 20 minutes! Awesome! Thank you @jacurtis !
Still confused. Not by this video, but when I actually look at MVC code it makes no sense. In Laravel for example, routes are in their own folder, and the views are in the resources/views folder, but where's model and controllers? I can find a Controllers folder in the app/Http folder, but it doesn't seem to do anything (there's no logic in it). I can't even find a "model" folder at all. So if it's MVC, why is everything hidden and mislabeled? And why does this make things easier? I typically see people repeating code to a MUCH higher degree with MVC. It seems like you need to do the same thing over and over again with MVC. Totally lost, and this video only confuses me more because while it seems simple, I can see nothing simple about any program that uses the model.
very very very bad explanation of the mvc pattern. Not only you barely talk about it, but you seem to not even understand what MVC is, or the fact that you have front end mvc, backend mvc, etc. You only confuse people.
Thanks so much for this video, I have been trying to understand this for months ( I am brand new to programming) and this video is really making it understandable. This is going to help me get a job, I can't thank you enough.
This is not MVC. it's kind of close to MVP, but not completely. actually what you've described would negate the whole purpose of MVC, MVP, MVVM etc. What in the heart of any of those architecture is separating the Model from the View. the Model is a GIVEN(!) and so is the View, what separates them can be a Controller, a Presenter or just a ViewModel, but none of them know nothing about the View, or else our View will never be reusable because it still has a 1:1:1 relation with the Controller and the Model. With MVC the Controller just updates the Model with the user's request (i.e. the operation the user wish to do on the data, such as 'give me a list', 'save this item' etc.) and then leave it for a View to query the Model and be able present the same data in many different ways, regardless the controller that updated the model.
I really like how you explained MVC, it is really clear to me now, thank you so much. I checked to see if you have an explanation of MVVM, but it seems you don't. Any plans on creating one or is there a video you recommend?
Thanks Jacurtis. Video was great in explaining all about MVC and now I real understand it. Had gone to Treehouse.com and Lynda.com but did not understand it at all. Will Keep watching all videos on Laravel.
I'm enjoying this tutorial - part-way through so far. Cudos - it's good. (Helpful). Made me chuckle though when presenter said something like "WordPress is Apache / Linux". I've only ever ran it, personally, on Windows, and mostly on IIS. (I like linux too - and embedded systems ... but I do like Windows. And PHP as well ... and just to pre-empt some of the haters, also assembly, C, C++, C# and so on [I have an electronics/systems background] ... I think there often seems an incredible amount of prejudice around, lack of imagination, ignorance and so on - it's almost funny).
Hm came here to learn about MVC as an iOS developer and been watching it for 10 minutes. Had to drop watching just because it seemed to have a lot of filler information..
I've watched a lot of videos and tutorials, and read a lot of resources online.
This is the best explanation of MVC that I've come across.
*subscribed*
I guess Im randomly asking but does someone know of a tool to get back into an Instagram account..?
I was dumb forgot my login password. I would love any assistance you can offer me
Came here for 100Devs and this is a solid explanation! Thank you for this!
7 years later, still a great resource. Thank you!
Your teaching really helped me understand quickly what MVC means in programming. Thank you for sharing your knowledge with all of us!
Coming from #100Devs. This was a fab intro for someone who just heard of MVC.
I'm sure you're building awesome apps by now. I'm currently on the MVC class.
niceeeeee
Thank you for this, this is the only video I've seen which properly explains MVC
Best MVC tutorial I have ever seen before !!!! Thanks Jacurtis.
I rarely like or comment on a youtube video but this video is an exception. I watched over more than tens of MVC videos and I never understand them but after I watched this I really understand WHAT THE HELL IS MVC lol. Really thanks man I appreciate your simple explanation. Now I can do my own framework in peace :)
very useful, finally understand mvc. i read about it before and it was useless. very clear, descriptive easy to understand.
This is great information. Seriously
This will save you massive amounts of tutorial time.
Our Coding Bootcamp gave a link for this explanation of MVC before we have a unit on it. Great run-down!
Very clear and concise. I love learning about the principal and/or concepts before focusing on the "how" - Great! explanation.
Best explanation of the MVC structure, love the presentation!
Amazing, now it makes sense, I will remember this thing throughout my life!
Thank you.
This is more explanatory thanks!!!!
Thank you so much for these, I really enjoy your way of visually showing what's happening in your videos.
oh my gosh, i finally understand MVC @__@ thank you
tu tambem és.....
Most clear presentation I have ever seen on MVC. Thank you for clearing up my confusion.
An example of genuine teaching
This is by far the most helpful explanation!!
The best explanation of mvc
Thank you so much, finally understand MVC patterns
Thanks! I'm using Spring MVC and this gave me the background I wanted, including the history in the beginning.
You've got to be careful when you watch this video as terms are not used rigorously but loosely. Structure, Process, workflow... The database is NOT the model. The view is Not the client and the server is NOT the controller!!!
i would recommend watching other videos on this subject too and comparing them but don't use this as just one video to understand the concepts!!!
Thanks! That diagram definitely helped clear up the concept
Note for others on what he said at 16:30. I was really confused by this as I found in some other explanations that the model can communicate with the view directly.
MVC can be implemented in many ways. One of them is where the model communicates with the view directly. Is it the neatest way? I don't know.
So, don't get confused when you find different explanations for the MVC. For example, some will call it a design pattern, others will call it an architectural style. It all depends on the context you're using it.
Thank you for explaining this so well mate.
Just to clarify - you were saying "lolcats", right?
Great vid man I've been using MVC so long but didnt realize its called this...I've always programmed in this way because it makes things flow so much better
This was very helpful! Thanks for all your hard-work.
Hats off to you, finally now it makes sense! Thank you!
Super useful! I just saw the video and I feel capable to explain to anybody what MVC is. (PD> English is not my first language)
yeah this is a great description of MVC
Skip to 5:30 for the tutorial........ yikes.
I'm 13 minutes in, and he still haven't really started yet... He's just talking about web servers and databases and programming languages. Nothing yet that helps me understand MVC at all.
pro tip: speed at x1.25 or x1.5
a saviour
Thank you! What a waste of fucking time.
true hero!
Amazing explanation, thank you for your clear answer! This video is very well structured video!
The best 25 minutes of my life.
thanks jacurtis you are a good expliner my friend :)
100Devs brought me here, thanks for the lesson!
thanks Jacurtis, very well put together video. I now understand MVC now
Thanks for putting this together. It's a great starting point for those just beginning to look at MVC, like me. It takes existing client-server concepts and relates them to MVC, which I found useful. We'll done.
This is a damn awesome Explaination. Especially after showing the diagrams of the client server and database :) thanks
best video I have seen on MVC
An absolutely fantastic explanation. This has really cleared things up for me.
thank you, I understand MVC now (UI designer here)
Your video said the model never talks to the view and the view never talks to the model. That does not fit the standard MVC UML diagram logic. It is more akin to the 3-tier architecture. I think the view does talk to the model when instructed to do so by the controller. [Happy to be corrected in my thought, as I am still learning]
genuine question tho, why would the view talk to the model directly, if anything it needs to go thru the controller in terms of networking isnt it - ?
This should have been required to watch the first day of my internship :(
GOSH IK THIS WAS 3 YEARS AGO BUT IT WAS SO RELATABLE, dude just give us one vid which is not beginners friendly at all T.T
No one can explain MVC better than you did
Nice explanation of MVC. Well done!
Amazing explanation, I'll have to watch a few more times cause I'm a slow learner but it is very clear and thank you for your help.
Is it possible that you described a MVP? What would you say is the difference between MVC or MVP?
I think so, right? Not sure this is a MVC... wouldn't a view AND the controller talk with the Model?
Yes it's definitely not the MVC pattern described in my uni text books. The Controller isn't supposed to be an Adapter for communication from Model to View, but only (for user input) from View to Model.
Oh well, as long as one uses the pattern to solve a problem and not just to use a pattern for the sake of using patterns, it should be fine.
Yes he is explaining the MVP pattern design. This stack overflow link explain the difference stackoverflow.com/questions/2056/what-are-mvp-and-mvc-and-what-is-the-difference
The MVP in 1992 was Michael Jordan.
hitman98761 you just made my day :D
Excellent explanation👏
Very good explanation. Wish you had such a good teacher as you yourself are cause all I needed to understand the concept behind it, was this video.
Thanks for this very helpful video, finally cleared my confusion.
Some constructive criticism: Explanations were good... when on-topic. Too many instances of going off on tangents, which can be distracting.
MVC was really easy to understand and follow. I posted some comments for study notes and space repetition on my dev twitter account.
your explanation is just more than awesome :D I finally understood mvc
why dont u make a video to explain what is framework programming . I'm sure I will understant it from u !!!!
Um, no mention of ASP.NET? :| I didn't even hear about cake php until now
he mentioned it at about 10:28
very great helpful and clear, good Job!!
Mr. Curtis, great job! Beautifully made video; good slides, great graphics and certainly good instruction. There were a few times where you seemed to talk yourself out on a limb though, and I would say do less of that. Maybe keep flashcards or something! Certainly have the best MVC video though, and I really appreciate all I was able to gain from it. Keep it up! Great job!
Thanks for the advice and feedback. Ill take it into consideration.
you can probably skip to 14:30 actually
Great explanation. Thanks.
really nice explanation of MVC. Thank you :)
solid, platform&language independent. the crux - as always - is in the routing
This is traditional web application process. It's not MVC architecture
5:00 starts explaining web (recommended for beginners)
15:50 starts explaing mvc (here it begin)
19:00 quick recap
i would still recommend beginning at 0:00 for the sake of great effort what is here made .
Thanks you very much for the explaination devMarketer!
Yeah, it's a bit confusing when the recap adds route processing and has the view interacting with the user before the controller actually receives the dynamically processed view response. Kinda like saying it goes to all the trouble of finding the correct controller to just toss it out of the equation after the view is hit with a request. It's a stupidly simple concept though, so it doesn't really matter. The only thing to remember seems to be User->Controller->Model->Controller->View->Controller->User. Basic "pipeline" or "black box" architecture that allows things to interact in a way that gives you less and less job security the better it's implemented. But luckily you're always working to impress the next guy that pays you more money to do a thing and gaining practical knowledge along the way to make sure there's an ample supply of those.
Thank you, I have found your video really helpful, I'll definitely follow your channel for more interesting lessons. Keep it up! respect :)
That's one of the best Web Development classes I ever watched! It made me understand how MVC works in less than 20 minutes! Awesome! Thank you @jacurtis !
this was such a nice presentation... thank you !! hope the rest of your videos clear as this haha
its all Laravel :( nooooooooooo. thanks though :)
This was incredibly helpful, thank you!
Anyone from #100devs ? Nice video on MVC, thank you!
Technically, the view t alks to controller via interface.
Directly or indirectly.
Still confused. Not by this video, but when I actually look at MVC code it makes no sense. In Laravel for example, routes are in their own folder, and the views are in the resources/views folder, but where's model and controllers? I can find a Controllers folder in the app/Http folder, but it doesn't seem to do anything (there's no logic in it). I can't even find a "model" folder at all. So if it's MVC, why is everything hidden and mislabeled?
And why does this make things easier? I typically see people repeating code to a MUCH higher degree with MVC. It seems like you need to do the same thing over and over again with MVC. Totally lost, and this video only confuses me more because while it seems simple, I can see nothing simple about any program that uses the model.
Hello, Laravel has a strange strucutre. You could check this tutorial series where you can learn how more about it. laracasts.com/skills/laravel
This is strongly recommended to one who starts learning MVC. Thanks bro for a very clear video.
very very very bad explanation of the mvc pattern. Not only you barely talk about it, but you seem to not even understand what MVC is, or the fact that you have front end mvc, backend mvc, etc. You only confuse people.
thank you i finally understand MVC funny enough i have been doing what seems to be MVC
That was amazing explanation. Thank you!
Excellent video. Thanks!!
Thanks so much for this video, I have been trying to understand this for months ( I am brand new to programming) and this video is really making it understandable. This is going to help me get a job, I can't thank you enough.
This is not MVC. it's kind of close to MVP, but not completely. actually what you've described would negate the whole purpose of MVC, MVP, MVVM etc. What in the heart of any of those architecture is separating the Model from the View. the Model is a GIVEN(!) and so is the View, what separates them can be a Controller, a Presenter or just a ViewModel, but none of them know nothing about the View, or else our View will never be reusable because it still has a 1:1:1 relation with the Controller and the Model.
With MVC the Controller just updates the Model with the user's request (i.e. the operation the user wish to do on the data, such as 'give me a list', 'save this item' etc.) and then leave it for a View to query the Model and be able present the same data in many different ways, regardless the controller that updated the model.
Masterpiece! Brilliant! Thank you very much!
Thank you so much, now I understand this
Fantastic Information Guy.... Love it :)
You're legend. Thanks for this!
Wonderful Dear.Thank you so much Sir
Very helpful! Thank you!
Wordpress is a linux thing.
Just gonna pretend it didn't happen, the video is actually really good :)
Nice explanation!
I really like how you explained MVC, it is really clear to me now, thank you so much. I checked to see if you have an explanation of MVVM, but it seems you don't. Any plans on creating one or is there a video you recommend?
Awesome explanation! Thank you!!!
Amazing tutorial. Thank you a lot.
Go to 19:30 for a quick 2 minute summary
Awesome explanation! you put it down in a so simple way! Thank you!
Thanks Very much but please make a video only explaining route processing process , i still can't get my head around it properly.
Well done! Thanks for sharing.
Thanks Jacurtis. Video was great in explaining all about MVC and now I real understand it. Had gone to Treehouse.com and Lynda.com but did not understand it at all. Will Keep watching all videos on Laravel.
Isn't submitting a form an example of the view talking to the controller, not just listening?
So basically.. MVC is just the structure of having a client, server, and DB..
Can I say view as frontend, model as backend and control as middleware
I'm enjoying this tutorial - part-way through so far. Cudos - it's good. (Helpful). Made me chuckle though when presenter said something like "WordPress is Apache / Linux". I've only ever ran it, personally, on Windows, and mostly on IIS. (I like linux too - and embedded systems ... but I do like Windows. And PHP as well ... and just to pre-empt some of the haters, also assembly, C, C++, C# and so on [I have an electronics/systems background] ... I think there often seems an incredible amount of prejudice around, lack of imagination, ignorance and so on - it's almost funny).
Amazing - thank you so much!!
Hm came here to learn about MVC as an iOS developer and been watching it for 10 minutes. Had to drop watching just because it seemed to have a lot of filler information..
Really well described. Enjoyed the tutorial and learnt something in the process. Great job!