Hacker Newsnew | past | comments | ask | show | jobs | submit | phillord's commentslogin

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.


My desktop is a Ryzen 1700, 8 cores, 16 threads. So I run "make -j16". =D

    $ make -j16
    make -j16  156,14s user 9,37s system 714% cpu 23,166 total


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.


That's a great tool. Thanks.


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.


Knowledge is knowing that a tomato is a fruit, wisdom is not putting it in a fruit salad.


Then again, there is nothing wrong with putting tomatoes in a fruit salad, or a mixed vegetables/fruits salad, which is delicious.


Alternatively, understanding is recognizing that a tomato is actually a berry; mastery is not trying to make a tomato shortcake.


In which category would we place the needless repetition of trite sayings?


Tomato is a fruit!

Or is it? I may need a Clojure-based epistemology to decide.


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.


Yes, but you have to know to exclude their backend. And, that library may be several dependencies deep. Now you're expecting potentially junior developers to have the insight to grep their entire transitive dependency tree, find the nop dep, and exclude it. This kind of silent failure is worse than the alternative.


Dependency exclusions is a code smell everywhere but java. I don't understand why someone is actively giving this advice.


The alternative is not specifying a nop dependencies and then inflicting on downstream uses the choice that I was not prepared to make.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: