phillord

Emacs-26 has threads yes. How many packages use them at the current time I do not know. With nrepl, though, most of the problems are likely to get from the interaction with an external process which has been able to happen asynchronously for a long time. So, threading (or its lack) might not be the problem.

"Text-centric computing platform" is lovely. Why don't you send that to Nicolas Petton -- it would great on the website.

Build from the source tarball, or a bootstrap build? For me, I can't get the later much below 10 minutes and often much longer.

Should be available in a day or two. If you are desperate, the RC1 is available on alpha.gnu.org

There are nice tools like "which-key" which massively reduce the work of remembering shortcuts. They are, incidentally, only shortcuts. The menus work as well.

Thank you!

I wrote a different version of the pizza ontology years ago, where the level of "spiciness" was dependent on the country you came from -- so American "hot" was equivalent to British "Medium".

It's hard to do, ontologically, but you can. It tends to make your ontology very complex though, and at the same time incapable (because it's hard to detect contradictions). So you should only do it when you need to.

Depends on the leavening agent (or not). I would argue that flat breads, yeast leavened, and sour doughs are all pretty different.

Sour dough pizza is pretty nice. Not sure it's allowed according to the book though...

It's about pizza not fruit.

This article is light-hearted of course. But there are food ontologies for real -- the BBC have one for organising their recipes. And there is another which is used for food crops, which is used for research into disease (of the crops), and helping to alleviate hunger.

It doesn't force anything though, unless you statically refer to the runtime. It does force you to exclude their logging backend, but that is straight-forward enough.

It's ugly advice. Wish there was a better alternative. Ideas on a post-card please.

My framework is built in Clojure. The interpreter is always there. Think of it like a statistics library with R.

The idea of a "main application" is itself not a clear one. There are a set of functions you can use. Whether you choose to launch directly over the library or import it is a matter of convenience.

The aliasing is just an example. The real use case involved pulling functions out of a map.

The main use of "aliasing" is to alias a namespace (to save typing) or to rename a function from one namespace where it clashes with one in local.