Exactly. Less code means easier maintenance.
Exactly. And if I need an experienced coder for C++ and a slightly less experienced for C#, it means that C# is cheaper to use.Yes! For inexperienced devs, but not for experienced ones!
Same thing here. Yes, it's doable. With a considerably amount of experience, time and a third party library that probably comes with costs of it's own, licensing, knowledge needed or whatever else. If you have a customer demand the the first row of the list be a special kind of green if it's wednesday, then that's a no-brainer in C#. You will need a third party library or a ton of custom code in C++.It certainly is harder to do GUI in C++, but with all those libraries out there, it's DO-able. One just needs to know how.
Both is totally irrelevant to my field of work. I'm neither short on disc space nor will anyone outside of the company get access to my executable. May differ for you. Obviously different environments need different tools.Plus it creates bigger executables and it's easier to reverse engineer.
So do I. But that's a crappy program and I can guarantee that the same program will take maybe 4.8s in pure Assembly. Bad programming is bad programming. .NET programs, like Java programs, only take longer to load because they are compiled at runtime. Startup time to me (and my customers) is irrelevant, remember I'm not talking two buttons and a textbox here, the programs are started once and then used for the remainder of the day. Even client validation against the database and database login will take longer than startup. If the application does a lot of stuff, time for startup becomes irrelevant. Again, this may differ for you. Different environments, different tools, yada yada yada.But there's also the speed question. If something takes 5s to do, just like clicking a button, then I'd find that program very bloated and unfun to use.
While running, no GUI in any language will take any amount of time that is noticable to the user. If it does, it's either real processing that has nothing to do with the GUI, or it's simply ........ty programming.
I love C++ and it's power just like I love a car that has some more raw power than I'd ever need. But if it comes to getting a job done fast and efficient, I'd rather take the tool that fits best. Which right now for me is C#.