tangentstorm

Yeah, the same idea works for any language, and the software I wrote for it is language-neutral. I just happen to have a history of making J videos. (I haven't actually used the software in a video yet... I was just saying the videos tend to follow that similar narrative structure.)

Not even remotely. it's just plain vanilla C, with dense formatting. Whitney makes extensive use of macros to completely change the language.

Yes to pretty much all of the above. It's an extremely terse array programming language in the APL family, but with ASCII primitives and strong distributed programming / IPC support. There are also at least a couple companies that still use K3 (I work at one), and no official support from the author (who went on to make other versions of K that are also awesome but completely different).

IMHO the biggest thing holding K back is lack of a production-ready / batteries included open source implementation. (There are a couple nice open source implementations of K but none of them are as feature complete as this one... Plus this one has at least a start on interoperating with .NET)

You have unlocked: Irony!!

This seems like an awful lot of worrying about a problem that doesn't actually exist.

Yes but in whatever language you're imagining here, a "list" probably isn't the kind of list that lisp uses (linked lists of cons cells).

> Even though you aren’t writing the 3P code yourself, by including it in your project you are committed to understanding it—and refreshing that understanding if you want to upgrade it.

This is a nice thought, but I suspect hardly anyone who uses a framework or library really understands it, or makes the commitment to try.

Obviously, a subset of really talented users eventually learn to understand the framework, but most are at its mercy.

Even then, you can't study every possible framework before choosing one to master - there are too many, and the cost of understanding the foreign code is simply too high.

So I suspect that in general, people try frameworks by taking a leap of faith, and then, sometimes, make the effort to actually understand it later - if and when it becomes necessary.

Is this something you can actually configure on modern processors, or is it more hypothetical advice for future chip makers?