120 karma · joined November 29, 2019
Check out my latest project ! Snackbag.dev
But if you run nix you could give it a whirl: https://github.com/KritR/ghostty-kms
But when hunting for them in the wild, they get a lot more confused.
But this has been pretty nice for me.
It’s also open source if you want to customize it for your own preferences (pinned apps, custom keybinds, etc)
Changes branches took an eternity, and people resorted to a more workspaces style solution.
If you’re planning on starting a big tech company, I wouldn’t recommend the approach.
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.
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.
I’m sure more heartfelt words were shared outside the scope of this obit.
something like
alias zg=‘zoxide —basedir $(git rev-parse --show-toplevel)’
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.
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.
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.
If you can get away with this, keep doing so, but definitely recommend putting some time into the 59000 / 69000 classes taught at the grad level. Advisors let you swap elective classes in your track for the higher level ones, and they’re far more interesting (especially for the AI/ML track). Also connects you with more professors that would be research oriented (if that was something you were interested in). The program also had an exchange with ETH/KTH which unfortunately I couldn’t take advantage of due to COVID.
I think it just happens to be that we like assigning colors to differentiate things in the mathematical side of CS.