I think it's well suited if you have data available and you want to create customized solutions for different types of users. Mendix is very good at doing that. It allows you to do it very easily. So those are good use cases.
If you need to build anything from a quick-and-dirty GUI utility to a full-fledged desktop application, .NET is the way to go. It doesn't require extensive knowledge of the languages as Visual Studio is extremely helpful in its autocomplete, refactoring, and prompts, and lets you build out your solution easily without worrying about the details of [the] setup and boilerplate.
.NET is heavily Microsoft Windows oriented, and while .NET core tried to resolve that with MacOS and Linux support, .NET Core is still waiting for wider adoption.
While free for small projects, additional features for big projects can be a little expensive.
Can be resource-heavy upon deployment. We continuously have our more senior staff optimize the code of our junior developers for performance. Other languages are a little bit more forgiving in comparison.
Drawing from my hands-on experience with Mendix, I can confidently state that the platform aptly fulfills our needs for web application development. Mendix stands out by providing a marketplace replete with pre-built templates and widgets. This feature empowers users to leverage readily available components, hastening the development process and contributing to an enhanced overall usability of the platform.
.NET frameworks are fantastic overall. There are no limitations to what you can accomplish with it. The most important part is that you'll have access to developer community support and that .NET is always being improved every month. Be it in web applications, back-end servers, or integrations, .NET enables developers to do it all.
I think their support system is really professional. They answer question quickly and accurately. They have a ticket system that allows to track the current status of a request. The only point for imporvement is a way for me to postpone an answer. Tickets get closed automatically after some time. I feel that the user should have the option to change to an on hold status, allowing for more time to respond to a ticket.
As Microsoft Gold Partners, we do have access to a lot of additional information and support from Microsoft. Still, the availability of "open and free" documentation, community, and enthusiasts of the platform is vast. Added to that, the quality of resources provided for all the Microsoft ecosystem is very impressive.
Because most of our apps work closely with our main system (ERP) and other tools, we went with Mendix. It's good at easily connecting with lots of different systems, which is exactly what we need. Another thing we like about it is that it can handle growth well, and its pricing is straightforward and easy to understand.
If it was up to me, I'd rather use something like Node.js hands down. Things are simpler, there is no gigantic convoluted class hierarchy to learn like there is with .NET. Also Node is really fast and lightweight. I find .NET these days to be a totally solid product and it certainly has its place - but it seems a bit dated and boring to me now.
Without Mendix we could not have been where we are now. A development platform as Mendix can make the difference in a constantly changing environment.
Upgrading to newer versions of Mendix is a breeze when you stay within a main version (e.g. M6.x to Mx6.x+1) and even between versions (Mx5 to Mx6) most of the time it is no problem at all and there are only minor changes needed to upgrade.
Learning Mendix is simple. Just start playing with it and see for yourself how easy it is and feel the joy of developing applications.
We are slowly switching from a dying programming language to .NET because it was too expensive to hire developers for the old programming language. There are way more .NET developers around and an amazing community which has allowed us to keep our costs low.
Our development time has been greatly reduced because now we're not developing applications for each OS platform. We do it once and deploy accordingly.
.NET Core has been a big mindshift in terms of how to program. The learning curve has been quite high for existing .NET developers.
