Repeating my other reply verbatim yet again as you keep copying and pasting the same exact comment:

First, to be clear, this isn’t so much “press” as a blog entry. Second, there are only so many mentions of “rust cultists” and “my rust” I can read in a blog before losing interest.

Repeating my other reply verbatim as you just did the same:

First, to be clear, this isn’t so much “press” as a blog entry. Second, there are only so many mentions of “rust cultists” and “my rust” I can read in a blog before losing interest.

First, to be clear, this isn’t so much “press” as a blog entry. Second, there are only so many mentions of “rust cultists” and “my rust” I can read in a blog before losing interest.

I disagree that the web site is fast; it took at least 10 seconds before the video would start playing.

I feel like the modern name for it would be just “Script”.

Unless the C++ code was doing something wrong there’s literally no way you can write pure Python that’s 10x faster than it. Something else is going on there.

Completely agreed, but it can be surprising just how often C++ really is written that inefficiently; I have had multiple successes in my career of rewriting C++ code in Python and making it faster in the process, but never because Python is inherently faster than C++.

Have you really not heard of it? It is a new architecture that is a bit better than x64_64.

Sure, but if you are not regularly expressing code that has the potential of summoning elder gods that will swallow your soul into a dimension of ceaseless screaming then are you really living?

I don’t always use regular expressions, but when I do, I use it to parse XML,

Something that definitely separates me from some of my less experienced coworkers is that, when I sit down and start to implement a plan I came up with in my head, if it turns out that things start exploding in complexity then I reevaluate my plan and see if I can find a simpler approach. By contrast, my less experienced coworkers buckle down and do whatever it takes to follow through on their plan, as if it has now become a test of their programming skills. This makes life not only more difficult for them but also for everyone who has to read their code later because their code is so hard to follow.

I try to push back against this when I can, but I do not have the time and energy to be constantly fighting against this tendency so I have to pick my battles. Part of the problem is that often when the code comes to me in a merge request it is essentially too late because it would have to be essentially completely rewritten with a different design in order to make it simpler. Worse, the “less experienced” coworker is often someone who is both about a decade older than me and has also been on the project longer than me, so even though I technically at this point have seniority over them in the hierarchy I find it really awkward to actually exercise this power. In practice what has happened is that they have been confined to working on a corner of the project where they can still do a lot of good without others having to understand the code that they produce. It helps that, as critical as I am being of this coworker, they are a huge believer in testing, so I am actually very confident that the code they are producing has the correct behavior, even when I cannot follow the details of how it works that well.