Archive for the ‘software’ Category
See Part Five
I made a number of Google searches of the forms below and summed the results (previous posts averaged the results):
"implemented in <language>" "written in <language>"
Naturally this is of very limited utility, and the numbers are only useful when comparing relatively within the same search since the number of results Google returns can vary greatly over time.
|Language||Total||Prev. Position||Position Delta|
1 combines Lisp, Scheme, Common Lisp, Arc & Clojure
2 combines OCaml, (S)ML, Caml
3 summed separate searches for sml and ml
I recently considered switching my server deployments from Linux to FreeBSD. I need to move a number of sites off a dedicated server to either a different dedicated server (less money), or to a vps (much less money). Since I have to go through some pain with switching, I figured now was a good time to try and decide whether I should stick with Linux (Debian/Ubuntu) or move to FreeBSD.
After spending too many hours researching and experimenting (multiple installations of FreeBSD & lots of software built/installed), I’ve decided to stick with Linux for hosting web applications. Here are some advantages for each OS from my perspective.
- A slight performance advantage currently from my research, but this is debatable
- My primary desktop is Mac OSX which is based on FreeBSD, so I would be able to leverage sysadmin knowledge between my development machine and my hosted machines. This is the same advantage I had when my main development machine was Ubuntu and I hosted apps on Ubuntu. However, OSX doesn’t require much Unix sysadmin knowledge, so this isn’t nearly as important as the analog below.
- I like the idea of building packages from source, and the ports system does this very nicely.
- The organization of the OS seems superior to me. The ports system, startup scripts, file locations, etc.
- Paul Graham’s server OS of choice (at least for news.ycombinator.com), so I expect Arc will continue to be well supported on it (that is if Arc continues itself)
- Yahoo & other large sites use it.
- Ubuntu is a much better desktop OS, and I’ve decided to use it on my non-Mac home computers, so I can leverage sysadmin knowledge between my home machines and hosted machines. The desktop installation for Ubuntu 8.04 is unbelievably nice. If I ever become dissatisfied with OSX as my primary desktop, I’ll switch back to Ubuntu in a heartbeat. I just loaded Ubuntu 8.04 on my old 900 MHz AMD w/ 384 MB RAM, and it’s quite responsive.
- I’ve accumulated more sysadmin knowledge for Linux than for FreeBSD, and supporting two operating systems (OSX / Linux) is more appealing than supporting three.
- Better virtualization support
- Linux threading seems to perform better (although FreeBSD has caught up a little)
- Companies such as slicehost.com support Linux, but not FreeBSD (due to virtualization issues), so this limits my options with FreeBSD
- Auto power management works out of the box – shutdown the OS and the computer powers down
- The binary package system is much faster for installations. If I need to get another web server up and running quickly, I can do it much easier with Debian/Ubuntu than with FreeBSD.
- Google & other large sites use it
The two operating systems seem quite close to me, and it’s possible I’ll make a different decision a year or two down the road, but for now, the cost of switching from Linux to FreeBSD is higher than any expected benefit – particularly since my code rests upon Apache, Mongrel, Ruby, Rails, etc.
I have an emotional bias toward BSD since I started out on SunOS (as far as Unix is concerned), and it seems to have a richer history; however, Debian/Ubuntu seems to be the most practical choice for me at this time.
Even though I ended up sticking with my current server platform, I do feel better about having performed my due diligence rather than continuing with a default, and I have some really great notes for setting up a FreeBSD system should I need to do so in the future 🙂
UPDATE 12/24/08: This article is now out of date. I just installed Ubuntu 8.10, and getting Emacs with nice fonts is now much easier:
- Install the emacs-snapshot-gtk package
- Edit ~/.Xresources to have
Emacs.font: Bitstream Vera Sans Mono-10
- xrdb -merge ~/.Xresources
Before discussing how to get nice fonts for emacs, it might be reasonable to ask, “why emacs?” I haven’t fully answered that question myself, but had I not been able to get nice, readable fonts on emacs, I probably wouldn’t continue researching it. For the info on getting nice fonts to work, scroll down to “Nice Fonts” below.
After many years of using large IDEs to develop software, I switched to vim about a year and a half ago when I began developing with Ruby on Rails. Although the learning curve for vim was a bit steep, I quickly got to the point of being more productive with vim than I was with my previous IDE, and I’m continually learning features of vim that save me time and effort.
Ok, if vim is so great, why am I considering emacs? In a word, Lisp. Emacs, has great Lisp support. For the little bit of Lisp dabbling I’ve been doing, vim has been fine, but from what I’ve seen demonstrated with emacs and slime, I think it’s worth researching. Another important factor is that emacs is scripted with elisp, a dialect of Lisp. I’ve never taken the time to read up on vim scripting, but scripting emacs with elisp seems easy. Type in some elisp code into the scratch buffer, evaluate it, and it’s integrated immediately into emacs. I haven’t written any vim scripts in a year and a half, but within a few hours of researching emacs, I had implemented several elisp scripts (from source obtained online).
Here’s one to simulate the % command in vim which moves the cursor to the matching paren:
(defun match-paren (arg) "Go to the matching paren if on a paren; otherwise insert %." (interactive "p") (cond ((looking-at "s(") (forward-list 1) (backward-char 1)) ((looking-at "s)") (forward-char 1) (backward-list 1)) (t (self-insert-command (or arg 1))))) (global-set-key "%" 'match-paren)
Here’s one to simulate the vim o and O commands which open a new line either below or above the cursor and position the cursor properly indented, so you can start typing immediately. I use this quite often in vim:
(defun bja-open-line-below () (interactive) (end-of-line) (open-line 1) (next-line 1) (indent-according-to-mode)) (global-set-key [?C-o] 'bja-open-line-below) (defun bja-open-line-above () (interactive) (beginning-of-line) (open-line 1) (indent-according-to-mode)) (global-set-key [?M-o] 'bja-open-line-above)
After my brief exposure to emacs, I think vim is more concise. In other words, it appears that vim can accomplish a given task with fewer keystrokes than emacs. I’m curious to see how hard it is to extend emacs to have some of the niceties I’m used to with vim. Maybe I can have the best of both worlds – the conciseness of vim and the extensibility and Lisp support of emacs. Lennart Borgman passed on a link to vimpulse.el, so I’ll take a look at it soon.
I swapped my caps-lock with my left control key a long time ago, so the emacs chording isn’t quite as much of a problem, but I still wonder if vim might be easier on the hands/wrists since it requires very little chording.
I know some famous lispers use vi(m) for Lisp development, so I don’t think emacs is a must-have. Also, if I end up using a commercial Lisp such as Lispworks or Allegro, I may consider returning to an IDE for lisp development. So, at this stage, I’m still very much a vim user who is researching emacs.
UPDATE:Well, sometime between the original post and now I became a die-hard GNU Emacs user, so I figured I’d update the post 🙂
But enough of that, how do you get nice fonts on emacs? I had heard that the new version of emacs (22) provided anti-aliased fonts, but apparently I was mistaken. I spent hours Googling and rebuilding emacs to no avail – quite a frustrating experience. Then I posted a question on the gnu.emacs.help usenet group and received a helpful reply in a few minutes which did the trick. Here’s the thread.
Here’s what I did:
cvs -z3 -d:pserver:firstname.lastname@example.org:/sources/emacs co emacs cd emacs ./configure --enable-font-backend --with-gif=no make bootstrap make sudo make install
After that, I was able to use the ‘Bitstream Vera Sans Mono-10’ font, and it looks great!
emacs -r -fn "Bitstream Vera Sans Mono-10"
The -r flag is for reverse video. I much prefer a black background. After making emacs from the cvs sources, it reports its version as 188.8.131.52.
After editing my ~/.Xresources file to have the following line:
Emacs.font: Bitstream Vera Sans Mono-10
And running the command:
xrdb -merge ~/.Xresources
Emacs automatically uses that font at startup.
During my hours of Googling, I had seen the page with the correct information here. But in my haste, I read the statement, “Note: Since the emacs-unicode-2 branch which had the xft support is merged into trunk, the current page is obsolete.“, and somehow got the impression that the entire page was obsolete, but apparently that is not the case.*
Fortunately, the helpful folks on gnu.emacs.help set me straight – thanks guys!
*UPDATE: I edited the wiki page referenced above, so the “obsolete” notice is further down the page.
After upgrading my Ubuntu installation from 6.10 to 7.04, vmware workstation stopped working. I downloaded the latest VMWare 5.5.4 with no improvement. Then I found this article which fixed the problem in a few seconds!
Just in case the article goes away, I’ll post the instructions here as well:
From the vmware-distrib directory, do the following:
# cd lib/modules/source/
# cp vmmon.tar vmmon.tar.bck
# tar -xvf vmmon.tar
# vim vmmon-only/include/compat_kernel.h
Change the line with:
static inline _syscall1(int, compat_exit, int, exit_code);
/* static inline _syscall1(int, compat_exit, int, exit_code); */
Tar the directory to vmmon.tar:
# chmod 755 vmmon.tar
# tar -cvf vmmon.tar vmmon-only
Finally, go back to vmware distrib directory:
# cd ../../../
# sudo ./vmware-install.pl
The error messages that indicate the problem for which this fix should work are as follows:
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /usr/src/linux-headers-2.6.20-15-386/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make: Entering directory `/usr/src/linux-headers-2.6.20-15-386'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config1/vmmon-only/linux/driver.c:80:
/tmp/vmware-config1/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or â€˜...â€™ before â€˜compat_exitâ€™
/tmp/vmware-config1/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or â€˜...â€™ before â€˜exit_codeâ€™
/tmp/vmware-config1/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to â€˜intâ€™ in declaration of â€˜_syscall1â€™
make: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1
make: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2
make: Leaving directory `/usr/src/linux-headers-2.6.20-15-386'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
Unable to build the vmmon module.
For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/download/modules/modules.html" and
Wow, debian.org has finally released version 4.0 (“etch”). debian is an awesome linux distribution for servers, but 3.1 has some rather old packages. In particular, I need Apache 2.2 for mod_proxy_balancer, so I installed Ubuntu 6.10 server on my last server to get more recent packages. I expect to use debian 4.0 for future server installs.