I told someone I was building a school project with win forms and they asked why if it's outdated. Nice to hear that I'm not actually wasting my time with it. 😅
It's surprisingly common in manufacturing, government, and other things that have been around for decades. Something a lot of devs don't realize (because they love technology) is that business users often don't care about the stack or frameworks, all they care about is the app does its job.
Just subscribed to a content creator this week who posted a video with the thumbnail "I quit Cobol". She'd been working steady for years for multiple companies maintaining their old Cobol infrastructure, quit to do content creation full time. Plenty of money and jobs in legacy code. Side note as someone who used to work as a mechanic, I hated it when our vendors would come out with their "New and Improved!" interfaces. They were forever this modern, bubbly, straight up trash interface when it comes to getting actual work done. Give me the old, utilitarian interface that shows what I need to see at a high density, where I don't need to scroll and search through a "pretty" interface to get to the information I need. One service, I stayed on the legacy interface past the point where it was no longer supported and semi broken, to the point where the page would literally give me an error every time I tried to even access the page and no amount of tweaking I did could make it load because I hated the new interface so much. Know your audience or client, not everyone needs or wants a modern interface.
Absolutely. XAML can do some really sleek things, but the learning curve is way higher. I'd probably use Winforms as well if I was teaching desktop fundamentals.
I told someone I was building a school project with win forms and they asked why if it's outdated. Nice to hear that I'm not actually wasting my time with it. 😅
It's surprisingly common in manufacturing, government, and other things that have been around for decades.
Something a lot of devs don't realize (because they love technology) is that business users often don't care about the stack or frameworks, all they care about is the app does its job.
Just subscribed to a content creator this week who posted a video with the thumbnail "I quit Cobol". She'd been working steady for years for multiple companies maintaining their old Cobol infrastructure, quit to do content creation full time. Plenty of money and jobs in legacy code.
Side note as someone who used to work as a mechanic, I hated it when our vendors would come out with their "New and Improved!" interfaces. They were forever this modern, bubbly, straight up trash interface when it comes to getting actual work done. Give me the old, utilitarian interface that shows what I need to see at a high density, where I don't need to scroll and search through a "pretty" interface to get to the information I need. One service, I stayed on the legacy interface past the point where it was no longer supported and semi broken, to the point where the page would literally give me an error every time I tried to even access the page and no amount of tweaking I did could make it load because I hated the new interface so much. Know your audience or client, not everyone needs or wants a modern interface.
I met an early 30s year old contractor at a wedding a few years ago who was billing $150/hr for COBOL work.
Eric is the Best!
As always, ty for your support!
My c# bootcamp instructor insisted on using winforms instead of wpf due to simplicity and stability they provide
Absolutely. XAML can do some really sleek things, but the learning curve is way higher. I'd probably use Winforms as well if I was teaching desktop fundamentals.