Jump to content

Why I hate UNIX: Difference between revisions

From NikiWiki
New page: ==Why I hate UNIX== This is a page which contains random entries about what sucks in Unix, weather it is Linux, FreeBSD, Solaris... It's mainly used as a reminder what we should do better...
 
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Why I hate UNIX==
==The Why I hate UNIX Page==
This is a page which contains random entries about what sucks in Unix, weather it is Linux, FreeBSD, Solaris...
This is a page which contains random entries about what sucks in Unix, weather it is Linux, FreeBSD, Solaris...


It's mainly used as a reminder what we should do better before World Domination with Voyager [tm]
It's mainly used as a reminder what we should do better before World Domination with Voyager [tm]


* Keyboard Layout in Xorg. Why does it have to be so hard...
* SSH & Terminals/TERMCAP: Aaaaaaaaaaargh (backspace, delete...)
* copy/paste: Qt way, GTK way, X way - copying highlighted text to the clipboard is very annoying
* unix commands like cp and mv (''cla loves the good old CMD commands!'')
* no consistent GUI concept (lets stick to CUA and/or anything advanced to that, possibly enhance them !)
* drivers or settings compiled into the kernel (uurg - stoneage)
* mount a floppy/CD(/USB stick ?) to access it
* no drive letters or something adequate (something like this must be there for those being used to it)
** the last two points need to be optional, I hate drive letters by now :) But yes, many people know just that so emulate it optionally
* forward slashes in file names (this is a killer for those being used to backslashes)
** same story, both must be possible
* case sensitive filenames (what is this good for ?)
* confusing directory tree with too many standard directories (requires too much knowledge, better use less standard dirs, better use env vars to point to certain directories !!!)


* Keyboard Layout in Xorg. Why does it have to be so hard...
== What I like about UNIX ==
Why not thinking also about the good items: (possibly we make another page of this?):
* boot/driver messages logged to a file (won-der-ful ! want this!)
* symbolic links (not implemented as files like in wincrap, but in the filesystem, or maybe with FUSE)
* mount partitions to empty directories (but: better go for FUSE to have something TVFS alike)
* piping output of commands into env vars (shell feature)

Latest revision as of 16:37, 10 August 2007

The Why I hate UNIX Page

This is a page which contains random entries about what sucks in Unix, weather it is Linux, FreeBSD, Solaris...

It's mainly used as a reminder what we should do better before World Domination with Voyager [tm]

  • Keyboard Layout in Xorg. Why does it have to be so hard...
  • SSH & Terminals/TERMCAP: Aaaaaaaaaaargh (backspace, delete...)
  • copy/paste: Qt way, GTK way, X way - copying highlighted text to the clipboard is very annoying
  • unix commands like cp and mv (cla loves the good old CMD commands!)
  • no consistent GUI concept (lets stick to CUA and/or anything advanced to that, possibly enhance them !)
  • drivers or settings compiled into the kernel (uurg - stoneage)
  • mount a floppy/CD(/USB stick ?) to access it
  • no drive letters or something adequate (something like this must be there for those being used to it)
    • the last two points need to be optional, I hate drive letters by now :) But yes, many people know just that so emulate it optionally
  • forward slashes in file names (this is a killer for those being used to backslashes)
    • same story, both must be possible
  • case sensitive filenames (what is this good for ?)
  • confusing directory tree with too many standard directories (requires too much knowledge, better use less standard dirs, better use env vars to point to certain directories !!!)

What I like about UNIX

Why not thinking also about the good items: (possibly we make another page of this?):

  • boot/driver messages logged to a file (won-der-ful ! want this!)
  • symbolic links (not implemented as files like in wincrap, but in the filesystem, or maybe with FUSE)
  • mount partitions to empty directories (but: better go for FUSE to have something TVFS alike)
  • piping output of commands into env vars (shell feature)