My favorite is nvim-treesitter-textobjects which gives you dozens of new targets for vim motions, such as a function call or the condition of a loop.

Firefox-based browsers do not support macOS automation (AppleScript/JXA). Safari lacks features/extensions. Orion/Vivaldi had bugs any time I tried them.

From the Chrimium-based browsers I tried, Brave blocks ads, supports PWAs, the crypto stuff can be turned off, and is stable. Brave does not excite me, but it's good enough.

As someone who uses the "I'm feeling lucky" regularly, this is definitely an improvement.

Don't aim to be rich, but try to have enough.

Sadly, filtering features seem to be only available for paid subscriptions of online services, or for self-hosted solutions. Or are there solutions I am not aware of?

Upon some digging, it seems that part of the slowdown is due to the gpt-5 models by default doing some reasoning (reasoning effort "medium"), even for the nano or mini model. Setting the reasoning effort to "minimal" improves the speed a lot.

However, to be able to set the reasoning effort you have to switch to the new Response API, which wasn't a lot of work, but more than just changing a URL.

I already have zsh-magic-dashboard running on empty enter.

If low-tech counts: Contacts. They are just so much hassle compared to glasses, the imagined better looks are not worth it.

Read-later services. Just another pile of things to manage. If I really need to read something, I add it to my todo app.

A linter what the reasoning for all rules is well explained, similar to shellcheck or eslint.

Both ideally integrated in an LSP, which also has all the common features of a modern LSP.

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

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

> "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.

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).

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).