most of the users of those third party harnesses care just as much about hitting cache and getting more usage.

know when to cut your losses and try something different.

can somebody provide a reference explaining/demonstrating the ergonomics of ORC/ARC and in particular .cyclic? This is with a view toward imagining how developers who have never written anything in a non-garbage-collected language would adapt to Nimony.

I like everything about it except for the thumb cluster. it is, amazingly, worse than the Ergodox EZ.

I wish the author would spring for a wireless Dygma Defy and tell us how that thumb cluster compares :)

In my experience, this post is often right (and the logs are often wrong). There's a tendency to either log too much or log too little - if only a few items are getting processed, it's fine and maybe even good to log all 7 of them.

But if many, many are getting processed - you'll experience semantic overload as a reader of the logs. What you want is a compressed form

Logging per time interval can be a very handy approach. In my work, we've settled on a hybrid approach - calculate in real time how often things are happening and then log the number of things that have happened, but at a rate that is roughly one log every N seconds.

This takes some more engineering up front but is remarkably often what a log reader actually wants.

the core idea here is really cool, and the UX is (or seems like it would be) impressive - no need to select a language, for instance.

Good luck getting it back on its feet!