MVVM with or without it?

Question

WPF

I'm learning WPF and so far so good, but I often come across MVVM, they write about it.
While MVVM itself did not study, only looked, logic understood more opinion. Although I do have questions.
My question is when to use MVVM? I understand complex and large projects, but if I have a project with only 100-200 lines, it's not very complicated. Collection of information from 1 site and that's it.

Answer 1

C MVVM is easier in both large and small projects

Answer 2

Always use. Simple - always. WPF is designed from the ground up for binding and normal architecture.
Just because you can do it the same way as in WinForms doesn't mean it's worth doing.
Just remember as a mantra, created a project - add a reference to the MVVM framework, and work. Any framework, for example MVVMLight. Or Prism. Or your bike (I do this), any.

Answer 3

You don't need MVVM if you don't plan to develop the project further, like supporting N sites on M different platforms or something like that. If expansion is planned, MVVM will come in handy, if only because it will be much easier to reuse the code.

Answer 4

in general, patterns were invented, not only to simplify the code / logic, etc.,
but to make it easier to understand,
for example, other programmers started a conversation, and said they say, for example, I use a factory in this solution, etc.
the programmer already roughly understands what you mean
, etc.
to me it seems
better from the very beginning to accustom yourself to such code by patterns
well, you need to google antipatterns

Answer 5

Take MVVM + Caliburn Micro. Mvvm Light is basically just a set of helpers, although there are also broadcast messages. Prism is too much to start with, maybe too hard.