Me: How does this new framework help our stack and/or process?

DevIdiot: it has MVC

Me: 😆🔫

When is it appropriate to switch to an MVC framework? Serious question. I'm tired of feeling so out of touch using WebForms, but it's hard to come up with a business case for switching. Is there one?

@shittywebdev I once read something on the topic. It basically came down to "if it's already written in webforms, then there is nothing to gain from changing. If it is a completely new project consider using MVC"

I get that. Why use MVC on a new project? I've used both and the only advantage I saw with MVC was less overhead from not having ViewState. Speed/performance improvements isn't a huge concern for my clients. Maybe I'm just not in a big enough company to see the advantages.

@shittywebdev honestly, I think it's just a buzzword thing. The lack of overhead is important to some people. I personally thought I was quicker to develop on it, but that was just me. The article I read said "consider" it. If you don't have a business case, you don't have a business case. I'm indifferent to either tbh.