Konrad Hinsen khinsen

The most successful malleable system in history

Malleable systems, as defined in the mission statement, were more fashionable in the past than they are now. There was a time, in the 1970s and 1980s, when malleability was a goal for influential systems designers. It was most prominently advertised by the Smalltalk design team, but it was strong as well in the Lisp community. Lisp machines, for example, were malleable systems. But Lisp machines are gone, and Smalltalk has remained a niche product to this day. Only one malleable system of the 1970s is still in wide use: Emacs. However, "wide use" is relative: it's true only in comparison to other malleable systems. On an absolute scale of software popularity, malleable systems are hardly visible. So what can we learn from the relative success of Emacs for the design of future malleable systems?

Lesson #1: Provide significant out-of-th

Markdown notes inside org-mode

The command org-babel-tangle will produce a file notes.md containing only the Markdown blocks from this file.

This is the first Markdown block:

# A section

	# To be filled by the author(s) at the time of submission
	# -------------------------------------------------------

	# Title of the article:
	# - For a successful replication, it shoudl be prefixed with "[Re]"
	# - For a failed replication, it should be prefixed with "[¬Re]"
	# - For other article types, no instruction (but please, not too long)
	title: "[Rp] Reproducing and replicating the OCamlP3l experiment"

	# List of authors with name, orcid number, email and affiliation

	(require 'org)

	(defun org-pinboard-store-link ()
	"Store a link taken from a pinboard buffer."
	(when (eq major-mode 'pinboard-mode)
	(pinboard-with-current-pin pin
	(org-store-link-props
	:type "pinboard"
	:link (alist-get 'href pin)
	:description (alist-get 'description pin)))))