1,061 karma · joined April 11, 2019
0. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2359769/ 1. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3210420/
The longer I have been working to develop processes and systems, the more I have come to appreciate defaults that do not change. It is interesting to see some of the new *coin and blockchain folks in their dark forest threads worrying about what happens if the interpreter changes its semantics and lamenting that contracts are meaningless if the interpreter can change. That is what standards are for, and that is what the "backwards geezers" are trying to do for Emacs since it doesn't have a standard, only social norms. I'm not too too worried though, since there are many sensible people in the community who understand why changing defaults can destroy trust and waste the time of millions of people. I am also not worried because there are many creative solutions to the problem of how to attract and maintain new users in a way that they can come to appreciate the benefits of stability.
1. https://lists.gnu.org/archive/html/emacs-devel/2020-09/msg00...
edit: Looking at the git history is very educational for how to bootstrap a self hosting system like this. Fascinating.
Another observation that I have had on this is that trying to convince philosophers that morality can be reduced to a decision problem and thus that Kant is not wrong, rather that he is just an asshole who didn't know that Turing complete systems exist, is a very hard thing to do. Their reaction against the dangers of belief in the categorical imperative is extremely well founded, and instructive for those who think that things like smart contracts might be a good idea.
One great advantage of defining traditional morality as being closely equivalent to the evolutionary imperatives of our biological substrate is that we can stop playing the stupid post-hoc rationalization game where we try to come up with rational explanations for what is fundamentally contingent behavior. This in turn provides us with an entirely clear space to start to imagine what post-moral society might look like, and envision what algorithmic morality might look like if we were actually able to feed Bentham's machine with all the factors instead of the stupidly limited number of measurements and dimensions that are usually imagined and that remain centuries out of date with the current state of the art in logic and computation.
Whether we want to live in a society where we have agreed that everything can be decided upon must be reducible to a decision problem, or whether we want to allow ourselves the get out of jail free card that is denying that we know enough to make the decision at all is another question. However, before we can even get there we need to be freed from the misbegotten idea that morality is in any way universal, or derived from natural law, or that natural law even exists. Out of an incredible body of work I will always thank Patricia for taking this head on.
I should also note that the argument that morality is rooted in biology is in no way mean to belittle what evolution has discovered. Patricia has argued that many of the positions taken by modern defenders of enlightenment ideals wildly undervalue so called traditional or local knowledge as "unenlightened" because that knowledge was not arrived at from first principles, but from long, hard experience accumulated and passed down over generations, and that westerns in particular have an abysmal track record when it comes to thinking they know better and thus not listening to the people who know that the reason why the crops are not planted by the river is because the hippos will come out and try to kill you if you do.
0. https://github.com/tgbugs/tgbugs-overlay/blob/master/dev-jav... 1. https://github.com/clj-commons/pomegranate
I think part of the above comment is expressing frustration about the fact that part of the reason for the lack of wide portability of these programs is precisely because people say "oh they can't do x" or "this is operating system specific" and taking it as axiomatic rather than realizing that with a bit of engineering time and effort they can be extended to work on other systems. This especially since there is pretty much no language that is used entirely by itself without dependencies on another at some point in time. If your language has a ffi, then you need a real package manager to accompany it.
When I started to use org-mode it was because I needed to generate a gant chart and I wanted a text format. I haven't used that functionality every again. Since then I have used org-mode for a variety of things, but never all at once, always a little piece at a time. Typeset a thesis in latex? Execute analysis code in a reproducible way? Write DRY bash scripts and tangle (compile) them? Run and log the output of one-off commands on remote servers so that if you ever have to do it again you have a record of it? The list goes on and on.
Last week I was told that I needed to start keeping track of the time I spend working on different tasks. Despite keeping todo lists I have never used the org clocking functions, ye there they were there, just a C-c C-x C-i and C-c C-x C-o away. Integrated into my workflow when I needed it with all of 30 seconds of effort and two key combinations of overhead.
Emacs is useful because countless others have encountered problems the likes of which a single person only rarely dreams. Not only that but they have probably already implemented a solution that is fairly easy to find once you encounter the problem and in 80% of the cases can be used unmodified.
Yes, you and all the rest of us are missing something. It is impossible NOT to miss something and no tool can solve that for you. The question to me is whether you want to spend your time learning a tool and integrating with an ecosystem where you never have the possibility of benefiting from the things that others did not miss.
Hypothes.is is great for prototyping curation workflows to explore what is possible before spending time implementing yet another tool. It also hits the sweet spot for having a UI that is just accessible enough for non-technical users that can display annotations made by bots. We have been using hypothes.is as the backend to crawl [0] research resource identifiers from the scientific literature for 4 years, and it has been solid the whole time.
I see some questions/concerns about the w3c compliance of the API. I'm pretty sure that there is just a switch the needs to be flipped, and that it has been implemented. Yep, it has [1]. Also as others have suggested it is fairly straight forward to set up your own annotation store, though it is not simple to replicate the Hypothes.is setup.
I hope that the pivot to education continues to go well so that it can fund the infrastructure, because Hypothes.is provides a very valuable (if hard to capture the value of) service.
0. https://github.com/SciCrunch/scibot 1. https://github.com/hypothesis/h/blob/master/h/presenters/ann...
1. https://www.hpi.uni-potsdam.de/hirschfeld/publications/media...
Rearrangement of the contents of virtual desktops and the desktops themselves is a topic in and of itself. The emacs world has a lot of tooling around this as well (see for example [0]), and the are a number of patterns/workflows for managing/composing/recombining workspaces that would surely translate other window managers since they deal with essentially the same issues.
For me the issue tends to be that it is easier and faster to create a new window of whatever kind wherever I am to answer the immediate need than to find the right one to answer it in, so I just open a new terminal window, jump to where I need to be, do what I need to do, and then ... forget to close it. Similar issue with dragging a browser window around with me wherever I go. One answer to this might be to slightly modify the behavior of the "open new instance of this program" key to act instead as "jump to most recent instance of this program, or if it does not exist, create it and jump to it."
One thing related to gc is that I started to work on but did not manage to complete, was the ability to snapshot the layout of all windows across all desktops in an x session. That would allow effective patterns to persist across restarts without the need to come up with a way to specify how things should be arranged. It would allow them to be arranged by whatever means, saved, and restored. I'll probably get back to it at some point.
As a note, anyone with the inclination can do this kind of thing in any language as long as it has xlib bindings.
I have also thought about trying to decouple how spaces are associated per monitor, but couldn't figure out a way to interact with such a system that wouldn't leave my brain lost somewhere in even higher dimensional virtual spaces than it already is!
0. https://www.gnu.org/software/tramp/ 1. https://www.emacswiki.org/emacs/TrampMode
From an engineering perspective this is a excellent example of a direct path from interpreted to compiled code. The trade-offs are clear (heck, they are number 0-3), and while there is complexity, all the engineering time has been effectively concentrated inside a single project, rather than forced upon tens of thousands of maintainers and users. Bravo. I wonder what other bytecode interpreters could benefit from this toolchain. Compile times from qlop.
On a Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Without comp `2020-05-03T15:33:27 >>> app-editors/emacs: 6′40″` With compile `2020-05-03T18:35:43 >>> app-editors/emacs: 2:11:45`
0. https://github.com/tgbugs/tgbugs-overlay/blob/master/app-edi...
0. https://gitweb.gentoo.org/repo/proj/prefix.git/plain/scripts...
I realize that Gentoo became a meme at some point, but it also seems that it might have transcended to the level of infrastructure. Thus, you rarely ever heard about it for the same reason you don't hear people talk about hammers -- it is doing its job running tens (hundreds?) of millions of chrome books among other things.
No flare, nothing fancy, it has solved a whole bunch of packaging, deployment, and environment control problems and gotten out of the way of its users (mostly ... chuckle), and it did it all with a pile of bash scripts and a little python here and there. Want to use systemd because you have a use case that would benefit from it? Go right ahead! The engineering work is done, no need for fights on the mailing list. Don't want to use systemd? `eudev` to the rescue! There are sound engineering reasons for not using systemd while also wanting to use some other (seemingly) completely unrelated piece of software that just happens to have a dependency on the kitchen sink.
Despite being a rolling release distribution, I find that the UX and workflows are more stable over long periods of time than any of the more popular LTS style distros. When I started fiddling with Ubuntu so that I could help my colleagues debug issues it took me an embarrassingly long time to realize that there isn't really such a thing as Ubuntu, just 14.04, 16.04, 18.04, etc. Each is some different form the other that stack overflow questions from one LTS are often simply wrong for another.
Writing this I wonder whether rolling release distros aren't effectively the original form of chaos engineering -- if everything is going to be changing all the time then it forces the developers to solve a different and perhaps more fundamental set of problems and ultimately leads to greater stability in the long run.