diff options
| author | Stef Walter <stefw@redhat.com> | 2015-07-15 23:19:15 +0200 |
|---|---|---|
| committer | Stef Walter <stefw@redhat.com> | 2015-07-15 23:19:15 +0200 |
| commit | 91d5d7b8de0327e55b8c9e1436907678551242ba (patch) | |
| tree | 4545c92b0598122a7ba2bf67c52468233e32084d | |
| parent | 43b1923d6406788d7b0edf1b6cfbde8d439a4e2d (diff) | |
File systems suck too :)
| -rw-r--r-- | content/technical/installer-anti-pattern.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/technical/installer-anti-pattern.md b/content/technical/installer-anti-pattern.md index 07dbf16..dc39f3d 100644 --- a/content/technical/installer-anti-pattern.md +++ b/content/technical/installer-anti-pattern.md @@ -50,7 +50,7 @@ Another trivial good example of avoiding this anti-pattern is the *Create new di Instead of popping up a dialog asking for the initial directory name, the directory is created and you're then ready to type the name. This has been implemented in various ways, but the core design concept is that the user learns one workflow for naming a directory, whether it's a new directory or one that's renamed. -A bad example? Sadly most Linux installers end up as pretty bad examples. Operating system installers are tricky ... mostly because hardware sucks. So we end up asking the user to make choices before they've started to use the system: bad. But as noted above, this is less of a problem for immutable things, such as where to install the operating system's files. +A bad example? Sadly most Linux installers end up as pretty bad examples. Operating system installers are tricky ... mostly because hardware and file-systems suck. So we end up asking the user to make choices before they've started to use the system: bad. But as noted above, this is less of a problem for immutable things, such as where to install the operating system's files.  |