Posts tagged emacs
I enjoy forecasting, pretty much in the same way other people enjoy video games, or stamp collecting. It’s also an activity broadly in line with my values. I think the world would be a much better place if people approached predicting the future with the same level of rigor they have when explaining the past. Yet incalculably more books have been written about the past than about the future, and the fact that studying the past is more tractable than studying the future only partly explains this asymmetry. I think most people approach forecasting in what some authors call “far mode”: as an exercise whose primary purpose is not to describe reality accurately, but to signal our aspirations, or something along those lines. However, as Robin Hanson likes to say, the future is just another point in time.
A modern data scientist often has to work on multiple platforms with multiple languages. Some projects may be in R, others in Python. Or perhaps you have to work on a cluster with no gui. Or maybe you need to write papers with latex. You can do all that with Emacs and customize it to do whatever you like. I won’t lie though. The learning curve can be steep, but I think the investment is worth it.
Plumbing is a new mechanism for inter-process communication in Plan 9, specifically the passing of messages between interactive programs as part of the user interface. Although plumbing shares some properties with familiar notions such as cut and paste, it offers a more general data exchange mechanism without imposing a particular user interface. From Plumbing and other utilities by Rob Pike
Multics is no longer produced or offered for sale; Honeywell no longer even makes computers. People edit on computers on their desktop so cheap and fast that not only do redisplay algorithms no longer matter, but the whole idea of autonomous redisplay in a display editor is no longer a given (although autonomous redisplay’s illustrious child, WYSIWYG, is now the standard paradigm of the industry.). There is now no other kind of editor besides what we then called the “video editor”. Thus, all of the battles, acrimony, and invidious or arrogant comparisons in what follows are finished and done with, and to be viewed in the context of 1979 – this is a historical document about Multics and the evolution of an editor. It is part of the histories of Multics, of Emacs, and of Lisp.
It really sucks that when Bozhidar Batsov put his big talk about how shitty EmacsWiki is into action, the only thing we got out of it was another shitty wiki. It bugs the everliving hell out of me that even though engineering is supposed to be a rigorous discipline, we throw all kinds of shit at the wall to see what sticks, without ever looking at the walls in the last four or five rooms to see what the hell worked the last time.