Earlier quoted context omitted.
Programs are so absurd to most people... they have to use rote learning to do anything with it (that's why changing the slightest bit will drive them mad). And most programs are full of hidden state. This is everything a programmer despise, we spend a huge amount of time ensuring our paradigms are principled and transparent, but these qualities rarely make it to the user level. So I cannot but sympathize with normal…
Oh I don't just mean programming; I've run into perfectly intelligent people who nonetheless respond to even the most basic computing tasks as if you've asked them to insert their tenderparts into a badger's den. Now, I'm perfectly willing to accept that some people just won't "get" computers, but I've also seen elderly retirees who took to it like a fish to water once you talked them out of being afraid of the thing…
My Lisp Experiences and the Development of GNU Emacs (2002)
31–40 of 41 posts
Re: My Lisp Experiences and the Development of GNU Emacs (2002)
#32Earlier quoted context omitted.
Ousterhout did some marketing pieces and he stated a lot of random things. http://www.tcl.tk/doc/scripting.html There was some controversy around it at the time...
I didn't realize that was a very controversial paper. If the timelines are correct though, that wouldn't have been offending rms yet: > rms: That was not the end of the GNU projects involved with Lisp. Later on around 1995, we were looking into starting a graphical desktop project. [...] > > At the time, TCL was being pushed heavily for this purpose. I had a very low opinion of TCL... -- JOs paper appears to be publi…
Re: My Lisp Experiences and the Development of GNU Emacs (2002)
#33Earlier quoted context omitted.
> My girlfriend couldn't understand why I was reading a kids book as it had an elephant on the front Thought you were going to say it was Learn You a Haskell For Great Good.
I'm actually reading that one right now. It's quite good, and has made a Haskell fan out of me already despite getting a bit fatigued by chapter 8.
Re: My Lisp Experiences and the Development of GNU Emacs (2002)
#34"There's an interesting benefit you can get from using such a powerful language as a version of Lisp as your primary extensibility language. You can implement other languages by translating them into your primary language." This is so short-sighted hand-waving; it doesn't take into account the existing ecosystem (libraries, tools, etc.) at all. Unlike lisps and schemes, TCL is way less fragmented and has a bunch of l…
I keep returning to the "I'd like an embedded scripting language in my C environment" year after year, and there is nothing that has made me pull the trigger yet. TCL is a non-starter for me; LUA is dubious; GUILE is a non-starter with GPL licenseing. Java is clunky and heavyweight, but maybe plausible, though it's more common to JNI C into your Java main. I think it'd be nice to have an embeddable Javascript like v8 that can attach to C underpinnings, but don't know if there is one. Maybe duktape?
Re: My Lisp Experiences and the Development of GNU Emacs (2002)
#35Earlier quoted context omitted.
> My girlfriend couldn't understand why I was reading a kids book as it had an elephant on the front Thought you were going to say it was Learn You a Haskell For Great Good.
I'm actually reading that one right now. It's quite good, and has made a Haskell fan out of me already despite getting a bit fatigued by chapter 8.
Re: My Lisp Experiences and the Development of GNU Emacs (2002)
#36I think it's interesting how he never explicitly says that he forked Gosling Emacs (I think that's what he did, but if not please correct me!). "Therefore, when I wrote my second implementation of Emacs, I followed the same kind of design...Now, this [GNU Emacs] was not the first Emacs that was written in C and ran on Unix. The first was written by James Gosling, ... I discovered that Gosling's Emacs did not have a r…
Yes, he did. At that time or a bit later I worked for UniPress; the owners knew that taking any action about that beyond a polite request would untimely be harmful. But it was seriously reckless of RMS to put his GNU effort in jeopardy.
We all had a good laugh. RMS is a funny guy and quick of his feet!
Re: My Lisp Experiences and the Development of GNU Emacs (2002)
#37I wish I could work on an OS written in Lisp, or in an equivalently expressive language. It's so damn important to have a really user-friendly system easily customizable by non-programmers. Actually, programmers should be routinely put out of their jobs, essentially the same way programmers put others out of theirs. :-)
Re: My Lisp Experiences and the Development of GNU Emacs (2002)
#38"There's an interesting benefit you can get from using such a powerful language as a version of Lisp as your primary extensibility language. You can implement other languages by translating them into your primary language." This is so short-sighted hand-waving; it doesn't take into account the existing ecosystem (libraries, tools, etc.) at all. Unlike lisps and schemes, TCL is way less fragmented and has a bunch of l…
Re: My Lisp Experiences and the Development of GNU Emacs (2002)
#39"They used a manual someone had written which showed how to extend Emacs, but didn't say it was a programming. So the secretaries, who believed they couldn't do programming, weren't scared off." That bit really jumped out at me, because it's something I've felt about computers in general for a long time. People get it into their heads that computers are hard/complicated/etc., and so they get scared of them, and so th…
Some people are excited about programming in the sense that they can "make the computer do stuff". But the way I see it, I make the computer "do stuff" by just simply pressing the power-on button. And writing a "hello world" doesn't make the computer accomplish more than to write the same string in a word processor. Maybe some people should just be reminded that programming is not fundamentally different from using a…
A non-programmer, I'm sure making it a welcome checkpoint at a programming language is an incredibly stupid tradition. It should always be an one-liner that does something no app in the world can do, with clearly identified spots that a newcomer can tweak for their individual needs.
Re: My Lisp Experiences and the Development of GNU Emacs (2002)
#40Earlier quoted context omitted.
I'm actually reading that one right now. It's quite good, and has made a Haskell fan out of me already despite getting a bit fatigued by chapter 8.
Finished chapter 8 yesterday in the middle of a 40C fever. Checked the page number only to realize I wasn't even halfway through...