Unlike a traditionally managed system, you manually keep an install list of all used system packages (including current version). It's conceptually similar to how conventional package managers might have a mirror configuration list. Within this list, you're also sprinkling in individual package options which Nix will automatically apply for you (the options that Nix "sees" are manually coded in by whoever did the bundling of that particular Nix package).
In other words: you're treating packages as if they were configuration and bundling that in with the actual configuration under a unified framework. This basically means that you can think of Nix packages as wrappers bundling the base software plus instructions for a config file generator. That's effectively the "gimmick" of Nix: config files are routinely regenerated, so in everyday use they're conceptually equivalent to an abstract interface between the Nix package manager and the software proper.
Worth mentioning at this point is the fact that the core Nix ecosystem is all about managing system-level software; Nix handles sudoer stuff and steers clear of interfering with user-level dotfiles. Using the hyprland wayland compositor as an example, you can see that the module only provides flags for things like NVIDIA patches and allowing xwayland -- options for shadows/colors/animations are omitted entirely because they should (under the Nix philosophy) be configured with user dotfiles.
Now with that being said, Nix itself is merely a package manager, so it's entirely possible to splash in as a companion to your distro's main package manager (similar to how you can globally install npm/pip packages). This is handy because Nix's ecosystem is highly invested in enabling users to write their own packages (i.e.: Nix Flakes). In fact, some Nix users exclusively use it as a framework for creating and managing custom packages whenever the need arises to install something not already provided in their distro's package repository.
Of course, the most vocal Nix users are all-in and use NixOS. With NixOS, Nix is your native system package manager. Everything system-level becomes Nix-managed, though the same leave-userspace-to-dotfiles philosophy still applies on the user level. This strategy enables cool stuff like seamlessly syncing your system environment between multiple workstations and having guaranteed safe restore points through the use of nothing but a handful of config files.
Beyond that, for the total Nix freaks, there's the Home Manager Nix package, which allows you to install and manage userspace applications Nix-style. This is handled separately from Nix/NixOS proper because userspace configuration is a much larger and faster-moving target. If you use Home Manager to fully capture your userspace, it's nigh-guaranteed that you'll need to get your hands dirty by writing custom Nix modules. As you may imagine, this process can be a big pain... though it comes with the benefit of being able to seamlessly carry user applications & dotfiles across any distro that supports the Nix package manager (including Darwin).
The story is more interesting than the title suggests! This guy was arrested for hacking two telecom companies, got released under investigation, then immediately hacked Nvidia before being put under house arrest. After that, he was relocated to a hotel (due to being doxxed) where all he had to work with was a Fire TV stick, which he promptly then used to hack Rockstar.
All in all, he's believed to have stolen $14 million+. By the way... he's 18, autistic, and enrolled in a special education school.
Should the NVD be deeply involved in all of them just to provide the most accurate security score? That’s an impossible ask.
This is a false dilemma. If the task is truly impossible, that's not a valid excuse to try anyway and fail repeatedly, especially if doing so causes negative externalities. Numbered scores with decimal precision are not necessary to the core functionality of a CVE database and there are plenty of alternative solutions which would minimize harm and scale more economically.
I just sort of let it go and join the background of life experiences. My brain already knows to remind me of a mistake when it's truly relevant, so why dwell?
Obviously this isn't great advice for those struggling... but it's what works for me. Not to brag, but I have an astoundingly bad memory, so not remembering things is kind of my forte.
"The screen is bonded directly to the front-facing camera, so the screen assembly must never be separated in order to prevent tampering with FaceID. As an additional anti-tamper measure, we've also recently begun permanently soldering the harness responsible for connecting the screen assembly and TPM. Unfortunately, this means that the screen assembly and motherboard cannot be separated without compromising system security. For the protection of our users, we at Apple cannot in good conscience offer any individual parts other than the case and master screen+motherboard assembly."
Note: if your knife begins plotting the demise of you or any other person, the best course of action is to assume your rightful place as an avatar of destruction.
It doesn't seem much closer to the blue Paris Accord goal compared with any of the other graphs in the same article, as far as I can tell.
As for India, I don't see how beating a goal of **+**25% emissions with +20% is any cause for celebration. I actually agree with you and the article when you say that they don't need to be held to the same standard as fully developed economies, but in that case we probably shouldn't be talking about them at all when it comes to meeting emissions reduction goals.
When someone says "China has absolutely not met the Paris accord goals" and you respond "New York times reported China is ahead of pledges", it creates the impression that you are correcting the former statement with a contradictory source. The source is not actually contradictory, however, because it explicitly affirms the original point.
They literally have a graph showing their paris accord goal as of now, where they as of now, and a 1.5c goal. They and India are ahead.
That is excellent. I'm very pleased to hear this. Perhaps you could share that graph next time instead?
EDIT: Content warning for the next reply in this comment chain: it contains a prank image featuring pig genitalia and feces. If you're on desktop, the image is hidden within a collapsed spoiler toggle that you can choose to expand if curious. If you're on mobile, please know that spoiler tags are not well supported in most apps yet, so this is your opportunity to stop scrolling if you happen to have issues with the described content.
... did you link the correct article? It seems quite critical of China's emissions?
None of the world's biggest emitters -- China, the United States, the European Union and India -- have reduced their emissions enough to meet the Paris Agreement goals.
Over the past two decades, China’s emissions have surged as the country has developed economically at a breakneck pace. Mainly because of its reliance on coal, one of the highest-emitting fuels, China now accounts for almost a third of all human-caused greenhouse gases — more than the United States, Europe and Japan combined.
Granted, the article says that China's emissions are projected to peak in 2025, but that still means emissions are estimated to increase every year for another 3 years. They have not (yet) actually reduced their annual emissions, let alone achieved anything close to net-zero.
According to projections from Climate Action Tracker and other monitoring organizations, China’s emissions are nearing their peak, years ahead of when China’s government had pledged to reach that goal. Analyses show China’s rate of emissions neither growing nor declining from now until 2025, before gradually dropping off. China’s peak will occur at a far lower per capita emissions level than countries like the United States.
The goal that China has beaten, it would seem, is their own internal peak date goal. It's good that they set and kept a goal, but keeping an internal goal is not the same thing as keeping the Paris Accord goals. The Paris Accord represents the bare minimum for avoiding a climate catastrophe and should continue to be the primary bar which we measure countries against.
Uh, why wouldn't they? Calculators check a lot of boxes that militaries care about: cheap, light, compact, durable, easy to manufacture, easy to use. I'd think that they'd be standard issue for any personnel regularly tasked with doing important calculations under logistically difficult scenarios.
Setting that aside... you are aware that modern battle tactics are completely, hopelessly reliant on battery operated devices, right? If a unit gets unintentionally separated from the grid long enough to start running out of power, there will be far greater fish to fry than a few botched arithmatic problems.
So, this is a question with a cultural and legal element. Legally speaking, it is possible in many U.S. states to be fired for no reason -- the employer does not need to explain themselves when asked for a cause[1]. This is to say that it's perfectly legally possible in (many) U.S. states to be fired for a reason so petty as a customer complaint -- whether or not that was the official cause notwithstanding[2].
With that being said, employers aren't compelled to fire their own employees in response to a customer complaint. From a management perspective, it's generally very inefficient to fire someone because you'll then have to cover their hours and find/train a replacement. For that reason alone, it's already rare in most industries for truly petty firings to happen. Unfortunately, this rule of thumb gets totally flipped in low-training industries whenever there's a surplus of bodies in the labor pool. As a manager, if you're able to replace a burnt-out and/or below-average worker by the end of the week, why wouldn't you roll those dice?
Even then, it's not exactly a daily occurance even in settings where these conditions are common... with one big exception. When it comes to businesses which serve "regulars" (e.g.: hotels, restaurants, grocery stores) there exists a certain type of individual who expects that their complaints will have the power to get people fired. This variety of power-starved person tends to exclusively patronize establishments where they feel taken seriously. Such establishments deliberately choose to indulge these sleazebags because they're potential "whales" -- people who, if handled correctly, will be worth much more money than the replacement cost of the staff they cause to be fired. These firings are basically performative in nature and have nothing at all to do with something the employee could have controlled.
[^1]: Protected classes are a whole other can of worms. For the purposes of this explainer, please just trust me when I say that the legal system is still able to protect protected classes without directly requiring paperwork from the employers themselves. The system would be significantly better at this job with a papertrail requirement, but the fact that it manages to work at all when employers can basically ghost employees is something worth noting.
[^2]: Another can of worms! As you may imagine, when giving a reason is optional, it is often (but not always) legally advantageous for employers to report petty firings as no-cause firings. It's all about CYA. For example, if they're doing something dicey like racial discrimination or retaliation against union organizers, an employer might go in the opposite direction and meticulously document dozens of petty reasons in excrutiating detail. This is usually what's happening when a service-worker employee is "written up" -- that information goes in a file to be used against them if they ever sue.
Unlike a traditionally managed system, you manually keep an install list of all used system packages (including current version). It's conceptually similar to how conventional package managers might have a mirror configuration list. Within this list, you're also sprinkling in individual package options which Nix will automatically apply for you (the options that Nix "sees" are manually coded in by whoever did the bundling of that particular Nix package).
In other words: you're treating packages as if they were configuration and bundling that in with the actual configuration under a unified framework. This basically means that you can think of Nix packages as wrappers bundling the base software plus instructions for a config file generator. That's effectively the "gimmick" of Nix: config files are routinely regenerated, so in everyday use they're conceptually equivalent to an abstract interface between the Nix package manager and the software proper.
Worth mentioning at this point is the fact that the core Nix ecosystem is all about managing system-level software; Nix handles sudoer stuff and steers clear of interfering with user-level dotfiles. Using the hyprland wayland compositor as an example, you can see that the module only provides flags for things like NVIDIA patches and allowing xwayland -- options for shadows/colors/animations are omitted entirely because they should (under the Nix philosophy) be configured with user dotfiles.
Now with that being said, Nix itself is merely a package manager, so it's entirely possible to splash in as a companion to your distro's main package manager (similar to how you can globally install npm/pip packages). This is handy because Nix's ecosystem is highly invested in enabling users to write their own packages (i.e.: Nix Flakes). In fact, some Nix users exclusively use it as a framework for creating and managing custom packages whenever the need arises to install something not already provided in their distro's package repository.
Of course, the most vocal Nix users are all-in and use NixOS. With NixOS, Nix is your native system package manager. Everything system-level becomes Nix-managed, though the same leave-userspace-to-dotfiles philosophy still applies on the user level. This strategy enables cool stuff like seamlessly syncing your system environment between multiple workstations and having guaranteed safe restore points through the use of nothing but a handful of config files.
Beyond that, for the total Nix freaks, there's the Home Manager Nix package, which allows you to install and manage userspace applications Nix-style. This is handled separately from Nix/NixOS proper because userspace configuration is a much larger and faster-moving target. If you use Home Manager to fully capture your userspace, it's nigh-guaranteed that you'll need to get your hands dirty by writing custom Nix modules. As you may imagine, this process can be a big pain... though it comes with the benefit of being able to seamlessly carry user applications & dotfiles across any distro that supports the Nix package manager (including Darwin).