Ruediger Meier schreef op 05-04-16 12:34:
On Tuesday 05 April 2016, Xen wrote:
- backward compatibility is notoriously bad in Linux compared to other systems (or even on its own): Gnome/GTK3 keeps breaking pretty much everything with every minor version. That's not true. Most Unix/Linux window managers and programs do it right. Stupidly the few broken ones (gnome/kde/etc) are mostly used.
So the question is: does your distinction matter in practice? But there appear to also be issues with binary compatibility and library compatibility to begin with. I didn't make up that statement. I was referring to some thought expressed in that large online document that was recently linked to. The one that compared binary compatibility and backward-compatibleness of Linux versus other systems. I don't want to go into that now here.
Consumer oriented applications like Thunderbird might not suffer as much from this; the database for TB 24 appears to be identical as for TB 38. But KDE specific apps might see a lot of that. Firefox and Thunderbird are worst. They are not even able to run twice on the same machine (e.g. ssh -X or vnc, etc.). It's a real pain. I think I was merely talking about version differences. If the OP also wants to log in multiple times on the same account, that is another issue.
Obviously the new spirit is to remove all multi-tasking capabilities. Software developers and designers want to force users to only do one thing at the the same time. Apps are starting in full screen by default or continously steal the focus. Websites have font sizes for blind people per default. If there is still space left on the latest 4K monitors then they fill it with utopic huge buttons or stupid pictures. A default pulse audio setup can only play sound for one user at the same time. Remote users are not able to play sound. Switching to console turns off the sound... Anyways...
Yeah I agree with that I think. I've never had to do any kind of remote program running, so I have not run into these issues myself on Linux. That saying I have never run a remote "client" across a network link (for X).
kde3 did and still does a good job to handle multiple simultaneous logins on different machines with shared NFS homes.
Okay. What of today?
About backward compatibility. IMO programs which "destroy" their own config files on version upgrade are simply broken. Please report bugs! I prefer to use programs which _never_ write something to their config files without asking me explicitly.
Yes, or they are broken by design, or becaus the designer doesn't care about it. Just think of the vast number of library updates constantly being pushed on Linux. There are just no long term fixed platforms that any app designer can depend on. Sometimes you have a release that stays consistent for some time, but it still means you need to package (and build?) for every version of every distribution instead of just one binary package for all. There are no agreed-upon Linux-wide "platforms". It is easy to say something is just broken. Then you don't have to blame the tree for the fruit. (Same way is to say that these are just bad apples, the rest of the tree is perfect). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org