

Looks like an F# pipeline
Looks like an F# pipeline
A common feature of all these lanterns
For sure, and Ocaml is a dream
F# is “beautiful” and “pretty well supported”, making it a good ramp-up.
surely you mean Algol style languages?
“the west”? huge tell there regarding OP. That wording doesn’t appear in the paper.
Confirms something I’ve strongly suspected about you.
Check out “densly packed decimal” encoding,
OP is a “C guy”
A systems language, one of the oldest but still in use and modeled after, used to build expensive research toys, which compiles itself via its interpreter…. is in some 4d space this plane doesn’t slice through.
FORTH also out in space somewhere
Except for the thousands of lines of boilerplate 🤷♂️
and Scala
Not a single link there to technical details about the projection.
Threw in some RWNJ “we’re being censored” noise as well. Fits with the XLibre crew.
you dont write letters as pages of markdown bullet points?
probably because they already own it.
use some file system with snapshots and differential backups, like ZFS, and snapshot it daily. Stream the diffs somewhere they can’t login to and which doesn’t mount the FS.
This will invariably save their bacon at some point.
I got news for you:
X11 has seen many extensions, competing standards, fragmented implementations, ambiguous “best choices” for users, etc.
MacOS and Windows have seen many API changes, deprecations, even wholesale language and architecture swaps.
X11 is a 40 year old architecture that is far from optimal.
The people doing the work set the standard in the Free Software world. They stopped working on XFree86.
Part of the friction getting linux on the desktop is due to X11.
You can still run twm and X. No one is stopping you.
why in God‘s name would you ever use that before rust or swift?
this is how those Marxist Leninst nation state actors work
Why would you reserve ram for swap???
You’re hindering the OS’s ability to manage memory.
Put swap on disk. Aim for it to rarely be touched - but it needs to be there so the OS can move idle memory data out if it wants to.
Don’t hard-allocate a memory partition for postgres. Let it allocate and free as it sees fit.
Then the OS will naturally use all possible RAM for cache, with the freedom to use more or less for the server process as demand requires.
Monitor queries to ensure you’re not seeing table scans due to missing indexes. Make sure VACUUM is happening either automatically or manually.