Wilya

Yeah, that completely invalidates his point.

I looked at a couple random agentic sessions in my openrouter activity, and the input cost is 10x the output cost.

Prompt caching on openrouter is complicated and unreliable. On local hardware with llama-cpp, it's mostly free.

The guy has a "Conspiracy theory and disinformation" section in his wikipedia page, that mentions 9/11.

Come on. That's your "totally not pro-russia" example ?

In 2015, systemd was a giant, immature and complex galaxy of tools, that came to replace a hacky-but-mostly-stable bunch of shell scripts. It was pushed fast. It came with good ideas and innovations. It also came with security issues, bugs, and lost productivity.

The fact that the main guy behind the project has a very... abrasive personality, and that the project got to widespread adoption through political moves more than through technical superiority, turned that dislike into hate.

But it's 2025 now, systemd has stabilized now, and I don't really see the point of all this anymore.

In full-cloud environments, in small/middle companies I've worked at:

Developers handle 1). Devops handle 2)/3)/5). Nobody does 4)

Youtube premium is still ad-free. There is a Youtube premium lite which is kinda-ad-free-but-not-really, but the full ad-free one still exists.

It depends how it is done. I used to think the same way, and I would never hire someone without having seen them program live.

But having experienced leetcode-style interviews on the candidate side, it's clear to me that they are no longer about figuring out and coding a solution on the spot. Interviewers expected a solution FAST, and to match that you need to have studied and learned the answer beforehand.

I blame everyone else and myself equally.

But I'll stop whining about politics when I'll stop witnessing well-behaved but incompetent people turn projects to failures.

> But regardless how fast we achieve net-zero carbon dioxide, there is good reason to believe that the societal impacts of extreme heat are manageable, and across different scenarios. For instance, according to the World Health Organization, even with increasing heat waves, mortality does not have to increase.

There are two big problems with this take:

1. The author takes the "100% adaptation scenario" from the paper, and ignores the rest of the discussion. Yes, if we mitigate the effects of heat waves, there will be no effect. I could have guessed that myself.

2. The part of the paper is about the deaths directly attributable to heat waves on people aged 65+. That is a super narrow metric. Maybe the author should read the "Undernutrition" part of the paper he himself quoted, which paints a very different picture. And that's not even the full picture.

In France last summer, some plants had indeed to be shut down because of the drought but:

* a minority of plants were involved, it was only an issue because it happened on top of other issues (planned maintenances delayed due to covid, corrosion issues)

* the problem isn't actually the drought, it was the heat. The plants could keep operating, but they would have rejected water too hot, in breach of environmental regulations.

Besides, new plants can be built close to the sea instead of rivers to account for that.

The resistance is already there, it's already happening. Car owners in Paris are furious, and bike infrastructure is already taking away space from roads. High traffic roads in the center have been downright closed and made bike-only.

It is feasible because Paris (the city itself, excluding suburbs) is a very crowded city, where owning a car has always been a luxury. People living in Paris itself who can afford a car, with the associated parking space and everything, are a minority.

People living in the suburbs are more likely to own cars and drive through Paris, but they don't elect the Paris mayor, so their opinion doesn't have much weight.

At every single org I've been where Datadog has been considered, the conclusion has been "Yes, it would be cool, but we really can't justify the price."

Yes, in theory, in the middle scale, you should outsource things, but in practice, it only works if the managed service is at the right price.

It is not an inconsequential oversight. Most people will at least have sessions open to internal/private systems, sometimes sensitive credentials. And part of the teams will go see clients with their company laptops. You absolutely do not want people to be careless about leaving their computers unlocked.

The number-based scheme is a leftover from old times. I don't think they are actually used for ordering how the migrations are applied anymore.

The migration file will contain explicit dependency information, something like:

  dependencies = [
    ('app', '0010_alter_menuitem_absolute_url')
  ]

The migration engine will order the dependencies at runtime, and it will bail (and suggest creating a "merge" migration) if you have diverging trees of migrations. I find it pretty robust in practice.