14 ms·
Emacs users are like Terry Pratchett’s Igors
- FatalBaboon 13y agoEmacs is one of those things everybody knows is good, but few take the time to learn. Over the years I've learnt quite a few languages, and what strikes me is that they're all so very alike. You find the same features with slight syntactic changes. At the end of the day, what really makes a difference is not which language you chose but what tools you are using. Do you have to memorize every important method or are they helping you find the documentation? What happens when something is a little broken, wait for a fix or patch the code immediately? Give up and live with it? With Emacs, the languages change but the tool stays the same, you just extend it. In a way akin to how programming enhances my mind to be able to solve tough problems, emacs enhances my capacity to hack by letting me hack the tool itself. Having a userbase made of people hardcore enough to learn some Lisp so they can hack their tool is just a bonus. Please keep fearing the parens! Emacs is still being actively developed, v24.4 is in feature freeze: https://github.com/mirrors/emacs/blob/master/etc/NEWS https://github.com/mirrors/emacs/blob/master/etc/NEWS (that's 1200+ lines of changelog for 24.4) How many pieces of software can you name that have been around for 36 years and are still kicking? Do you think it has something to do with Lisp?
- SkyMarshal 13y agoWith Emacs, the languages change but the tool stays the same, you just extend it. In a way akin to how programming enhances my mind to be able to solve tough problems, emacs enhances my capacity to hack by letting me hack the tool itself. Oblig reference to classic essay on that topic: http://www.osteele.com/posts/2004/11/ides http://www.osteele.com/posts/2004/11/ides
- nabla9 13y agoLearning something that takes time should be seen as investment. If you invest your time and effort, you want to know that your investment pays dividends in the future. I feel that Emacs is one of those tools where my investment is safe and the code I write to ~/.emacs produces huge value over several decades. It's not going away. Development community is so big that it supports all new stuff that comes along.
- actsasbuffoon 13y ago> Over the years I've learnt quite a few languages, and what strikes me is that they're all so very alike. I used to think this as well, then I learned some Prolog. For those who aren't familiar with it, Prolog is a logic programming language (as opposed to imperative and functional languages). Instead of telling Prolog how to solve a problem, you give it a set of facts and tell it what you want to know. Prolog takes care of the rest, without writing any conditionals, loops, etc. At least in theory; in my (small amount of) experience most non-trivial Prolog programs usually involve some imperative style code. Still, it's wildly different and a lot of fun. There's also lambda calculus, which is crazy, and wonderful, and absurdly difficult, and one of the most joyous experiences I've ever had. It's a language with nothing but functions applied to other functions. Even numbers are functions in lambda calculus, which has some fascinating implications. I wouldn't want to build anything non-trivial in LC, but I've learned a lot about programming as a result of studying it. Discovering how to create singly linked lists in LC using nothing but partially applied functions was a profound and emotional experience. I remember how hard I laughed when I noticed that LC's false function is the same as the Church-encoded numeral for zero. These are things most other developers don't think are funny because they have no idea what I'm talking about. I think a few of my co-workers suspect I should be institutionalized when I start talking about lambda calculus. Of course, there's also Haskell. A lot of lambda calculus is applicable to Haskell, which makes sense as Haskell descends from the ML family of languages, which in turn come from lambda calculus. Haskell doesn't look or feel like most other languages, and it makes some decisions that seem really strange at first glance. Lazy evaluation, all functions are curried, no mutable state, all functions are pure, there are no variables, no exception handling... the language sounds almost unusable. Then you learn about monads and you realize that it's trivial to add support for something that looks and feels like mutable state, except it's a system of your own design. Imagine what would happen if you could change the way variable assignment works in your language of choice. For instance, software transactional memory was originally implemented in Haskell as a monad. They didn't have to modify the language to add support. I can't think of many other languages where that's the case, and it's a thing of beauty. That's a long and rambling way to say that lots of languages are really similar, but there are some wonderful languages that are extremely different. I highly recommend experimenting with them, but be aware that your friends and co-workers are unlikely to have any idea what you're talking about. And on the off chance that they do understand, please let me know where you work. I want to work with you people.
- agumonkey 13y agoTwo thing that I found lacking for less-than-good hackers like me : - idiomatic (minor|major) mode organization (I found a book and a pdf which are old and might not represent the best way to do so) - at emacs conf, jwiegley showed some old and tiny extensions (edebug, redshank) part of his workflow. Very interesting to discover dark corners of the large emacs extensions space and how people solve problems their way.
- seivan 13y agoHmm, I am probably missing something, but isn't Igor from Mary Shelley (Frankensteins assistant)?
- Udo 13y agoFrom the article: "This really reminds me of Terry Pratchett’s Igor clan. I discovered this amiable race in The Fifth Elephant. Igors are a people inspired from the typical hunchbacked Igor archetype, but in Discworld, they are also self-modifiers. Their bodies consist of mixed and matched and patched and swapped body parts among other members of their clan, of scars and self-adjustements. They are infinitely self-improving, self-experimenting. They might end up with a botched job and have to hobble around for a few days, but in the end it’s always fixable. And they lisp."
- ColinWright 13y agoYes, you're missing something. You need to read some Terry Pratchett. There are several entry points to the canon, some better suited than others to different readers. The Igors first arrive in The Fifth Elephat, or possibly Thief Of Time. As an entry point (but without the Igors (yet)) I recommend "Guards! Guards!", YMMV.
- rbobby 13y agoSmall Gods is also a fun place to start.
- InclinedPlane 13y ago"Igor" as Dr. Frankenstein's assistant achieved prominence through Bela Lugosi's portrayal of the character "Ygor" in the film "The Ghost of Frankenstein". (No character named "Igor" appears in Mary Shelley's novel "Frankenstein: or the Modern Prometheus".) "Igors" are a community of folks within the fictional "Discworld" universe created by author Terry Pratchet. Dr. Frankenstein's assistant is merely a lab assistant. Igors on Discworld are folks who remake themselves by way of transplants, as described in the article.
- masklinn 13y ago
- etfb 13y agoI'm a recovering Emacser, happy enough with less powerful but more modern text editors. It wasn't the program or the UI that finally did me in, but the community: I had a problem with how Emacs worked, I wanted to figure out a solution, so I asked on #emacs on Freenode and got nothing but abuse. I realised there's something about Emacs that attracts the sort of users I don't want to associate with: people who are smug, self-absorbed and utterly without empathy. Did I want to be one of them? No, I did not. Did I want to have to rely on them for help in my work and play? No, I did not. So I found a text editor that has sufficient extensibility and I installed that, and uninstalled all the emacsen on all my machines. And I felt a lot better afterward.
- FatalBaboon 13y agoThey probably tried to make a common point: do not give the solution. For a given specific issue, the most you should give is pointers. For the function that solves your problem saves the day but knowing how to find any when needed solves a lifetime of problems. Pointers help to put you on the right track so you're not discouraged.
- etfb 13y agoI was asking all the right questions -- is this possible, what hooks should I consider, what should I take into account to make sure that the stuff I add doesn't stamp all over other stuff. I'm a programmer with thirty years experience and twenty years with Emacs; I know this stuff. Basically, they shut me down. The thing I was asking was contrary to the whole philosophy of Emacs. I had, they assured me, no right to ask it. I was an idiot for having the problem that I was seeking to solve. And nobody, they told me, had ever had the problem ever in all of history. Were they right? Well, no, not even slightly. They were horribly, evilly wrong. But even if they had been right, their response was wrong. Their argument was "if you have this problem that can be fixed by a change to Emacs, change yourself". This, in the most extensible editor on the planet. It was like being told that my car's tendency to pull sharply to the left when passing another car was normal and expected and I should take care not to pass other cars.
- stiff 13y agoIn common understanding of emacs, its use of lisp recieves perhaps too much attention, while its overall wonderful architecture is underappreciated. Emacs isnt just an editor with embedded lisp, its more a vm for bootstrapping editors. You could do an emacs with python, but the hard part is providing an environment where the extensions dont interfere with the user input loop, with buffer redisplay etc., while still staying easy to write. The emacs buffer-based async handling of external processes is a masterpiece of software engineering, much better than things like unix pipes. Doing extension languages for interactive programs is much harder than it seems at first, and emacs is a prime example of doing it right.
- leephillips 13y ago"The emacs buffer-based async handling of external processes is a masterpiece of software engineering, much better than things like unix pipes." This sounds intriguing. Do you have a pointer to something I could read that might expand on what you're saying here? (Aside from the emacs source.) Amusing coincidence: the only Pratchet book I've read is The Fifth Elephant.
- mr_luc 13y agoSeconded! Like a lot of Emacs users, sure, I love Lisp. But I don't really understand how it's architected. Sure, I understand that there is this abstraction of a Buffer. But it's quite abstract. I'd love to know what's happening under the hood. I think a blog post that even gave a 37signals-blog-post-sized expansion of the grandparent's comment would probably be frontpaged on HN.
- thirdtruck 13y agoJust wanted to recommend reading more Pratchett. :) I bought a couple more novels last week and couldn't help but finish one (Equal Rites) less than twenty four hours later.
- terhechte 13y agoI've read more than 20 Pratchett books (I think I didn't read the last 2-3) and there're two absolutely great books among them: - Nightwatch: Great idea, fantastically written - Going Postal: Great book for everybody who reads HN. Great characters, storyline, and fantasy meets hacking.
- bachback 13y agobeautiful post. the learning curve for getting into elisp land is steep. we need something like emacs in the future, something to evolve the emacs model as the self-evolutionary programmer's environment. the 1M LOC code is much too bloated for the modern age. it should be more tightly integrated with bash/linux/git, and have better exploration methods. i am not sure why nobody is working on this, besides lighttable. perhaps that is the problem with emacs/lisp. finding the valuable stuff out there takes time and is not build around sharing.
- progman 13y ago> the 1M LOC code is much too bloated for the modern age. Why reinvent the wheel? Emacs works well enough, and computers are getting faster every generation. Many editors appeared, they all had the chance to make Emacs obsolete but they ALL failed. Every editor could challenge Emacs but obviously it is not so easy to compete. I use Emacs for decades now because of its extreme stability (almost same version among many operationg systems) and extreme reliability (not a single crash ever). I have tested new editors from time to time but Emacs is still superior. These are some raasons why Emacs is still alive today despite its ancient source code. Another reason is that Emacs depends on Lisp which is much more stable than modern standards like Python, Javascript and HTML5 which change pretty fast and make it difficult to keep big software up to date. For instance, imagine an Emacs like editor written in Python 2. Now the codebase would have to be changed to Python 3, and possibly soon to Python 4. By the way, Haskell provides excellent support for DSLs. So it should be no problem to develop a tool which converts Haskell plugins (or Python or whatever) to Emacs elisp.
- chrisdone 13y ago> By the way, Haskell provides excellent support for DSLs. So it should be no problem to develop a tool which converts Haskell plugins (or Python or whatever) to Emacs elisp. I've been thinking about adding Haskell as an additional language for Emacs alongside Elisp. It would be nice to be able to use both.
- dbalan 13y agoone thing I struggle with emacs is that I can't find a place which documents the emacs way of doing things. Emacs has multitude of features, there are just too many to master, yet even to know that they exist. One example would be rectangle select http://www.gnu.org/software/emacs/manual/html_node/emacs/Rectangles.html http://www.gnu.org/software/emacs/manual/html_node/emacs/Rec..., I absolutely love them - but till one of colleague introduced them to me, I had no idea they existed.
- wglb 13y agoI often go to http://www.emacswiki.org/ http://www.emacswiki.org/.
- mickeyp 13y agoI try to write long articles explaining Emacs workflow over at http://www.masteringemacs.org http://www.masteringemacs.org. You may be interested in my latest post on discover.el.
- ttuominen 13y agoI've found emacs-fu useful. http://emacs-fu.blogspot.fi/ http://emacs-fu.blogspot.fi/
- mathattack 13y agoPerhaps I'm nerdly enough to go to the Terry Pratchett part of the story first. This really reminds me of Terry Pratchett’s Igor clan. I discovered this amiable race in The Fifth Elephant. Igors are a people inspired from the typical hunchbacked Igor archetype, but in Discworld, they are also self-modifiers. Their bodies consist of mixed and matched and patched and swapped body parts among other members of their clan, of scars and self-adjustements. They are infinitely self-improving, self-experimenting. They might end up with a botched job and have to hobble around for a few days, but in the end it’s always fixable. And they lisp. Pratchett litters his books with lots of unexpected gems - I view it like Easter Eggs for books. Could he have possibly added the lisp on purpose???
- aetherson 13y agoI'll take issue with this claim: "Work environments are a very personal thing. They exist to serve only one person: you. Me-me-me is a winning attitude when dealing with your environment." I think it's considerably more important to have a (basically good) work environment in which your colleagues can sit down and use fluently than to have one that's absolutely optimized to your individual tastes.
- wting 13y agoDo you share workstations with your co-workers or do significant amounts of pair programming? I'm not sure why my work environment should be optimized for a <1% use case.
- aetherson 13y agoI do significant amounts of pair programming. But even more so, I don't think that your coworkers using your workstation should be a <1% use case even if you never pair. My contention is that: 1. Work environments -- including ones that don't formally pair -- should be highly collaborative. 2. It's typically massively less efficient to help someone past a block or communicate a new coding technique via telling them what to do rather than doing it. Much less anything even remotely iterative, where you need to, say, write some code, look at some output, and write some more code. 3. The difference between "a basically good development environment" and "a development environment that is specifically optimized for just specifically you" is actually quite small. There's no real need to sacrifice much of anything in order to get an environment optimized specifically for you.
- wting 13y agoDo you share workstations with your co-workers or do significant amounts of pair programming? I'm not sure why my work environment should be optimized for a <1% use case.
- JackMorgan 13y agoIf you pair a majority of the time, sure, make a standardized workstation with your team. My team uses viemu in VS, which the rest of our office detests, but hey, we are the ones pairing 99% of the time. When I am not pairing for the majority, I setup my machine to my tastes, and simply install a "default" editor for the few times someone else actually needs to type on my machine. Emacs and IDEA both have good ways to revert everything to defaults temporarily. I do not believe, however, that a perfectly customized setup has only small gains. For example, consider two tools that I have never seen as defaults in any editor or IDE: rainbow parens/brackets and paredit mode. Rainbow parens just highlights pairs: http://stevelosh.com/media/images/blog/2010/09/rainbow.png http://stevelosh.com/media/images/blog/2010/09/rainbow.png And here is a short minute paredit mode explanation: http://www.youtube.com/watch?v=D6h5dFyyUX0 http://www.youtube.com/watch?v=D6h5dFyyUX0 When actually editing code, those two tools save me several hundred keystrokes an hour. And those are just the first two tools I thought to use as an example out of the entire toolbox that is emacs. If I was to now give up just those two tools, I would be sentencing myself to the mental equivalent of tying five pound weights to my legs for the marathon that is the rest of my programming career. Why would I intentionally require myself to type more keys per hour to do the same editing, rather than just learning a faster way to edit? This is, obviously, also my argument for learning the vim editing system (which I also use in emacs).