15
fyroc
8y

Knowing and correctly implementing MVC should be a requirement for all developers.

Comments
  • 5
    What about people who create APIs solely?
    Or console program creators?
    Oh and should WinForms/WPF devs also have that requirement?
  • 3
    Why just MVC? There are many patterns, some better for certain languages or solutions than others.
  • 6
    @burtybob I think OP just meant it's a skill every developer should have, not that it necessarily should be used in every project
  • 0
    Yes, I'm saying it's a skill every developer should know. Yes there are Devs that may never need it with their language but by knowing it, it can allow you to organize your codes and methods.

    There are other ways other than MVC too.. MVC is just most common and in my opinion the simplest.
  • 0
    @burtybob I don't think devs should shoehorn themselves into such a narrow vein. Most good devs I know are able to program a variety of applications, and I think any good dev should be able to do this.
  • 0
    MVC might be the most commonly used frameworks but wanting every developer to know it is a bad idea.someof us know mvc and hate it (with a passion ), we have built or used custom frameworks and run benchmarks against mvc and proved several times that it's not always the best solution.
  • 2
    @bondman Um, I'm not sure you can benchmark a design pattern. You can certainly benchmark an implementation of one, but your figures won't actually measure the effectiveness of the pattern itself, just the platform it's been built on.
  • 0
    @samk what makes you says so? two similar implementations one with framework and one without can be benchmarked. It really isn't rocket science unless we are talking about different things here
  • 1
    @bondman I think we are. MVC is a design pattern, a way of structuring code so that it conforms to certain rules. It's language and platform agnostic. I misunderstood your original comment about disliking MVC and having benchmarks suggesting it wasn't always optimal.

    I was trying to make the point that you can't benchmark the actual design pattern - the theory/concept of it - but you can certainly benchmark ways of implementing it on a given platform or environment (which seems to be what you were meaning).
Add Comment