I love the minimalistic approach of ascii charts:

  Apples         xxxxxxxxxxxxx------- 100
  Bananas        xxxxxxxxxx----------  75
  Oranges        xxxxxxxxxxxxxxxxxxxx 150
  Grapes         xxx-----------------  25
  Pineapples     x-------------------  10
  Watermelons    xxxxxx--------------  50

- https://mrrartpro.com/

- and as Obsidian plugin: https://github.com/alincoop/obsidian-tinychart

The fact that it's a class on ethics and technology is quite ironic.

From the article:

> "A lot of students who take philosophy classes, especially if they're not majors, don't really know what philosophy is," she said. "So I like to get an idea of what their expectations are so I can know how to respond to them." Sounds very reasonable to me.

Looks nice, residuals the merging is something I haven't seen in other clipboard managers.

I think my main question is why I should use a browser-scoped clipboard manager over a global, system wide clipboard manager (that allows me to filter by application).

Thanks!

And you raise a good question. So just to make sure we're on the same page, even though the extension is browser-scoped it still has access to the system's clipboard across other apps so things you copy in VSCode will show up in the history. It just doesn't know that you copied it from VSCode specifically so yes you can't filter by application like you say.

So with that drawback in mind, I believe the advantage is that it's less intrusive and cross platform by default. Whether it's simpler needs, app fatigue, or work restrictions, some people just don't need a whole app for this one feature (especially when those apps usually come with a whole suite of other productivity tools, requiring more permissions and resources).

This is all just based on my own experience as a user of an existing popular extension though (https://chromewebstore.google.com/detail/clipboard-history-p...). I can't speak for all other 100k active users but my guess is that what I described above is approximately the reason for its popularity.

100K people that don't know that clipboard managers exist as a system application/and or are limited on what they can install at work.. But are also probably sharing all their clipboard history with the addon creator. :facepalm:

Yeah the goal of my extension is it's open-source and people have the choice to build/install the extension themselves.

Also you're being a little close-minded about the 100k users, people are simply different and have different needs. I for example know these productivity suites exist but choose not to install them because I don't need the other features and have also had bad experiences with apps ruining my system state.

I sometimes use sounds as opposed to print statements when debugging automations or certain UI behavior, e.g. to indicate whether a certain if-condition was triggered or not.

The advantage over normal print debugging is that you get immediate feedback, and do not need to switch to a console. This is also useful when it comes to debugging split second timings (custom window movement scripts).

You just gave me the idea for a tool that watches log files and plays sounds when certain patterns occur.

FourSquare, or rather location-based social networking in general. Bummer that this category of apps did not work out, had real potential to connect people locally.

Unread for iOS. I think it has the smoothest UI of any mobile feed reader.

Unread is now available for Mac as well. (Full disclosure: I am the developer.)

With the syntax being a selling point, I think having a comparison between jq, yq, and dasel would be really useful. Luke a few examples how to accomplish X in each one of them, so we can judge for ourselves which syntax is preferable.

Comparison of last example from https://axel.leroy.sh/quick-refs#dasel

desel: .data.all().filterOr(moreThan(.quantity,3),equal(.quantity,3)).mapOf(key,key,quantity,quantity)

yq: .data[] | select(.quantity >= 3) | {"key": .key, "quantity": .quantity}

jq: .data[] | select(.quantity >= 3) | {key, quantity}

Using custom snippets in your editor

Since there is apparently some confusion what mason is and what it is used for, a brief explainer.

As opposed to being a plugin manager, mason is a package manager. It installs editor-agnostic tools like LSPs, linters, or formatters.

As opposed to system-level package managers like homebrew, mason is specifically integrated in nvim. Other than having an UI inside nvim, this entails features such as auto-installing packages when bootstrapping nvim on a new machine.

As opposed to language-specific package managers such as npm or pip, mason includes packages across languages. That means instead of having to install one tool with npm, one with cargo, one with pip etc., you can install all your nvim-related packages just with mason.

While a plugin manager is basically a necessity, mason is more of a nice-to-have tool for nvim. It is convenient for some people, while others prefer using their existing package managers.