At this point I wonder if there are some internal politics that want this project to fail and be over. 70 price tag, live service but only on ubisoft platform, ignoring the most demanded features, etc.
It's like they are tired of a project that was a money black hole for years and they just want to pull the plug.
That's the traditional italian way. Instead of using hard dry mozzarella that can be grated, you get super soft fresh mozzarella and slice and put on top.
Not to mention, Pomegranate in Spanish is Granada, literally Grenade. It's also one of the more famous regions in Spain, and it exports a lot of that fruit, which, as is usually the csse, has both Spanish and Portuguese on the labels to reduce costs.
No one in Portugal should jump to that conclusion unless they are ridiculously xenophobic.
The texture healing technique is technically brilliant, but imho looks weird.
I will stick to Source Code Pro.
3.0 and 3.3 were big on optimization iirc.
They also moved to the custodian system which makes stellaris easily the most polished and stable of all of Paradox games
Thats not true at all, there has been incredible improve, particularly with jobs.
We got our swamps, but then came the Dutch and they defeated the sea.
Humanity will survive this but everyone will suffer the effects. Even something relatively minor like COVID had great effects to the global economy, but with these we are talking about:
Weather inestabilization, with greater storms and massive heat waves.
General crop failures in many places of the world.
Desertification in many areas.
Massive migration waves.
Very difficult and unstable economy.
We are starting to see some of this, but 2050 onwards is going to be a very difficult time for all humanity except the most wealthy.
I don't think Lemmy is more privacy friendly. In fact, its, arguably, even less privacy friendly that others.
I kind of agree with your points, but I think there has to be a distinction of libs. Most deps should be static IMHO. But something like OpenSSL I can understand if you go with dynamic linking, especially if it's a security critical program.
But for "string parsing library #124" or random "gui lib #35".. Yeah, go with static.
I have yet to find a memory hungry program thats its caused by its dependencies instead of its data. And frankly the disk space of all libraries is minuscule compared to graphical assets.
You know what's going to really bother the issue? If the program doesn't work because of a dependency. And this happens often across all OSes, searching for these are dime a dozen in forums. "Package managers should just fix all the issues". Until they don't, wrong versions get uploaded, issues compiling them, environment problems, etc etc.
So to me, the idea of efficiency for dynamic linking doesn't really cut it. A bloated program is more efficient that a program that doesn't work.
This is not to say that dynamic linking shouldn't be used. For programs doing any kind of elevation or administration, it's almost always better from a security perspective. But for general user programs? Static all the way.
Because they were friends (or at least knew each other).