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.

Consumer protection laws obviously don't apply to businesses, and banks close business accounts all the time for not following the terms of services. That sounds like a MUCH more probably cause than "I said mean things about Palantir".

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

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.

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

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.

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

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.

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

That's a random study I found on Google, of course, I'm sure Meta has more accurate data on that.

Besides, you need to build the same kind of redundancy in both cases, so that shouldn't influence the choice.

[0] https://www.canada.ca/en/conservation-institute/services/con...

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.

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.

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

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

* availability. On AWS, you can start a couple dozens or hundreds of instances on demand, for a limited time. You are paying for that spare capacity. VPS/Dedicated servers generally have much lower spare capacity, and you're booking things by the month, not by the minute.

* reliability. Most real cloud instances live on networked drives, and your risk of losing data is very low. On root servers, you have to handle data reliability yourself earlier. (you should do backups either way, but you're likely going to use your backups more often on VPS/Dedicated offerings than in the cloud)

* surroundings services. Private networking, security features, etc.

You pay a premium for all that, so for the same raw compute performance, cloud prices will be at least 2-3x the price of a basic root or dedicated server. On the other hand, vps/dedicated servers typically include bandwidth in the price. The best choice depends on your requirements, but most people will blindly go towards cloud servers..

It's pretty easy to trigger ci runs via git hooks, and once you're used to it, checking their results in jenkins instead of in the git repository UI makes no difference. But code reviews really need a dedicated interface.

[0] https://github.com/mtoyoda/sl [1] http://r-wos.org/hacks/gti