4 reasons to drop MVVM
-
The MVVM design pattern has been around for quite a while now. It has a lot of strengths when done correctly. But, I believe the time has come to recognize that MVVM has a lot of shortcomings that point to its demise.
Already? I only just learned what the second 'V' was for. Now I'll never learn about that last 'M'
-
The MVVM design pattern has been around for quite a while now. It has a lot of strengths when done correctly. But, I believe the time has come to recognize that MVVM has a lot of shortcomings that point to its demise.
Already? I only just learned what the second 'V' was for. Now I'll never learn about that last 'M'
Actually the performance bottleneck he speaks of with Angular is quickly becoming moot as the whole loop thing is being phased out. And not every framework relies on that. Granted, it does increase processing time, but using an MV* framework isn't nearly as bad as this guy makes it out to be. To me it sounds like he's ill-experienced.
Jeremy Falcon
-
The MVVM design pattern has been around for quite a while now. It has a lot of strengths when done correctly. But, I believe the time has come to recognize that MVVM has a lot of shortcomings that point to its demise.
Already? I only just learned what the second 'V' was for. Now I'll never learn about that last 'M'
From the article: "It sounds great. And when it works it is. But that’s the main problem, it hardly ever works well." "You try it on some small application and you get excited. Like a gateway drug, it lures you in. And when you finally go to implement it on some larger application, you find out that it really doesn’t scale all that well." This describes a lot of things even outside design patterns. Many things which work great on a one-off test with highly dedicated people end up being terrible when applied generally. A big reason is that with the small experiment, everything can be controlled. Things quickly unravel beyond that. (Confirmation bias also plays a huge part--you want it to work and dismiss or ignore the problems.)
-
The MVVM design pattern has been around for quite a while now. It has a lot of strengths when done correctly. But, I believe the time has come to recognize that MVVM has a lot of shortcomings that point to its demise.
Already? I only just learned what the second 'V' was for. Now I'll never learn about that last 'M'
What he's really talking about is Angular, and how it handles data binding, and that's a problem for Angular not a problem with the underlying MVVM design pattern. I've been using Kendo UI from Telerik which also uses the MVVM pattern without any problems. He's found certain issues with how Angular implements MVVM and conflated these to the wider design pattern itself.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
The MVVM design pattern has been around for quite a while now. It has a lot of strengths when done correctly. But, I believe the time has come to recognize that MVVM has a lot of shortcomings that point to its demise.
Already? I only just learned what the second 'V' was for. Now I'll never learn about that last 'M'
-
The MVVM design pattern has been around for quite a while now. It has a lot of strengths when done correctly. But, I believe the time has come to recognize that MVVM has a lot of shortcomings that point to its demise.
Already? I only just learned what the second 'V' was for. Now I'll never learn about that last 'M'
That guy takes issues with Angular and makes it seem like the pattern is to blame. I have news for him. It's not. All implementations have issues, but the pattern is not the problem. He is an idiot that should not be programming.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
The MVVM design pattern has been around for quite a while now. It has a lot of strengths when done correctly. But, I believe the time has come to recognize that MVVM has a lot of shortcomings that point to its demise.
Already? I only just learned what the second 'V' was for. Now I'll never learn about that last 'M'
Well., mostly, because MVVM looks like a spring or Slinky...
-
May be the author didn't reflect on that thought.
-
The MVVM design pattern has been around for quite a while now. It has a lot of strengths when done correctly. But, I believe the time has come to recognize that MVVM has a lot of shortcomings that point to its demise.
Already? I only just learned what the second 'V' was for. Now I'll never learn about that last 'M'
I opened that page, and saw that he's got a certificate from "scrum alliance csm" or something like that. I had to close that page immediately as there's little chance of him knowing anything meaningful about development.
-
The MVVM design pattern has been around for quite a while now. It has a lot of strengths when done correctly. But, I believe the time has come to recognize that MVVM has a lot of shortcomings that point to its demise.
Already? I only just learned what the second 'V' was for. Now I'll never learn about that last 'M'
As the very first line of history is incorrect, I see not much point in progressing further... "MVVM was originally created by John Gossman to support the XAML syntax used to create Windows™ desktop applications and Silver Light applications." Should read "MVVM is an adaption of the Model View Presenter pattern, originally documented by Martin Fowler, to the XAML architecture of WPF and Silverlight applications."
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
What he's really talking about is Angular, and how it handles data binding, and that's a problem for Angular not a problem with the underlying MVVM design pattern. I've been using Kendo UI from Telerik which also uses the MVVM pattern without any problems. He's found certain issues with how Angular implements MVVM and conflated these to the wider design pattern itself.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
My thoughts exactly. Speaking as someone who uses MVVM for desktop applications, I like it a lot. That's not for what Mr. Bush would write off as "religious reasons" but simply because it's the best pattern out there right now. Five or ten years from now, I'm sure we'll all be using something different - that's the nature of the game - but I'm certainly not going to abandon it just because someone's having a few issues with a framework. Do we know if those issues lie with Angular or just his implementation of it, anyway? Does he just have too many watchers going on at once? I can't really comment as I don't use Angular but if it is such an issue, why is this the first time that I've heard anyone say that Angular doesn't work with MVVM? It's certainly supposed to and many people seem to use it that way. All in all, a very poorly considered piece and I hereby suggest that we drop HTML and shut down the internet just in case I ever have to read a similar one.