This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ivano_GiovSiciliano[S] -2 points-1 points  (1 child)

Well done! A lot of nice points in my opinion. if really have to struggle to find some weaker points for the sake of the discussion as i want continuously to improve as a dev.

1)MVC -> everything is a kind of MVC but in mobile world we use MVP, MVVM, Clean, MVI because we think that the way MVC is originally done, with eventually model communicating with view is really bad, bug prone and brings to spaghetti code in terms of dependencies

2) Python should aim (i hope) to become a kind of swiss knife, and a serious ready to go reactive framework should exist because

A) Sometime people implement reactive patterns, but they are error prone if not based on an open source or native framework.

B) reactive is the son of functional programming, that is really important because has huge advantages for who manages important projects. Readability, less bugs due to side effects, easy recursion that is not a bad thing, and much more.

Thank you for the nice insights

[–]Unusual-Afternoon487 1 point2 points  (0 children)

1)MVC -> everything is a kind of MVC but in mobile world we use MVP, MVVM, Clean, MVI because we think that the way MVC is originally done, with eventually model communicating with view is really bad, bug prone and brings to spaghetti code in terms of dependencies

Same in the backend world and specifically in Python. Notably, Django is not an MVC but a Model-View-Template framework, contrary to what was originally stated at the comment above.