Nice listing but make sure that you give credit where credit is due.
1) Testibility - Given that you actually use WinForms correctly, you can get the same amount of code coverage.
2) URL Routing is avaliable for WinForms. I use it myself.
3) Built in jQuery support is in WinForms as well.
4) Mobility support - they both use dection schemas for mobility - they are just different.
MVC is great and I support its use but just be careful not to assume everything is black-n-white. There are cases in which use of one or the other can be argued and there is alot of overlap scenarios. I would argue knowing both approaches, their pros and cons, and choosing accordingly.
1) Testibility - Given that you actually use WinForms correctly, you can get the same amount of code coverage.
2) URL Routing is avaliable for WinForms. I use it myself.
3) Built in jQuery support is in WinForms as well.
4) Mobility support - they both use dection schemas for mobility - they are just different.
MVC is great and I support its use but just be careful not to assume everything is black-n-white. There are cases in which use of one or the other can be argued and there is alot of overlap scenarios. I would argue knowing both approaches, their pros and cons, and choosing accordingly.