skim VS dive

I really like using something like fuzzy search for menus like these. https://github.com/Cloudef/bemenu is pretty cool in that it works both in a terminal, X11 and on Wayland, so if you want to do something graphical later you can easily migrate. There's also fzf and skim, which work similarly but are only for the terminal.

Current profiles (to be improved upon): | Profile | Details | | ---------------- | ------------------------------------------ | | default | fzf-lua defaults, uses neovim "builtin" previewer and devicons (if available) for git/files/buffers | | fzf-native | utilizes fzf's native previewing ability in the terminal where possible using bat for previews | | fzf-tmux | similar to fzf-native and opens in a tmux popup (requires tmux > 3.2) | | max-perf | similar to fzf-native and disables icons globally for max performance | | telescope | closest match to telescope defaults in look and feel and keybinds | | skim | uses skim as an fzf alternative, (requires the sk binary) |

There’s also a variety of fuzzy finders like https://github.com/lotabout/skim or fzf. Basically the same thing, but different interface.

Have you ever tried sk? skim is an fzf re-write in 🦞. While I use it occasionally, I never really incorporated fzf into my workflow so I'd be interested to hear your opinion.

I’m not familiar at all with fzf, but I do know that skim supports this.

You state that as a blank and white fact, but there's nuance.

https://github.com/lotabout/skim/issues/317#issuecomment-652...

fzf skim

Agreed, but use skim instead

Dive is an open-source tool that allows you to explore the various layers of a Docker image. It shows you the content of each layer and helps you identify voluminous or unnecessary parts.

Dive is a great tool for debugging this. I like image reduction work just because it gives me a chance to play with Dive: https://github.com/wagoodman/dive

One easy low hanging fruit I see a LOT for ballooning image sizes is people including the kitchen sink SDK/CLI for their cloud provider (like AWS or GCP), when they really only need 1/100 of that. The full versions of both of these tools are several hundred mb each

This post is going to be shorter. I'd like to highlight a tool that I really enjoy working with called "Dive" It is an essential tool when working to build and optimize docker containers.

Whether you work with Docker regularly or even create your own Docker containers, Dive is a great tool for streamlining image sizes, potentially helping you save storage costs and speed up deployments.