![](/static/0b35d4a1/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/c0ed0a36-2496-4b4d-ac77-7d2fd7f2b5b7.png)
Let me simplify it: proceeds to print the same expression
Let me simplify it: proceeds to print the same expression
Deprecation warnings should contain suggestions for alternatives.
In general, given a Turing machine which outputs the result of a procedure to its memory tape, you can equivalently construct a recognizer of valid input/output pairs. Say P is the procedure, then the recognizer R is let (i, o) = input in P(i) = o
The reverse is also possible. Give a recognizer R, you can construct a procedure P that given part of the input (can be empty), computes the rest of the input that makes R accept the whole. It can be defined as for o in all-strings, if R(i, o) then output o and halt, else continue
.
It might feel contrived at first, but both views can be useful depending on the situation. You’ll get used to it soon with some exercises.
For all possible input, only recognize the one input that’s (under certain encoding scheme) equal to the sum of the given list. That’s for a given list.
Another more general approach is that, only recognize the input if (under certain encoding), it’s a pair of a list and a number, where the number is the sum of the list.
Nah, in real CSS, the window would overflow and bring down the whole house.
Look, there’s a thing called safety-catch and that’s why my son can play with semi-auto rifles.
If you execute a binary without specifying the path to it, it will be searched from the $PATH environment variable, which is a list of places to look for the binary. From left to right, the first found one is returned.
You can use which cat
to see what it resolves to and whereis cat
to get all possible results.
If you intentionally wants to use a different binary with the same name, you can either directly use its path, or prepend its path to $PATH.
Reminds me of the character White Rose from Mr. Robot. Here’s the introduction scene.
Sadly not its meta factory.
IMHO the reality is more complicated than what’s described here.
Open source is sustainable (in the sense that people will continue to do it), even without the maintainers getting paid, for better or worse. This is evidenced by the history and the majority of open source projects now.
The bait-and-switch problem, which gets the maintainers paid, hurts the ecosystem in the long run, which relies heavily on the good faith.
Static websites can be beautiful and easy to use without being complex.
PG’s blog and HN can definitely use some CSS tweaks. I can’t remember how many times I clicked the wrong thing in HN.
On the other hand, it’s easy to get reader mode/custom CSS/alt frontend working for such websites, so maybe it’s alright after all.
The original “agile” is a reaction to the overly rigid planning and emphasizes worker self-management. It makes sense since the people who are closest to the work (the workers) know best how to plan and implement the work.
It immediately breaks down when a specialized management tier emerges and tries to push their own agenda, i.e. to sell themselves rather than do something meaningful.
At this point, whichever form is used doesn’t matter. The management, endowed with the power from above, will exploit the weakness of any agile-shmagile methodology to push their own agenda.
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.
Why are they even on the same bus?
Request is not 3D tho.
There’s the GitHub product feedback repo, but as a closed source product (I know, the irony), you can’t point to the code for the problem and nothing other than blind luck can guarantee you a reply, let alone a fix.
On top of that, they are adding ads to the UI, even for paying customers, so there’s that.
I have to print f to show respect.
Yes for OCaml. Haskell’s inequality is defined as
/=
(for ≠).<>
is usually the Monoidmappend
operator (i.e. generalized binary concatenation).