OpenGL is a low(ish) level hardware interface, that is almost certainly implemented in legacy unsafe code, so it will be fertile ground for CVEs. Presumably this is a security fix gone wrong

> Nix is very awkward (and slow) to use for fine-grained caching, which is price of entry for a decent build system.

This is sadly true, I've tried setting up a bazel-esque C++ build system in Nix, and the requirement for 1 derivation per .o file makes it very inefficient

> It also comes (practically) shackled to nixpkgs

This isn't true, and I think it is a shame that it seems true. Nixpkgs is both awful, and completely optional. It would be great if there were more resources on how to use Nix without Nixpkgs, or as is commonly requested, a smaller, cleaner and better engineered alternative

I know it technically isn't true and I use the word 'practically' deliberately. The problem is that as soon as you opt into one part of nixpkgs (say a compiler) you end up implicitly opting into large parts of it because of common code in nixpkgs that make assumptions about undocumented magic environment variables etc that other packages (e.g. libc) may make use of or set.

I feel like a core problem though is the assumption you use Nix for everything - as soon as you try and pull in prebuilt pieces for pragmatic reasons, or output something you can use somewhere outside of nix, it starts making life hard.

Honestly, I'm hoping for someone to use AI to translate the Nix universe of scripts to a saner and more modern, user-friendly language.

The FAQ seems clear on this

> Where is my code actually hosted?

> On bare-metal servers that we operate in Scaleway's Paris datacenters

That could change at any time. They could move to an Italy datacenter owned by a different company and that would be just fine.

But whether they're making a promise to stay in the EU specifically? Or whether they might expand to territories that aren't physically in Europe? That could matter, and the FAQ doesn't tell us.

(And yeah the line at the top says 100% EU but that's not the full picture.)

I hope they also have a backup outside Paris.

    const MAX: u32 = 100;  // Compile-time constant
    let x: u32 = 10;       // Cannot be changed

If x cannot be changed, how does it differ (meaningfully) from a compile time constant in a safe language, ie in a case of no raw pointers

const can be used in places that need a compile-time-known value (like a fixed array size). let can't, even if it obviously holds a fixed number.

The missing line on that graph is November 2019 when Github Actions were introduced. It would also show the point where things went wrong for uptime

Before Github Actions places I worked at pushed monliths to a dedicated CI, Github just hosted the repo, now we push microservices to a monolithic deploy pipeline. I'm sure someday we'll get it right, or maybe the robots will for us.

There are no need for permissions if the link per discussion is obscure and you use HTTPS. In that case the link is the password

Check it out now. Thank you.