An update:
If your company is on the U.S. OFAC SDN lists, subject to an OFAC sanctions program, or owned/controlled by a company on the list, our ability to collaborate with you will be subject to restrictions, and you cannot be in the MAINTAINERS file.
That’s more like his opinion or a post facto justification. Turns out it is a US thing.
If your company is on the U.S. OFAC SDN lists, subject to an OFAC sanctions program, or owned/controlled by a company on the list, our ability to collaborate with you will be subject to restrictions, and you cannot be in the MAINTAINERS file.
So to get back, you have to basically prove that you have no relations with OFAC SDN companies.
This update is from https://lwn.net/Articles/995186/
Unless you do something special depending on the day (like going to church on Sundays), aren’t the two options the same? They are both 4 up 3 down periods.
Haha, but it’s really a pack of tools, more like a toolbox.
// TODO: Leave the code cleaner than you found
Bingo!
Well, that already happened for Reagan and Arnold Schwarzenegger.
Philip K. Dick’s early novella The Gun describes this, but instead of chat bots, they were auto nuclear weapons.
Maybe I’m missing something, but shouldn’t the benchmark be a good approximation to the real workload? I don’t see how the measurements reflect the performance difference in real life usages.
Why would I need 100MiB/s processing as opposed to 20MiB/s processing, when I can only read maybe several lines per second?
Let me simplify it: proceeds to print the same expression
My gut feeling is that the procedural generation thing in Startfield somehow absorbs some people’s need for mods.
Deprecation warnings should contain suggestions for alternatives.
After the crush, they shout CR2032.
Reminds me of the character White Rose from Mr. Robot. Here’s the introduction scene.
It’s not presented as a loop and there’s no wife panel after the fourth one 🤔
I’m gett the ing UDP same vib joke
As other comments point out, they are usually not properly packaged through nix.
If you read the vim/plugins modules, for most plugins, the derivation just downloads the plugin, puts it to nix-store, and makes it available to the editor through environment variables. So it’s similar to the binary distributed software. Two most notable restrictions:
nix-store model.So for plugins that don’t have external dependencies (or dependencies other than the “common” ones like python or sh that happen to be available), and that don’t interact with the filesystems, this approach would be fine, but the more complex ones would fail.
In your example, mason failed because of 1, home-manager wasn’t aware that the pip module is a transient dependency of this plugin; and treesitter failed because of 2, because it doesn’t know that nix-store is read-only and should be managed by nix.
There are no general solutions, but people may have nixified some plugins on a case-by-case basis. If you don’t want to spend a lot of time (and remember that it might be broken by the next plugin upgrade), as others have suggested, take the traditional plugin management approach. (Personally, I use LunarVim which uses Lazy.nvim and it’s been working fine.)
This, but unironically used as a marketing trick:
There was no v1 of Oracle Database, as co-founder Larry Ellison “knew no one would want to buy version 1”
That’s why the first Oracle database is v2.
Linux Foundation (of which Linus is an employee) is an US entity. RISC-V International foresaw this and chose to incorporate in Switzerland.