1. Buy groceries when the price is low.
2. Refund when the prices go up.
3. Profit!

Yes for OCaml. Haskell’s inequality is defined as /= (for ≠). <> is usually the Monoid mappend operator (i.e. generalized binary concatenation).

I first read “mortgage of the family” and somehow it’s worse.

Let me simplify it: proceeds to print the same expression

Have you heard of 996.icu? I don’t know where you get your statistics, but have a walk around 五道口 and you’ll understand.

Also, I don’t know where you see that I’m a fan of CCP. The government is largely responsible for the phenomenon by not prosecuting the companies lol.

I’m not saying that this isn’t a protest, but merely providing the context for the protest. They took the relaxed dress code to an extreme and deliberately interpreted it as “anything you like”. It’s more of a malicious compliance protest. That’s why they were scolded by the leader, instead of being fired.

I’m not saying everything about China is evil, but 996 is an actual thing, actively resented by Chinese young people. I’ve got friends working such schedules. I’m presenting their views. I had also visited their offices and saw the folding beds.

For those who don’t know, it’s not quite new (except for the word that describes it, Ban Wei 班味). Because of the long working time, a lot of Chinese companies (especially in the tech sector) allow very casual dressing, plushies, even folding beds in the office. Sounds good but is actually horrifying.

The sentence meant to be sarcastic. The dry humor was lost in translation.

It’s a one-piece pajama in the video. She has a coat over it during the work.

Because these two industries are both labor intensive.

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:

1. Nix is not aware of transient dependencies.
2. The plugin is not aware of the 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.

https://en.m.wikipedia.org/wiki/Oracle_Database

It’s real, but mainly aims for corrupted former officials, e.g. Operation Fox Hunt. Arresting Hong Kong dissidents might be more politically difficult.

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.

Not just installing. When updating, sometimes it tries to reset the options and change my default browser to edge.

Try fzf. The default hooks will launch fuzzy finders for

• C-r: history search
• Alt-c: change directory
• C-t: fill in argument for a nested path

All seem pretty good for your use case.

It’s a “terminal multiplexer”, i.e. you can start multiple terminals in a single terminal.

You might ask, why not open a new terminal window or tab? Well, you can only do that in a desktop environment and that’s not always available. Even if you can, you might want the terminals to be side by side in a single screen, which might not be easy to do with window tiling.

The real power of tmux, though, is that it manages the session you created. To quote from the manual:

tmux may be detached from a screen and continue running in the background, then later reattached.

So, one use case would be saving your current terminal setup. Instead of exiting the terminal and navigating to the project and setting up the environment again next time, you can simply detach and re-attach.

When connecting to a remote server, this is especially useful:

Each session is persistent and will survive accidental disconnection (such as ssh(1) connection timeout) or intentional detaching

Suppose you want to execute a long running command on a remote server. If you just put it to foreground, when you exit the ssh session, the job is also killed. If you put it to the background, its output can’t be easily observed.

With tmux, you can simply run it in the foreground like normal and detach. When you reattach later, the job is running and you get all the output easily, as if you have been in that session all along.

Reproducibility is a blessing for both software development and daily use.

NixOS