UNIX sucks

There's a setting for every petty little shit thing you can imagine, except for a custom path where you want apps to put their rc files and whatnot. I bet there was someone at some point in the design of UNIX who said "LOL lets clutter ~ with a million dot files and directories! Ha ha ha!!"

Face it: UNIX is gay.

Two words:
Windows registry

DURRRRRR

>>2

signed

DRIVE LETTERS ARE GAY (LOL CPM)
I STILL CAN'T HAVE A FILE NAMED CON, AUX, LPTx, OR COMx ON MY DESKTOP (DOS IS DEAD-YEAH RIGHT)
X86 INSTRUCTION SET IS GAY
CISC ARCHITECTURE IS GAY-MMX/SIMD IS A CHEAP HACK
BEING FORCED TO WASTE RESOURCES IN GUI ENVIRONMENT IS GAY
EXPLORER.EXE IS MADE OF GAY AND ROTTEN SHIT
IEXPLORE.EXE IS MADE OF EVEN MORE GAY AND FAIL
USING BACKSLASH TO SEPARATE DIRECTORY NAMES IS 20 TYPES OF GAY
WPA SUCKS BALLS
WGA SUCKS ELEPHANT BALLS
WIN32 API IS PROPERLY APPRECIATED ONLY BY SCAT FETISHISTS
MSVC++ TAKES GAYNESS TO HIGHER PLATEAUS
BUT EVERYTHING ELSE IS COOL

>>4
Maybe, but at least Windows supports the caps lock key.

>>1
you can:
./configure --confdir=/what/ever/you/want
could be something like --sys-config-dir or something else though.

whats wrong with dotfiles/dirs? they're usually "hidden" anyway, so it makes no difference if they are just in ~, or in ~/.config/.

yeah, windows is better. you have to work as root, because most apps are coded shit and you cant change it.
ENJOY YOUR VIRII.

http://4-ch.net/code/kareha.pl/1117884645/

Just because Windows is full of shit and fail doesn't mean that *nix isn't.

>>8
that was the most retarded post I've ever read, and I have hardly any experience in unix.

>>8
Truth

I have hardly any experience in unix.

Which, of course, shows what your opinion on the matter is worth.

I know people spew shit all the time on 4chan (gotta love it!), but it's rare that someone spews shit while admitting they don't have a clue.

>>8
Wow, that guy is pretty stupid.  At least one of his points was worth considering though, e).  I don't really mind though, as I have no configuration files that aren't dotfiles, and I put my stuff in subdirectories.

What's stupid about it? I agree with most the points.

posting in a shitty thread

14 GET

>>14
Unix tard got his feelings hurt

>>8

a) lol. Idiot. Maybe someone should tell him that -- is always before full words and a single - is in front of characters
--help == -h/-?

b) That's not a problem of the system but the problem of programmers who think they are clever. Or just don't know what they are doing, Or come from SuSE.

e) Why the hell would anyone need to do a ls -la on his homedir????

g) because "sane" and "powerful" can cooperate.

h) lol true :)

i) If you don't like lego cars and want a complete model car, then WHY THE FUCK DO YOU USE UNIX?????

>>16
:%s/g) because "sane" and "powerful" can cooperate./g) because "sane" and "powerful" can't cooperate./g

>>13
I assumed most, if not all, of his points were broken in the linked thread, so I was too lazy to write a long piece on each of them.  I still am, and neither will I read the thread to see, as it is too long.

>>16
a) ps? su? Lots of dinosaur utilities have shitty parameters.
b) The FHS sucks, plain and simple. It's retarded. Really.
e) Because dot-shit files are still files. Don't tell me you support hidden files; you might as well go use Windows Explorer.  Security by simple hide is the worst kind of security, and it always leads to trouble.
g) Bullshit. Unix console editors are bullshit, save for a few ones like mcedit which are mediocre or nearly average. Well, at least we got Kate.
h) Linux is a library hell. Install a few big applications, and you'll end up with a thousand of them, including several versions of each because linkers and developers are stupid.
i) Problem is, you can't really ride lego cars. They look nice, they look custom, but when you sit in them, they break.

>>19
a) ps has many parameters (tl;dr?), su has a few. now tell me about the shittyness please.
b) no, it's not. remember: not everyone uses one big /. if you seperate /usr from / it's really handy to have a /bin with the stuff you need to boot/mount the other directories. /usr/local is usful because you don't mess around with the /usr/bin which is usually controlled by the package manager.
e) they're not really hidden, they just don't show up to not annoy you, because they're usually config files you don't want to see every time you do a ls ~.
g) if you can't hanle "unix console editors" you probably won't use the command line often anyway. it's not hard at all to do basic stuff in vim, like editing a file (takes less than 5 minutes to figure out). you won't notice how  powerful it is though. (please don't compare vim (or even emacs) with something like kate)
h) what library hell? if you use a proper file manager (like... dpkg, pacman, etc.) you don't have to care about how many libaries you have installed, because you won't even notice them, except that you are asked to install them as dependencies. and it's really not as if every program uses 100 different libaries. if you have some basic libraries installed you won't have to install more most of the time.
i) then use something heavily preconfigured like suse, fedora, ubuntu, mandrake, etc.

>>16
a) What about dd, chmod, find, route, or any of the xterms? Why is it cp <src> <dest>, yet ln <dest> <src>? Why does ls -la work on linux, yet not on solaris? Et cetera.

b) You have got to be kidding. Every significant *nix out there has that layout, yet it's not a problem of the system?

e) I do it everywhere. Pure reflex. And of course, by default, root's ls is aliased to ls -la (as it should be), so dropping to root is annoying.

i) Maybe he likes it dispite the flaws? I certainly do. I just wish the flaws would go away. We'd have a better *nix.

what library hell?

I just had my head beaten in with that exact issue yesterday when I wanted to install mlview. First, mlview wasn't in the repository, so I had to do a source compile.

I had to install all the -devel packages, because the person who installed on this machine left them all out. It caused a cascade which resulted in me spending half an hour typing ./configure, then switching to the package manager to install the missing -devel package.

Some libraries had to be upgraded, but caused a conflict with others, so that resulted in a while upgrading.

Then there was the dependency that didn't resolve because some idiot forgot that libgnome-devel depends on libpopt-devel, or something like that.

Then finally the system choked because there was no libesd-devel package, despite there being a libesd package.

>>21
a) yaeh, it's inconsistent, but it's not *that* bad, because most of the progams accept both -stuff and --stuff. ln works like ln works like that because that way you can just do a ln (-s) /stuff/you/would/like/to/link and it get's linked to the current directory. that allows greater flexibility and less work (most of the time). ls -la doesn't work on solaris, because solaris isn't linux and linux isn't unix. you can, however, install the gnu-tools anytime.
b) ./configure --prefix=/usr
fixed. no big deal.
e) it's your problem that you always do a ls -la, not unix'.

>>23
ln -s <src> is unambiguous, and has little to do with ln -s <dest> <src>

With regard to b), how many people actually compile their installation from scratch?

With regard to e), the same argument could be applied to a flat filesystem. We have directories for a reason.

s/ln -s <src>/ln -s <dest>/

>>23
e) it's your problem that you always do a ls -la, not unix'.

And if you use a `real' ls utility that does not use the ugly hack which hides dotfiles, eh?