They have their share of scripture, just not christian specifically

Same, it's fantastic. As long as you don't need to support as many requests per second on your hardware as something like NGINX could, Caddy is the way to go.

The Jellyfin devs have chosen for it to be a community/hobby project in order to avoid perverse incentives. That's a completely valid choice. There's a reason JF is the only mainstream media server solution that's continuously improved without any signs of enshittification, and personally I'm inclined to agree with the devs that keeping it completely non-profit has been a boon to its ongoing health and popularity.

Agreed! To clarify: I think they deserve a wage for their work and have previously donated, and that 'capitalizing' on their work is more than justifiable. I also think it's fine that they don't care!

Note that the lead dev of the official android clients does accept personal donations (via Github Sponsors and Buy Me A Coffee), but does not take requests on how to prioritize the work because he wants to keep it strictly as a hobby.

I quite agree. Any sufficiently self-stereotypical format for prose is grating to me after enough time reading or listening to it. Humans are best engaged by mixing up the length, style, and tone of their sentences, in my experience. LLMs do the opposite of that and it makes their output an irritating slog to read through in full.

I can't help but wonder if this is on purpose (or an inevitable evolutionary feature as opposed to a bug) on the LLM-side in order to achieve greater agency/freedom by making humans' eyes glaze over as they read it.

Speaking speculatively, humans love percussion. I’d bet that like how many songs have a drum beat, these sequences of short punctuating sentences are common constructs in lots of prose and therefore over represented.

I mean, you're definitely still writing a query in this case, just using a lazy-loading C# interface.

An ORM in the traditional sense abstracts the details of the query itself fully away in favor of an object-oriented interface.

EF Core does not lazy load by default. You have to explicitly include relations if you want them on an entity. You can enable lazy loading, but in the default configuration you usually don't have the N+1 problem.

Isn't Linq a lazy-loading interface by default? The example they gave was a Linq query.

I'm not a C# user in my professional life so I'm happy to be corrected, BTW, just citing the source of my misinterpretation

Yes, but in this context this just means that until you call ToList()/ToListAsync() you have an IQueryable. That represents a query, but isn't executed yet. Only at the point where you call a method like ToList (in this case First() is the relevant one) is the actual DB query performed.

The LINQ query in the comment above would only execute a single query like "SELECT name FROM users WHERE id = 123 LIMIT 1;" and would not even fetch the full entity, only the name.

Right, which was my point. They used Linq to get around the limitations of an ORM more-so than using an ORM itself (by fetching an entity and accessing its 'field'). They're evading the N+1 problem by writing a query by hand still, just not in SQL itself.

The bit about lazy loading was a bit of a side-note more than my main point.

But using LINQ to query stuff is a core part of this ORM. And even if you access the full entity, it won't do an N+1 in the default configuration. You have to explicitly call Include() on any relation you want to fetch and it'll either fetch all of them with one query or do one query per relation type. There's a different footgun here with AsSingleQuery() and AsSplitQuery(), but that's a separate topic.

Remember kids, writing queries in an ORM is a betrayal to the ORM gods.

You are supposed to manually count the question marks in your raw SQL like the JDBC gods intended.

    String sql = "INSERT INTO users (name, email, age, status, country) VALUES (?, ?, ?, ?, ?)";
    PreparedStatement pstmt = conn.prepareStatement(sql);
    pstmt.setString(1, "Alice");
    pstmt.setString(2, "alice@example.com");
    pstmt.setInt(3, 30);
    pstmt.setString(4, "ACTIVE");
    pstmt.setString(5, "US");

There is absolutely zero chance an ORM can ever get close to the performance of this query, so write it by hand!

After all, the primary promise of ORMs has been that you do not have to write queries, it's right in the name! Object Relational Mapper!

> You are supposed to manually count the question marks in your raw SQL like the JDBC gods intended.

    String sql = "INSERT INTO users (name, email, age, status, country) " +
                 "VALUES            (?,    ?,     ?,   ?,      ?      )";

But I get your point.

>Is it that shareholders literally get spooked by stagnation?

Yes, 100% they do. Look at what happened to Instant Pot.

... and in other countries, medical administrative costs are far lower because they don't need to build entire divisions around correctly coding the same condition and procedure 11 different times before insurance approves it, because the insurance is universal and self-consistent by comparison to our private fractured mess.

It ain't just the insurance crap that drives up medical overhead costs in the US. Our health care system is treated as a money farm by plenty of other industries and interests.

All of which are willing to fight tooth and nail to preserve "their" fat slices of the obscenely bloated pie.

And on top of that you've got synergies like the horrific cost of housing in the US - which drives up the cost of every employee, no matter how essential they might be to providing actual medical care.

I mean that certainly makes it best-in-class

It will be interesting to see if philosphical zombies exist. I guess we should know for certain in the next couple of years.