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.

Yes, and that is my point: unless you wearing a seat belt somehow made the accident more likely to happen, it really doesn’t seem like manslaughter applies here.

According to this page, you could attempt to argue “lack of causation” if there was no connection between you not wearing a seat belt and your passenger getting killed.

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”.

My taste buds disagree that this is “unfortunate”.

Censorship sucks and I can’t believe we let an entire country get away with it and still did business with them the whole time.

It is not clear to me that the country would be less censored now and the people there better off if we had refused to do business with them.

(Just to be clear, I am not saying that we handled China as well as we could have over the last few decades, but hindsight is 20-20.)

I think that sometimes what happens to people is that they build the life that they implicitly believe they are “supposed” to be living because that is what they see everyone else around them doing, rather than based on an honest self-assessment of whether this really is the what will make them happy. When they realize that this life is not actually making them very unhappy, they look for outside factors to blame because they did everything that they were “supposed” to be doing so it could not have been their own misinformed choices that led them to this point.

And in fairness, no one chooses where they are born and the cultural conditioning that we receive, so this is not entirely their fault. It is really a societal problem that we do not encourage enough people to engage in true self-introspection to figure out for themselves what is important to them and what they want to get out of life so that they make these kinds of decisions with great deliberation and personal self-insight rather than taking the default option.

A Linuxponential curve!

Choosing to have a child later on generally has fewer negative consequences than unchoosing a child you have already had.

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++.

Genuine question: does anyone actually use Vala for anything? I think that the idea of a language whose OOP system is native GObjects is a nifty one, but I have seen no evidence that it has caught on in any significant way.

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,

I find the author’s writing style immature, sensationalist, and tiresome, but they raise a number of what appear to be solid points, some of which are highlighted above.

I tried reading the article and gave up because life is too short for me to read a tiresome article making points that aren’t even particularly that new.

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.

So does that make the new name the undead name, and therefore like a zombie name?