MPD: A case study for Client-server model

/prog/, explain why client-server model isn't pure shit for desktop applications like an audio-player: "run the music player daemon first, and then start the client, then stop the server process"
This is fucking overengineering ruining my KISS principle.

Would you rather your application's persistence be determined by the existence of a graphical window or a shell session that you can't close until you want to finish? The system tray doesn't count; it's not going to stay once you log off, and you can't skip tracks without being at the same session you started the process on.
The client/server model is the simplest way of being able to communicate with a long-running application whenever you want, bar sockets and FIFOs, but who the hell wants to echo skip >> /tmp/music-player.fifo?

Whoever thought daemonize everything was a good idea and ``the UNIX way of doing things'' was an idiot. Probably someone from suckless.org.

There are many ways of IPCs, sockets is provably the worse option. But tell me: why I would care to stay my audio-player running after I log off?
btw you can send any running process to background using Ctrl-Z + bg

>>4
sockets is provably the worse option
Citation needed.

why I would care to stay my audio-player running after I log off?
My desktop plays music through the stereo. I work on my laptop nearby. Why would I want to stay logged on to my desktop while I'm not using it?

you can send any running process to background using Ctrl-Z + bg
Excellent, now try closing the shell.

>>7
Why would I want to stay logged on to my desktop while I'm not using it?
Because you're running a general userspace program.

>>8
No I'm not. HIBT?

>>7,8
Look up screen, nohup, and disown.

>>10
And then how would I interact with the program afterwards?

>>11
Did you even look up what screen is?

I read that as [b]overniggering[/b[

Looks like you never thought of running a server on a media server and running clients from anywhere with Internet access.

This is really convenient, specially when you don't like to carry your music around with you.

I was going to make a joke about how we should have a ``man daemon'' to serve up manpages, but it probably exists.

>>12
I know what the fuck screen is. I was referring to the other things, but it seems you just want to be correct so you decided I meant screen, nigger.

>>1
This may or may not be a coincidence, but client-server programs aimed at desktop which have non-client-server analogues are complete and total shit compared to at least some of their analogues.  Examples:
 - torrent clients (KTorrent is superior to all existing client-server torrent clients),
 - same for emule, soulseek etc networks, the only marginally tolerable soulseek client for linux is nicotine+ (which is complete shit, but client-server implementations are not usable at all),
 - music players: 90% of GUI-only and 100% of text-only (C*Mus) players included in Ubuntu are superior in all respects to MPD and all of its clients, which are shit (including ario),
 - thank God nothing pops up for ``rss reader daemon'', otherwise this list would have grown in two.