An example of a constructive approach to improve an installer:
While ZFS has existed for years on FreeBSD, it was not possible to do a ZFS FreeBSD install until recently.
In April 2012 Vermaden posted a guide how to do a manual install of FreeBSD using the ZFS filesystem. See http://daemonforums.org/showthread.php?t=7099
I neither had a system or disk drives to do such an install. When in the summer of 2013 I acquired the hardware needed, I wrote a Makefile to automate or script Vermaden's ZFS install but then aligned on 4K block boundaries . See http://daemonforums.org/showthread.php?t=8032
Last week I installed FreeBSD 10.1 in a virtual machine on a Linux box. And wow, the 10.1 installer did a ZFS install that very much is like the one Vermaden proposed. FreeBSD users should be thankful to him for quietly pushing and demonstrating the need for a FreeBSD ZFS install.
RE: graphical installer
The problem with a graphical installer or any GUI program is that it cannot be scripted or automated easily. Since a couple of weeks I have playing with Virtual Machine Manager, that is a GUI for creating and managing virtualized guests on Linux. After a while you get fed up because you are afraid to develop RSI from having to use your mouse so much.
So I spend a week studying and reading the man pages of the command line utilities that allow you to do the same thing and even more than the Virtual Machine Manager GUI. I now can install a new OpenBSD virtual machine within 5 or 10 minutes.
BTW in the 1980's I installed
Forth on an Apple II computer by typing in a IIRC 50 page long 6502 assembler listing. It cost me more than a week to get that assembled and running
