michael-ax

plug in an un-wired connector, cut of the wiring post, smooth with a nail-file or put on a crowning drop of glue so it won't rip your bag and you're done.

e.g. "maximising sum(log(utility))" like the comment on the article said. the only thing strange here is that philosophy deals with qualitative, not just quantitative domains. thus they tell these stories. :)

using it to prioritize your relations forces you to grapple with subjective and irrational things such as personal prefs, aspirations etc. so.. also rational and humanizing.

this leaves using it to mess with others without them participating in weight-setting (democracy as a weight discovery mechanism?), that's where it gets messy.

i fail to see where any of the three facets above make it humiliating to see where 'by priority' the most relative improvement can be made. i mean, this is all just fine talk about something innate to nature, no?

also, there's zile.

consider putting a photo of your keyboard next to your screen and painting the keyboard a nice uniform black.

your body-mind's intelligence will swiftly learn to position your hands and coordinate your/its fingers without adding things to unlearn later.

the photo of your keyboard near where you are focusing when looking at the screen makes a huge difference, one could start with just that.

we applied rle encoding for time-series and triac control systems 43 years ago after getting some guidance from a mainframe guy - but since RLE is practical so that we even use it to give direction to people on the street, its probably so old that its even found its way into the way our genes are encoded. :D

but also ask "why are the tables of content prefixing the contents of all my books?"

its taken ages, but with this model, c lib authoring has finally taken something that was a core strength of pascal: single-file modularity.

though in theory there's no difference between theory and practice, in practice, there is. and this kind of packaging makes a lot of sense for a lib like this.

https://www.scientificamerican.com/article/the-good-kind-of-...

https://owlcation.com/stem/What-is-the-Mass-Effect-Gravity-A...

https://owlcation.com/stem/What-is-the-Mass-Effect-Gravity-A...

edited to add video and sciAm paywall links:

https://www.youtube.com/watch?v=_INqXPFdJM8

https://www.scientificamerican.com/article/the-good-kind-of-...

still i wonder if this thing couldn't embed itself into a bash-process and serve tui frames with a scriptable curses api so that you could, for ex, have some tabs and buttons and graphs on a system status app

it could bring inversion of control to node and any kind repl .. so that instead of away from a term-info and term-cap standard, one would move toward curses as an acessible tui/gui metaphor, or at least toward something that makes sense without constant apologies for the past.

maybe i'm not using the right words, but it seems to me that hacking this up so it can be stuck into bash so that its api appears like any other language extension would make notcurses a highly desirable dependency for just about any project!

if passwords also covered account scopes -- which is what this tool enables one to monkey-patch into the OS, i could give you my password so you could gorge on my code without me having to worry about you reading my journals or abusing ~/.ssh

other than that, i second your notion.

I'm thrilled by the idea of using passwords to switch between the sorts of things i do without having to log-out.

Server-side maintenance/generation of .zsyncs might be transformative wherever replication is desirable, no?

summary: this is a nice cow/cloning wrapper for use on a single ssd partition!

-- but cloning not copying between volumes or partitions is .. and when you actually want to copy with fcp, it can be very slow as detailed in other comments.

. . # exit when sourcing [ "$0" == "${BASH_SOURCE[0]}" ] || return 0

echo "Tests for [$0]" . .

this way you'll wind up able to load/source globs of reusable self testing code into the global namespace with ease.

add a [ -n "$1" ] && { undef and exit } block at the top of the file where you document the names you're using as you would in a header.c and packaging your code for reuse becomes easy.

at last count i have 19 such modules in /ops/bash. they are immensely useful to help me remember this atrocious language :)

running in-browser is not the same as installing their electron client.