X11 and everything around it is unfixable security hazard slop, just slop that was painstakingly created by humans.

Also Wayland is it being forced on us? I have plenty of coworkers that run X daily because they are still afraid of the Wayland boogeyman despite the fact that their supposed clipboard and screen sharing problems in Wayland (the only two supposed problems they can name) have been solved for years.

People don't use Xorg daily because they are afraid of wayland. People use Xorg daily because they have tried wayland and there was something that stopped working.

Xorg allows running sub-instances.

Wayland is now older than Xorg was when "it was really old, we need something new".

How do “stream over an open connection” and things like “sleep for months” play together?

Naively without digging into the code I would look at a “streaming over an open connection” as likely to strictly more brittle.

The way it works is that Restate supports suspending workflows that sleep for months and later (once the sleep finishes) resumes them at exactly this point. Technically, this is the same process as resuming a crashed workflow.

While the workflow is actively doing work (like calling other services, accessing state or interacting with external services, for example) the server is connected to the workflow deployment via a low-latency bidirectional streaming connection to receive and acknowledge progress that the workflow makes. That way the workflow can finish as fast as possible.

A nice side effect of this model is that you can co-locate your workflow with expensive resources, such as a sandbox, which should be used by all durable actions that the workflow executes. The reason this works is because Restate can inline durable steps (what would be modeled in Temporal as activities, I believe).

If a handler starts a sleep/human approval/RPC call, or so, then this timer/promise is persisted in Restate's journal. Restate does the waiting. The handler process itself can suspend (e.g. on a serverless function), and the bidirectional connection is closed. Once the timer fires/approval comes in, Restate re-invokes the service with the journal of previously completed steps, and the service can replay to the exact point in the code where it suspended and continue from there. Restate is like a DB for journals, so you can sleep for as long as needed, also months.

So you have fast persistence of events while a handler can make progress, and suspensions while waiting.

I guess the confusion is that it doesn't have to be one single persistent stream.

While the durable function does fast work and adds steps, it pushes it through a stream. When a wait point comes, it closes and replays on resumption (typical durable execution style).

That gives you the best of both worlds: same long-running workflows with long sleets and suspensions, but also ability to add steps with few ms overhead only.

Does this actually matter that much for some tools when the kernel is GPL?

I does. The OP says "Linux" but means "Linux distros", which are made of thousands of "commingled" pieces (i.e. the licence of one piece does not affect the other).

Each piece that becomes MIT means less pressure on corporate users to give back any changes they make, and we'll end back up in the 1980s again where "Amazon Linux" is full of secret-sauce they refuse to publish and makes the base system incompatible with "Google Linux" (or whatever happens to be kicking about), creating deliberate lock-in out of a system that started open. In much the same way that macOS and FreeBSD are divergent today.

In theory there could be a the MIT version relicensed to GPL and this version could be carried as a standard if having MIT software as core utilities was considered enough of a threat - right? You just have to retain original license/attribution.

That would be an awfully awkward move in the realm of Linux-related politics but if having an MIT-licensed coreutils was such an existential thread, at least you can fix it with aggressive license moves and not code.

We've balkanized Linux but you're free to use the original (which we are deliberately incompatible with, as is rival #2, rival #3, rival #4, etc. and we're all mutually incompatible with each other)

Amazon and other clouds already patch the hell out of Linux, but they don't distribute physical devices with that Linux on it to anyone, so they don't have to deliver source code either.

I am not totally sure I see the actual concern here, that a company is going to sell devices with a really great `find` implementation but not contribute it upstream?

In the 1980s and 1990s, there were a number of commercial Unices (SunOS, HP-UX, AIX, IRIX, etc.) Every one of them was incompatible with each other, sometimes subtly, sometimes blatantly. They were all competing against each other and all seemed to encourage you to use their proprietary extensions in your software and deliberately fuck over anyone using any other variants.

What it meant was a headache for writing platform-agnostic software. It was not a productive way to create software.

Replacing GPL software with MIT software just encourages this behaviour to come back. We already see it with how macOS userland took FreeBSD and sprinkled incompatibilities everywhere.

In the US there are very strong fraud protections for credit cards, but a debit card is just unfettered access to your bank account.

For safety reasons I never use a debit card for anything but an ATM.

you can just do a chargeback in case of fraudulent transaction.

That is not true for debit cards in the US, which is my point.

Don’t you need a runtime to do Go/Java style?

ArkKVM is a fully open source product now

No don’t worry they said it’s not slop because there’s tests lol

> Ideological Alignment

I too align and want to do business with people who's entire online existance is NOT centered around "Everyone who politically disagrees with me is a racist fascist and I want people to cause harm to them and I will ban them from my forums if they disagree at me at all about my politics"

Sweeping Nazi shit under the rug is one thing, sending them free money is even more pathetic.

Such a boring NPC response

Holy projection what a sad small little outlook

It drives me crazy that it shards your photos all over the place in opaquely named directories so you can’t actually find anything without its database index.

Photoprism is the best one I’ve found that will just take and index your folders as they are.

What do you mean opaquely named directories? It’s yyyy/yyyy-MM-dd/originalFileName. Those opaquely named files are the thumbnails.

Immich will also index your folders as they are. It’s called “External Libraries” in the documentation.

https://docs.immich.app/administration/storage-template/ is their best attempt to address your concern, but honestly I'm fine with navigating my photos solely using immich. (with annual backup copy stored in cold cloud storage)

For this exact reason, I'm using Immich by pointing it to my folder structure as an "external library" https://docs.immich.app/features/libraries/

I believe that's a setting, you can have it store the files in a more predictable directory hierarchy. Though it's better to make that choice early on before doing a lot of imports.