I limit fruit production based on the number of fruit on the belt, to avoid creating a huge buffer. But after that the factory just runs continuously at the same speed. And if I have too much of a final product, it gets destroyed or burned for heat and electricity.

One benefit, especially in the beginning, is that by processing more fruit you get more seeds. And you need the seeds to expand your fruit production later.

The enemies are probably one of the not ideally designed parts of Gleba. It's trivial to handle them if you know how, and can be very frustrating if you try to approach it the "wrong" way. If you have been to Vulcanus and Fulgora you can trivialize their threat.

https://factorio.com/blog/

https://factorio.com/blog/post/fff-441

https://factorio.com/blog/post/fff-442

https://factorio.com/blog/post/fff-443

Gleba is different, but I think that is good in a game that is as long as Factorio. There's a bit of a bumpy difficulty curve here if you approach Gleba in certain ways. But it is very different mechanically than the base game or the other planets in a way that is interesting, at least to me.

It took me two or three iterations when I first landed on Gleba. But afterwards my factories there were more robust than on the other planets and almost never stalled or broke down. And solving that was quite satisfying.

There was also bad communication on the topic, often when politicians got involved or due to outdated information continued to be repeated. But there certainly was a lot of public discussion about the risks of the vaccines, they were simply vastly outnumbered by the benefits of the vaccines.

And if you think this administration is prioritizing science with actual applications, I have a bridge to sell to you. The cuts they made are not sensible policy, they are inherently destructive and wasteful. They aborted studies that were still running, so a lot of money was spent and we'll never get any results from that because they were not finished.

And it's not just particular topics they hate, they hate the entire system and institutions. And they try to either break them and force them to adopt their political views, or they attack their funding or use any other powers to dismantle them.

This really doesn't sound believable to me, but who knows with all the craziness going on. Software developers in the US are seriously expensive, using them for data labeling would be a waste of resources. And the percentage sounds very high, unless "core teams" is only a small subset of the total developer count.

One thing I'm wondering about is the performance of temporal tables for the common case, when you only query current rows. When you manually version tables, one strategy is to have a second table that contains archived versions. So your main table only has the current rows, avoiding a performance hit for having many versions per entry. Is there a way to do this with temporal tables? For example partitioning between active and old rows?

Even for clearly despotic regimes, overthrowing them is not the obviously right thing.

Explaining text column types without mentioning limiting length with constraints instead of using varchar also seems a bit questionable to me.

https://www.postgresql.org/docs/current/planner-stats.html#P...