It is great Magnitus & dtgreene that you have unwrapped all the entanglement Sw development entails.
You have moved from the oversimplified "programmer vs CPU time trade-off" to grab the bull by the horns.

I am afraid I will not reply every piece of your posts: It would require a significant time and typing effort that this holidays do not allow me. Besides, is not the place to have this deep discussion.
Instead, I'll try to write a short post then.

After finally bringing the meat to the table, I declare Magnitus the winner of the tiger raffle (In case your/my posts were a winner/loser competition or it alleviates somehow my 2 provoking posts).
I am afraid I won't tell you my expertise areas. Instead for a change, I propose we brag how many times we have been the villain/,,loser,, pushing back projects by the topic on the table.
Don't you think would be more purposeful? :)

Anyway, in pursue of shortening, I quote key phrases from both of you:

Magnitus: "If you never had to deal with deadlines. I envy you. You must be very privileged (but also kind of out of touch with the reality most developers face).
I won't pretend that the software industry doesn't suffer from a wild west problem"

Magnitus: "A well designed piece of software is full of tradeoffs leading to a well designed solution for the problem the software is trying to solve.
Universally good software, irrespective of problem domains, doesn't exist. Its always contextual."

Magnitus: "bloated complexity ... I bailed out of that some years ago"

dtgreene: "the code is running on a system not owned by the developers"

dtgreene: "aren't suitable in embedded situations. In this case, CPU power and RAM are not as cheap or abundant as they are on more conventional machines"

dtgreene: "launching shuttles into space [considerations]"

Magnitus: "Context matters"

Magnitus: "When taking advantage of fine-grained lower level optimization, it is assumed to be performed by someone who is proefficient and knows how to optimize thing"

Magnitus: "conservative with technology at heart. I don't use a tool until I've understood it well (I don't need to read all the code for dependencies that are very large, though I do expect at the very least to get a lot of wisdom from people with a great deal of experience in the tool, usually indirectly via a book). It does create a hard limit on what I can use which I find healthy. It forces you to prioritize on what truly matters and it causes fewer failures in production"

dtgreene: "test out snippets of code to see how they actually work while you are learning"

Magnitus & dtgreene: [Several specific cases]

I agree with both of you. Magnitus, if you like, you could compare this quotes to my 1st post keywords list. Any way or other, we are talking about the same: A long list of things to consider.

Then, if we agree: Why both of you used the infamous oversimplified "programmer vs CPU time trade-off"? (Rhetorical question)

I invite both to more frequently be the villain/,,loser,, raising the voice against unrealistic deadlines, bore to death the decision makers with all the intricacies Sw Eng entails (Go find and use puppetry and 5 years old explanations if needed), push back the deadlines and the scope creep with the ultimate goal to deliver quality Software. Let's get some scars to be proud of and let's create a safety_net/union (open to proposals) to give support to each other into a business crushing the human talent causing us stress, anxiety, nonsense, and a lot of sh*tware. Again, someone will need to clean up all the mess and very probably will be ourselves.
Please, we must defend the respect Sw Eng deserves.

I hope someday to meet both in person to have this fascinating discussion.
There, I will not need provoking/profanity tactics. I promise.
Enjoy the holidays and read you both later.

I would really prefer for this not to be treated as a competition, to be honest.

You should not waste time on tag+ posts in this thread, they are clearly trying to pass for someone with software development skills they do not have. Not even at a basic level.

Though the runtime verification you refer to entail a performance penalty, its realistically a worthy tradeoff in all, but the most stringent performance use-cases.

Honestly, at this point, I find I lack recent experience with a low-level language: I was a wizard in C++ roughly a decade ago, but I haven't kept up with the many advances of the language since and would have some rampup to do to update my knowledge there so its a good opportunity to examine the landscape for alternatives (since I'll invest energy into it either way) and Rust does seem more modern (in a good way).

I haven't really needed a low level language in my job for some time (I'm not working with embedded systems, drivers, kernel-level code or code that has demanding real-time response requirements), but I'll most likely dabble in game development again on the side and Rust might fill that need (I looked and Rust has some libraries for games).

I even have a book lined up that I'll hopefully be able to read sometimes next year.

In the simple case, when you just want to loop through an array, you can just do something like "for x in array", and the compiler will omit the run-time checks, as it is safe to do so.

In more complex cases, the run-time checking is generally a good thing, and if it is actually causing a performance issue (like failing to meat a hard real time constraint), there's still the "escape hatch" of unsafe code. (Just be careful with "unsafe".)

I have heard a lot about Python in the past. Basically, I never use this program before. But I have great interested to build a new website using Python. For me WordPress looks more easier.

Apples and oranges here.

Python is not a web host or a web hosting service.

Edit: Actually, "apples and oranges" isn't even a good analogy here, as they're both fruits, while WordPress and Python aren't the same type of thing.

I don't know, but what I do know is that Python is not a web hosting service.

Websites can be built using Python, a versatile and powerful programming language, through various frameworks and libraries specifically designed for web development. One of the most popular frameworks is Django, a high-level Python web framework that encourages rapid development and clean, pragmatic design. Django provides a robust and efficient way to build web applications, offering features like an ORM (Object-Relational Mapping) system, authentication mechanisms, and built-in admin interfaces. With Django, developers can create secure, database-driven websites efficiently.

Another popular choice is Flask, a lightweight and flexible micro-framework for Python. Flask is known for its simplicity and ease of use, making it an excellent option for beginners and small to medium-sized projects. You can also share your Python programming tips.

A bot bumping a bot :P

Enough is enough! I've had it with these motherfucking snakes on this motherfucking website!