I use Python because it has a HUGE library of math, data plotting and other functions. Many of these libraries are in C/C++ or Fortran, so run fast, and have a long legacy or are actively maintained, so are reliable. I also use Python for machine learning where most of the work is data or method exploration and the immediate running of code cells (in Jupyter, for instance) allows fast iteration of the code. On the other hand, I wouldn't use Python for a time-critical real-time system, although I have used it to interface with Arduino's and data acquisition boards. However, Python is not that much slower than compiled languages unless the run-time is very long. Even then, if the code is solving big matrices then most of the time is in Fortran anyway. From my understanding, the reduction in speed in Python is mainly to do with it not being a typed language: the interpreter has to figure out the data type on the fly. I'm not sure why this has to be since best coding practice is to use type-hints, which can be statically checked, but are ignored by the interpreter. I don't see why type-hints, if present, can't be used by the interpreter to enforce typing. As to the comments about using white-space for formatting, I was already indenting to make the code readable so ; and {} are redundant to me and now seem like clutter whenever I work in C/C++/Java/PHP.

it's been eight fourteen 31 years since Win 10 7,3.1 [insert:] and it never got any better,

Playing with the interface format and other cosmetic features is annoying, but the core issue is MS needs to fix the massive number of security problems that are buried in the code. It must be nightmare code because every time something is added/modified, more bugs seem to be exposed. The code must be just patches on patches rather than a cohesive architecture.

My background is engineering. (PhD - Mechanical). Started coding in the 1970's. Mostly writing analysis and modelling code, but some machine interface and control stuff as well. I can't say I have a lot of sympathy for you. There are lots of development systems out there. C# is just the latest of a long list of system you will encounter in your career. Some are application specific, some are legacy. C#, or any .NET system, is a minority in the programming world. If you're aspiring to be a professional programmer, then part of what you will be paid for is deal with odd-ball, undocumented and buggy systems - there are lots of them - that were probably written with the best development environments of the time. Let's hope that you're C# programs stand the test of time as well. Lots of code dies an instant death as soon as a user sees it. About having to do hacks - at some point the limit of any system will be pushed. If you look at some of the C# articles on this site you'll see lots of hacks that the authors though were good solutions but ended up having some unintended consequences (a euphemism for bugs), as pointed out in the replies. Being a programmer is not about the languages you know. It's about organizing the project correctly and expressing it in the clearest (meaning most reliable) code you can wrangle up. As a NAV programmer, trying to accurately interpret the needs of accountants and managers ("the clients") without going over-budget is good experience. Good luck on your career, whichever way you go.