halflife VS nix

It's a part of C++ project https://github.com/ValveSoftware/halflife

I wonder if this is something you can amend in the actual code here: https://github.com/ValveSoftware/halflife

I know the most known issue about overbright on github already states that they will not fix it, but that was from 2013 and thoughts about overbright issue could've changed since then. Plus I am running HL on linux and this issue Infuriates me since I'm stuck using the OpenGL renderer (which is the only renderer that has this issue). We've known that valve really likes their linux oriented approach, and plus we know they love their Deckies that they updated HL2 with fixes and QoL stuff, what's stopping them from fixing overbright?

More info on texture scaling: https://github.com/ValveSoftware/halflife/issues/1650

Funnily enough, on Half-Life 1 engine-based games (i.e. the engine that came before HL2 - on which Team Fortress 2 runs; such as Counter-Strike 1.6), a different allocator problem exists -- glibc's malloc() just decides to fail miserably[0] on some setups.

[0] https://github.com/ValveSoftware/halflife/issues/3158

I guess you have to either modify the code https://github.com/ValveSoftware/halflife/blob/master/dlls/hgrunt.cpp

The original Half Life, including goldsrc, is source-available: https://github.com/ValveSoftware/halflife

And in fact even their Half-Life 1 bugtracker on GitHub is policed: https://github.com/ValveSoftware/halflife/issues

This is fixed in 2.24.6: https://github.com/NixOS/nix/releases/tag/2.24.6

See also https://discourse.nixos.org/t/vulnerability-in-nix-2-24/5190... for updates.

Can someone link to the actual fix? It's a bit hard to navigate the git history for me...

DigitalOcean does not have out-of-the-box support for NixOS. However, we can use a custom image to launch a droplet with NixOS.

Nix is an entire universe of software. It runs on Linux and macOS, on both Apple Silicon and Intel processors, and has several components:

I have been using NixOS for a long time. And I am very happy with it. It is very stable and easy to configure.

The data definition and operational model of SOPS is well suited for a Nix-powered system. sops-nix offers both NixOS and Nix Home Manager modules which provide a declarative way to manage secrets using SOPS.

Are you using an API gateway? Do you really need one? If you are using NixOS and feel comfortable with some Lua, you may want to consider OpenResty on NixOS as an API gateway.

Since then I have been using NixOS on my tinkering computers (x86 & ARM64) at home because I liked this one-file-format-declarative-definition of machines. With some new cloud technology evaluations ahead, for which I usually bring up dedicated disposable VMs, I wanted to transfer some of my NixOS learnings and create a disposable NixOS Azure VM. As I did want to create a (lame, everbody does that) custom image I was focusing a while on some infection methods (use any installed system and then "infect" with NixOS) nixos-anywhere and nixos-infect. I did only succeed to a certain point but had to stop because time was running out. One thing I learned in the past 3 decades: pull back in time before you get stuck in a rabbit hole, contain your frustration, swallow your professional pride and move on. Maybe someone reading this already has figured out how to bring NixOS on an Azure VM in this or another way.

If I remember correctly originally perl was a large part of nix's implementation. I thought they avoided haskell or another functional programming language in fear of recruitment issues and went with perl in part because it was known by the implementors.

Here is a github issue where they talk about some of the transition to cpp:

https://github.com/NixOS/nix/issues/341

Tenv manages all tools by wrapping them in an additional binary that serves as a proxy for the original tool. It means you can't install Terraform or OpenTofu on an ordinary Linux machine alongside tenv (except NixOS case). At our tool, we supply a binary with the same name as the tool (Terraform / OpenTofu / Terragrunt / Atmos), within which we implement the proxy pattern. It was required since it simplifies version management and allows us to add new capabilities to automatic version discovery and installation handling.