The original font on the album is Prestige 12 Pitch, with some manual fuzzing.
The track list on the back is in FF Trixie.
Using FF Trixie to produce a PNG, you get this (in black and in white).
The original font on the album is Prestige 12 Pitch, with some manual fuzzing.
The track list on the back is in FF Trixie.
Using FF Trixie to produce a PNG, you get this (in black and in white).
@Fischblog https://www.amazon.de/Peter-Turchin/dp/0452288193/
Peter Turchin hat dazu viel geschrieben
Source: https://x.com/KatysCartoons/status/1504463231380865031
Bis 2050 wird Kernfusion die dominante Energiequelle auf der Erde sein. Dazu soll der offene Reaktor im Zentrum des Sonnensystems durch Fernfusionsempfänger angezapft und mit Batterien stabilisiert werden. Ergänzend wird (Windenergie genutzt) EDIT die dabei entstehende Abwärme mittels Niederdruckgeneratoren in elektrische Energie umgewandelt (https://mastodon.social/@buur/112353980651723797)
@lobingera @mschfr kann man so nicht sagen https://en.m.wikipedia.org/wiki/Crab_Nebula
@lobingera @mschfr alle Elemente mit einer höheren Position als Eisen im Periodensystem sind so entstanden und verteilt worden.
Sie sind außerdem selten.
If Nextgres gets you to think about this, this is good.
Just don't see it as a drop-in solution for your problem, because it isn't. At all.
Modern Postgres has a solid replication story with logical replication, but this is more expensive than with MySQL and does less.
Logical replication generates the equivalent of a binlog from the WAL, but on the fly and for each replica anew. This costs more CPU on the primary by comparison.
The concept of GTID is lacking, so you essentially have async or semi-sync RBR, but need to come up with the equivalent of primary-switch logic from before the invention of GTID.
I have been searching only cursory, but have not found methods to stop replication at a predetermined log position, which makes primary switches or clone-and-resume operations a thing that needs more research.
I am also unaware of any concepts mirroring wsets and group replication, but I do know that there are clustering solutions for Postgres. I still have to look into them.
All in all, operational concepts do not port well, and require careful planning
On the other hand, if you have an application where Wire Format and SQL Syntax are the main problems that prevent a port, you have other, much larger problems and maybe want to do a refactoring project before even considering any migration (even to a newer version of MySQL) project.
That said, with the current enshittification of pseudo open source projects and with the managements shambles that MariaDB is in, Postgres may well be the preferred migration target.
https://hachyderm.io/@tobyhede/112329476255728961
Thank you. You can stop sending me this link. I have seen it.
I am intrigued how robust this is, and how valuable this is.
When writing PHPLIB two decades ago, I wanted to store simple session data in a database, and found that even simple data types such as VARCHAR (because of charset handling) and Date and Time types were not very portable.
On top of that there are often a lot of assumptions into query performance that go into SQL, …
and that can maybe lead to disappointments. Unless your SQL is trivial (for Web stuff, it often is), it may not be a straightforward plug and play.
All in all such migrations are possible, and having done them, I found that wire protocol and SQL Syntax are usually not the obstacles. Especially if an ORM or generated SQL or a proper DAO story are involved.
Also, this is a dev story.
It is not an ops story.
When plugging a Postgres into an application that previously used MySQL, the ops story still is thrown out completely and needs to be redone from scratch. This is often the bigger part of the task, even without such a module.
You'd have to redo backup and recovery, replication and scaleout, monitoring, and all other operational and maintenance aspects of the database (unless you are on AWS, but then the database choice …
hardly matters at all, and you have other problems instead).
Postgres behaves operationally very differently from MySQL. For example, MySQL is happy with ephemeral connections as they are common in a PHP context, and can handle thousands and with tuning ten thousands of concurrent connections directly.
For Postgres you'll fail at hundreds, and need to introduce a proxy layer. Postgres also hates ephemeral connect-query-disconnect execution, so the proxy is mandatory here, too.
Spotify hat sich geköpft und ist nun überrascht, das nur mit dem Rückenmark denken operative Herausforderungen generiert. Der CEO redet sich seinen Griff ins Klo schön.
Mit dem Angriff KI wird das aber alles in Ordnung kommen.
Wolkig mit Aussicht auf Fleischbällchen
Oder jedenfalls mit klumpigem Niederschlag und Gewitter.
Stellt sich raus,
https://www.theverge.com/2024/3/23/24109511/stability-ai-ceo-emad-mostaque-resignation-decentralized-ai
Stability AI CEO resigns to ‘pursue decentralized AI’
https://techcrunch.com/2024/03/22/stability-ai-ceo-resigns-because-youre-not-going-to-beat-centralized-ai-with-more-centralized-ai/
Stability AI CEO resigns because you’re ‘not going to beat centralized AI with more centralized AI’
hatte einen ganz anderen Grund
https://www.theregister.com/2024/04/03/stability_ai_bills/
Stability AI reportedly ran out of cash to pay its bills for rented cloudy GPUs
Das nimmt jetzt langsam die Form von Cryptocoin-Goldrausch an, wo die einzigen, die Gewinne machen, Schaufelverkäufer sind.
Die Lehre aus dieser Rechnung ist übrigens die enorme Energiedichte von Schokolade.
Ihr könnt das auch noch einmal mit Himbeersaft oder Lebertran rechnen, wenn Euer Fliewatüüt keine Milka verarbeiten kann.
Also ein Apron von 8*8*24 Metern, bei einer Dichte von 2.5 t/m^3 also 3750t Beton, jeweils vorne und hinten an jedem Brückenträger.
E = ca. 1 GJ, oder 277,78 kWh, das ist in etwa die Energiemenge, die unser Haus im Februar produziert hat (3,6 MJ sind 1 kWh)
Oder bei 2246 kJ Energiegehalt einer Tafel Milka Kuhflecken 445 Tafeln Schokolade.
Man rechnet bei Beton mit einer Energieabsorptionsfähigkeit von 2-5 MJ/m^3
Also ca. 500 m^3 Betonbauwerk, das sind etwa 8*8*8 Meter, mal Sicherheitsmarge.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.