I’ve seen some talk of replacing etcd with FoundationDB, which could yield similar improvements.

Ironically in SF it seems inversed. Whole Foods is second cheapest to Trader Joe’s, and Safeway is the most expensive.

I live in Los Altos next to Mountain View and Safeway is very expensive compared to every other option except Whole Foods. There are a few items they have that are the same as others, like bananas so I sometimes walk to the closest Safeway to stock up on those but otherwise one has to be wary of the pricing.

I was looking for this 2 days ago for a new computer setup.

I haven’t had a chance to download this yet, but hoping that it has native keybindings. (Cmd+N) on mac for composing a new email or something similar.

I know fastmail’s built in keybindings are robust, but I can’t keep track of them all.

Yes, the keyboard shortcuts are available, but I am unable to see browser navigation shortcuts like 'command + left arrow' to navigate to the previous page.

I don’t see this article actually arguing against GitOps. It just argues that the policies in place for GitOps need to make sense for the environment you’re developing in.

Obviously, the level of auditing and reviewing for infrastructure changes in a Prod environment make no sense for a Sandbox environment, and there’s nothing in GitOps that implies these need to be the same.

Ideally at every phase of development, you have very legible infrastructure that can be shared and iterated on by a team. The CI pipelines backing this should offer rapid turnaround times, and things should be easy to test.

All things which the general GitOps concept still works in tandem with.

Usually GitOps have flow like checkout => modify => commit => push => PR => merge => check result. Even if we remove the merge step, still have flow modify => commit => push => check result. In which the commit & push still could be removed

Eh, I think more optimistically, this is something her and her partner could joke about, and that he got a chuckle out of it.

I’m sure more heartfelt words were shared outside the scope of this obit.

One useful thing I discovered recently about zoxide is that it has a basedir flag, so in theory you scan scope your query to the directory you’re in or based off some git root.

something like

alias zg=‘zoxide —basedir $(git rev-parse --show-toplevel)’

https://github.com/ajeetdsouza/zoxide/pull/1027

Wow! That's really useful!

Yes, thanks!

My current assumption is that other classes of assets, assuming technological progress continues at its current rate, will grow significantly faster than demand for land. So the economics that once made homeownership favorable, no longer exist.

Holding the assumption that your landlord operates on favorable conditions (mine is pretty responsive and rent increases are controlled), I’m not sure I have a good reason to opt to purchase a house unless I’m planning on occupying it for the next 2 decades at minimum.

I can’t help but think purchasing is an emotional decision, unless the location you live in allows you to buy for a similar rate to the mortgage pricing, but I’ve only observed this in LCOL areas.

> My current assumption is that other classes of assets, assuming technological progress continues at its current rate, will grow significantly faster than demand for land.

You seemed to have missed one unique attribute of land. They’re not making any more of it.

A friend of mine built an alternative UI for this, that may be more digestible if you’re trying to lookup individual items.

http://plastic.food/

Running the container on Windows is probably a lot more complicated because there’s no obvious built in chroot + mount filesystem command (at least from memory).

I believe they’re built on silos. I believe containerd itself is probably as low in the container runtime as you’d want to go… See https://github.com/microsoft/hcsshim for the actual bindings.

iTerm and Terminal are pieces of software emulate a physical terminal environment. They take the output of programs/shells output characters and control codes to render text, clear the screen, etc.

The terminal emulator receives keyboard input via your operating system, and passes it to the shell program via stdin.

The shell is responsible for prompting you and handling whatever you type. For example the “$ “ waits for next character from the terminal emulator until you hit newline.

The shell is responsible for parsing your input, executing any child programs “ls” for example, outputting their content to stdout, and prompting you again.