Eh, your CPU can't stay eg in the high power state (post its steady state thermal envelope) for very long, but you'd still like to know how much power that consumes.
The kill-a-watt is unlikely to be fast enough. Especially if there are perhaps capacitors in your computer's power supply?
Are you interested in how much energy a certain instruction uses or are you interested in how much power your computer uses while running a certain program?
"Feeder" on Android. Built-in web is the Android web client. But I let it open the links with Firefox anyway. I just use the RSS Reader to get the list, actual reading I do in the Browser.
"Those tools and techniques should cease to be arcane nice-to-haves for nerds: we must get more non-technical people onboard" is key here, I would say.
If those tools cease to require arcance incantations and work seamlessly like every other thing everyone else is already using, then I don't think it's unrealistic at all.
That's exactly what I do, because I need the visual confirmation and can't really wrap my head around it otherwise.
Sometimes when I don't realize I'm in insert mode, I jump around the document and don't know what just happened. Visual cues in-between would have been nice, so I don't always feel as surprised as I do, lol.
Although I don't know if in that particular fiddly case it would have any benefit.
Not noticing that I'm in insert mode isn't something I can remember struggling with.
There are different solutions for it:
- Obsessively press escape so you're always in normal mode
- Style the statusline so it's very colorful when you're not in normal mode
- Have the cursor be "fat" when in normal mode and "thin" when in insert mode (isn't this the default?)
Even though I've been using Vim for 15 years or so I also enter visual mode for some commands. It's quite useful, but not necessary all the time (like di" for instance).
If you have a reasonably long `updatetime`, you could try something like `autocommand CursorHoldI * stopinsert`.
On both vim and nvim, updatetime is 4 seconds, so if you have 4 seconds of inactivity that autocommand will automatically put you back into normal mode.
