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

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.

Sometimes this can help, but lately I’ve been running into the opposite problem where people have been following this advice to such a degree that one cannot ever figure out what is going on without having to constantly jump around to find the actual code involved in doing something.

Because it looks like that functionality uses special compiler functionality only available on GCC and clang?

“This isn’t us encouraging you to gamble-it is us asking you to think about how bad you would feel years from now if you learned that you could have made a ton of money if you had only placed a bet right now! It’s completely different!”

I can understand this view for early backers (I’m one of them) but what about people who decided to drop money on the game in the last 2 or even 5 years? Were they also scammed despite hundreds of articles about delays, issues and thousands of people yelling about a scam every time SC is mentioned?

Maybe, maybe not, but is entirely possible to be scammed while also being in a position where you should have known better; the two are not mutually incompatible.

The root of the problem is that you think of momentum as being defined to be the product of something’s mass and its velocity, but this is actually only an approximation that just so happens to work extremely well at our everyday scales; the actual definition of momentum is the spatial frequency of the wave function (which is like a special kind of distribution). Thus, because photons can have a spatial frequency, it follows simply that they therefore can have momentum.

Something else that likely contributes to your confusion is that you probably think that where something is and how fast it is going are two completely independent things, but again this is actually only an approximation; in actuality there is only one thing, the wave function, which is essentially overloaded to contain information both about position and momentum. Because you cannot pack two independent pieces of information into a single degree of freedom, it is not possible for position and momentum to be perfectly well defined at the same time, which is where the Heisenberg uncertainty principle comes from.

I appreciate this sentiment a great deal in general, but sometimes it is difficult to uphold when I have to regularly deal with “time vampires” who not only require that I explain the same thing to them over and over again beyond reason but who also show no willingness or ability to actually learn the thing that I am explaining to them; at some point I just run out of patience and start ignoring them to the extent that I am able.

What I like to tell people is that I am as good a programmer as I am for the simple reason that I began when I was about 8, which gave me a very early start on making all of the mistakes one can possibly make when learning how to code.

(It has been funny watching some of my coworkers learn a new coding technique and finding it to be so cool that they apply it everywhere regardless of whether it fits or not while I think to myself, “Ah, I remember when I went through that phase as a teenager!”)

Quoth the article:

As spotted by iMore, this indemnification stems from how Epic Games breached the developer agreement it had with Apple when it tried offering its own alternative payment system in August 2020.

In short: Epic Games pissed off the court when it consciously chose to violate the terms of its its contract with Apple before filing the lawsuit, rather than first filing the lawsuit and waiting for it to conclude. The court is taking the unusual step of billing Epic Games for Apple’s legal expenses precisely to disincentivize this kind of behavior in the future.

And if it doesn’t have objects, then it has no class!

That is conceptually how dynamic programming works, but in practice the way you build the cache is from the bottom up rather than from the top down. It’s a bit like how you can implement computation of the Fibonacci sequence in a top-down manner using a recursive function with caching, but it is a lot more efficient to instead build it in a bottom-up manner.

Sure, but shouldn’t you want your generated markup to adhere to the complete standards so that you know it will be interpreted correctly, rather than hoping that the browser will make the correct guess about what you really meant?

I completely agree with that assessment, but what is weird to me is that most people use frameworks so they don’t actually touch any of the markup themselves.

That approach makes a lot of sense for amateur web sites, but less sense for professional web sites.

Wait… I just noticed this:

[XHTML] never took off on the web, in part because in a website context so much HTML is generated by templates and libraries that it’s all too easy to introduce a syntax error somewhere along the line; and unlike HTML, where a syntax error would still render something, the tiniest syntax error in XHTML means the whole thing gets thrown out by the browser and you get the Yellow Screen of Death.

This confuses me; don’t you want to make sure you are always generating a syntactically valid document, rather than hoping that the browser will make something suitable up to work around your mistake?