How steep is the learning curve there? Should I just go with Plex and keep it simple?

You’ve got it the wrong way round. Jellyfin is simple. I’ve never understood Plex.

They do. You look at it every time you see the contents of your disk. It’s just organised in a tree to make path based lookups fast and locate organises its database differently to make fast basename lookups.

As I would expect. Does the result surprise people?

If so, rename the arguments to fun() to be r, s, t, and u. Just inside the function. Does the obvious two scopes now make it clearer?

.net

Anything I run in C# or similar seems to allocate 512GB of virtual address space and then just populates what it actually uses.

I’ve got a 12. I really like it.

Get a DIY one and put your own memory and SSD in it. You’ll save £$\€ over the framework prices for those. I paid about £750 total for my maxed out 48GB/2TB one. Then slap something like Fedora on it and you’re good to go.

I got a Lenovo slim pen 2 as the framework stylus isn’t out yet. Pairing required holding the buttons for ages, but works great after that.

It’s more my back than my knees

…or PCMCIA for short.

Go with a VM for FileMaker I’d have thought.

BTW Bonjour is known as multicast DNS in the non-apple world and the standard Linux way of supporting it is Avahi.

Agreed. The headline is terrible. Headline Case Doesn’t Help Either.

I think it’s cheese-stringification.

A lot of the security fixes since spectre have focused on exploiting speculative execution (a key CPU performance feature) to cross security boundaries. Defeating speculative execution when switching from user to kernel space (for example) adds a lot of overhead.

The new kernel add controls so that machines that don’t need to worry about these exploits to disable the performance killing fixes.

It’s a few hundred lines of C across 7-8 files. It checks the password hash against a set of predefined ones and then calls a script if it matches.

It doesn’t need a lot of maintaining.

So I can never commit a test without also implementing the functionality?

That’s madness.

You’re both right. You’re both wrong.

• You write tests for functionality before you write the functionality.
• You code the functionality so the tests pass.
• Then, and only then, the test becomes a regression test and is enabled in your CI automation.
• If the test ever breaks again the merge is blocked.

If you only write tests after you’ve written the code then the test will test that the code does what the code does. Your brain is already polluted and you’re not capable of writing a good test.

Having tests that fail is fine, as long as they’re not part of your regression tests.

As does Arch.

The avalanche has started. It is too late for the pebbles to vote.

Now you’re being silly.

What’s a good alternative to Jira?

…except there’s no hardware to run it on. They’ve chosen an ISA profile that’s not been decided on for long enough.

I think people who dislike flatpaks or similar aren’t having “problems”. They work, but they’re using using a sledgehammer to drive a nail.