Recur has zero inconvenience. It's four letters, it verifies that you are in a tail position, and it's portable if you take code to a new function or rename a function. What's not to love?

In what sense?

We've removed sex from normal life as far as possible. Films can be full of violence but any hint of titillation is verboten now. Any reference to sex in normal walks of life is seen as harassment, chauvinistic or pandering to the male gaze. Our culture is influenced by global social and religious conservatism in the quest to sell media to as many markets as possible. Our own new conservatism (the so-called left wing) is just as bad.

On top of that we have the culmination of a few decades of obsessive education about STDs and sex as a dangerous act that can ruin lives. A far cry from 'The Joy of Sex' as a cultural phenomenon.

We're letting prudes and those with deep psychological issues around sex call the shots. Millennials and Gen Z may be a lost cause, but let's hope that Gen A can rewrite the rules.

The point is that this kind of control will drastically reduce under 18s consuming content that they shouldn't. We don't need the all of society's controls to be flawless.

The experience has gotten worse and worse now for a decade. The core team have continued to take things in a worse direction (supported by a small group of fanboys) and most newcomers are now completely baffled by the tooling.

You can have a directory per environment and a directory of shared resources that are used by all environments.

It seems like workspaces add a new construct to be learned and another thing to add to all commands without much benefit. Could we just stick with the simple way of doing this?

If a lecturer at university sets a task for 100 students (say, write an essay about the factors that led to the first world war), there will be clear and glaring similarities between the way that points are made and explained if many students use chatgpt. Yes a student might rewrite or paraphrase chatgpt, but low effort copy and paste is going to be very obvious because chatgpt's model cannot produce an entirely unique approach to the task every time it is asked.

I know there are weights and parameters that can be adjusted, so there is some variety available, but I think better to think of the LLM as an additional (all-knowing) person you can consult. If everyone consults that same person for an answer to that assignment it's trivial to detect.

Very good point, but please stop using this phrase.

The cartridge itself was fascinating because it had two extra controller ports on it! You had for player gaming by plugging two controllers into the console and two controllers into the cartridge that was protruding from the top of the console. The cartridge was a little taller than usual to accommodate the extra hardware.

For almost all intents and purposes, if you are asked to create a YAML file then you can choose JSON as your syntax instead, because your file will be understood by the YAML parser. The benefit being that JSON has far fewer quirks and edge cases.

It's comical that when people get confused with YAML (which is often) they convert their YAML snippet to JSON to see what's really going on. YAML is horrible for humans to write. Let's just use JSON, the sane syntax, instead. A few extra parents and quotes is really no big deal, and it's far easier to read unambiguously.

The advice "don't use virtual threads for that, it will be inefficient" really does need some evidence.

Mildly infuriating though that people may read this and think that somehow the JVM has problems in its virtual thread implementation. I admit their 'Unexpected findings' section is very useful work, but the moral of this story is: don't use virtual threads for this that they were not intended for. Use them when you want a very large number of processes executing concurrently, those processes have idle stages, and you want a simpler model to program with than other kinds of async.

Why push java towards this 'failures as return values' when we already have a solution? Yes, you will be able to get the compile-time safety by immediately using switch on the return value, but what if you don't? Exceptions are a completely sound solution, failures as return values can easily escape detection.

No-one likes having to think about the error cases, it feels like it complicates things. But we need to stop seeing exceptions/try/catch as something to eliminate and realise that this approach is one of the best innovations of Java. Using return values, or monadic approaches to error handling, are fundamentally unsafe when you have a mixed paradigm language. Far too easy for the programmer to do something wrong, so we're relying on discipline again and not the compiler. In other words, back to square one.

What the...

Xbox does not have true exclusives these days, because of a strategic choice by Microsoft to ensure that Windows PC gamers (and Xbox owners that also have a Windows PC) will get the same experience. So how do we apportion successes PC gaming market when we look at "Who's winning in gaming"?

For sure, this strategy of letting Windows join the 'Xbox' family seems to have hurt sales of the console itself. A Windows PC and a PS5 seems to be the perfect combination to play all the best games. But is it a problem that Microsoft is making and selling fewer of a certain kind of hardware unit?

I really want Xbox to survive as physical hardware. We need competition in the market to push those gaming devices to be the best they can be. I just hope that it's understood how shifting fewer units is a natural and inevitable consequence of bringing Windows PCs into the family.

It might be assumed that Xbox lost this console generation. Yes, there were some major mistakes made in this generation and the last that must have hit sales. What has also happened, though, is that Xbox as an overall gaming brand has grown beyond the console itself.