Your argument is to have 2 subtly incompatible abis and one day binaries magically break.

You’re right it breaks c stdlib, but that’s literally the point, libc is broken by design, this is the fix.

No program with time32_t will ever work after 2038, so any compiled that way are broken from compilation.

You’re right that the length isn’t specified though, the issue is changing types for triplets silently has unfortunate side effects.

If you really want to be clever, mangle the symbols for the functions that handle time so they encode time64 as appropriate, but doing it silently is begging for trouble.

This seems overblown, we’ve faced these things before.

The straightforward path is adding new calls and structs and leaving the old code in place, then having tests that return -1 for time32_t and seeing what breaks.

It’s not pretty, but this is life in the new epoch, gentoo doesn’t have it harder than anyone else except when they’re trying to rebuild while the transition is happening.

I know nobody wants 2 apis, 1 deprecated, but this is an ancient design decision we have to live with, this is how we live with them.

An infected phone app on your wifi can screw you.

Yeah.

My home server runs that many, but it’s a monster dual xeon.

The freebsd instances have a ton of jails, the Linux vms have a ton of lxc and docker containers.

It’s how you run many services without losing your mind.

I mean, the extension system means we could easily fix it, just deprecate the old paths, use the legacy xlib to set up extensions and write a lighter stack from there. A new input path too and you’re on your way.

It makes things a bit more complicated, but it’s also exactly how x86 managed to stay relevant all these decades, the old macro instructions are all slow microcode and you only use the safe stuff that’s hyper-optimized.

Meanwhile you get the one thing X has: It works.

Rust zealots are on an unstoppable jihad.

Expecting suicide fork bombers any day now.

Yeah sorry, c/c++ guy here.

I get that rust is the new shiny.

But now it means changing any potentially bound c function means I need to be fluent in a language I barely heard of before this year and has a syntax that makes c# look normal.

So, how about no?

Wtf man, I never even pushed that shit upstream!?

https://forums.linuxmint.com/viewtopic.php?t=244076

Alternately:

https://forum.xfce.org/viewtopic.php?id=16993

xfconf-query -c thunar -p /misc-open-new-window-as-tab -s true && thunar ~/Downloads

2 things:

1. It’s more the determinacy, a GC randomly fires up and your systems stops for some long amount of time. There are pauseless GCs but that’s a different nightmare.

2. The kernel has things similar to GCs. They’re used for more specialized tasks, and some (like rcu) are absolute nightmares that have take decades to get working.

Trump’s coin dropped already.

Qxl does, it’s fairly modern.

Otherwise you have virtio and virglrenderer, which are as modern as it gets this side of pcie pass through or intel’s sriov.

Vga is fixed iirc, the original frame buffer was tiny, the emulated one gives you 16mv

Cirrus logic gives you 16mb too iirc, then you can use other drivers that give you more,

https://www.kraxel.org/blog/2019/09/display-devices-in-qemu/

It did, let me explain:

On the original (ie Thompson and Ritchie at Bell in 1969-71), I think it was a PDP-11, they installed to a 512kb hard disk.

As their “stuff” grew they needed to sprawl the OS to another drive, so they mounted it under /usr and threw OS components that didn’t fit.

https://landley.net/writing/unixpaths.pdf

I’ve done the same, outgrew so you mount under a tree to keep going, it just never became a historical artifact.

It meant user, as in user-installed programs and libraries for this system over the core system programs and libraries of the operating system in /bin and /lib.

Someone learned it wrong, but otherwise I think the image is right.

It’s a great language, and I even like their deployment/packaging system.

But oh my god it assumes everything follows its rules, and does NOT play well with others.

We need a rust-based distribution, there can be only one.

Did that a few times, the difficulty is keeping it up to date with new releases or distro hopping, I just git clone my environment with a bin path and distro specific environment variables.

Fyi /usr/local/bin is for system wide applications, freebsd and it’s friends use it for non-core software installs.

Unix has had a long running convention of separation between “operating system” and other files, so you can blow away something like /opt or /home without making your system unbeatable.

If you stick stuff under /usr/bin then you have to track the files especially if there are any conflicts.

Best to just add another path, I use ~/bin because it’s easy to get to and it’s a symlink from the git repo that holds my portable environment, just clone it and run a script and I’m home.

Oh sorry that was badly written, I compile my own kernel and run lxc on top of that, with debian base userspace otherwise.

Then kvm on top for really different stuff.

For my server it’s debian on the bottom with zfs file serving raidz2, and on top of that 1 kvm for debian docker containers, and 1 kvm for freebsd jails which actually hosts most of the services I care about, docker is fallback if they’re a pain to set up.