cool_hw

I did a quick search earlier and it seems these are informational only and not necessarily persistent warnings. Some discussion suggested that some unsupported requests to the disk can result in these, but I don't know for sure.

fzf.vim works better, in my subjective opinion, but I haven't configured telescope a lot.

Treesitter integration is a bit easier in neovim IMHO (but I haven't tried to make it work with vim too much.)

Newer plugin development seems to be much more on the nvim side than vim as well. (Although I do feel fzf is superior to telescope, at least out of the box.)

I'm happy neovim exists, it rekindled vim development.

Also, someone correct me if I'm wrong, but isn't the bus factor 1 on vim?

This is exactly the kind of comparison that prompted me to post this topic. I suppose macOS just uses the SSD far more.

How does your workload look?

Thanks.

Thanks for sharing, is this a 1TB drive?

Going by the percentage used, looks like an expected lifespan of 1200TBW.

Power On Hours seem to indicate the disk has been on for a good chunk of time, so I would think you're doing fine. Percentage used says 6%, so that seems decent too.

What model SSD is this?

I think most folks will.

What is your RAM/SSD config?

This is why I asked here. Most folks don't seem to mind it, but it is an order of magnitude, if not more, higher disk usage than linux.

Is there a noticeable difference in battery life usage with option 1?

I think that's because `power on` hours is talking about the disk being in the power on state, not the rest of the machine.

Wow, that's a well used machine!