Does this just block autoplay, or videos completely?
Why would it be dificult to migrate from red hat to another distro in the first place?
In all honesty, there was no single standard before, but one for each distro (of small family of distros).
True, systemd did change a lot of things, but that doesn't invalidate the former point: it did standardize a lot in the process.
Wasn't it like 10 days ago that we say the demise of SSL 3.0, the last version still alive?
Yesterday we had news of Chrome dropping support for it.
Now facebook it setting up new servers that use it?
When jumping on a machine with a distro different to my own, I'd have to read for a while before understanding how to start/stop services. This was a pain if I needed to quickly help someone out on how to do something.
Now all distros run systemd, so it's just "systemd start nginx" on any gnu/linux distribution. Except gentoo, but I don't see a gentoo user asking me for help on how to do X. I also haven't come across clients with gentoo-based servers.
Standard service unit files help too. The work is done once, (generally upstream) instead of having to write service configuration files for every single distro (and keeping them up to date!). This may sound trivial, but the amount of effort reduced is immense!
Good thing we have OpenStreetMap which just keeps getting better and better.
But Linux is for desktops. For servers, you're always better off using BSD, which actually was born for servers.
Indeed, these scripts suck, while systemd's service unit files are very easy to edit and maintain. I wish we could have a an old-school init system that allowed configuration in that syntax: The best of both worlds.
Why not Intel? The latest Intel lines are pretty good (I game a lot on one of those), and have their drivers in the upstream linux kernel.
AMD is simply so awful in terms of drivers, that it doesn't really matter if the hardware is slightly better.
From TFA: Thomas prefers a layered feature exposure so that users can enjoy certain advanced features at a later stage after they get accustomed to the basic functionality of the application.
I assume that they'll keep the options around, just not mixed with the very basic options. A big issue with KDE right now, is that the settings windows of any application has half a dozen tabs, with dozens of options each. The very basic options and most common options should be grouped together, an advanced settings slightly on the side. Otherwise, it's just too intimidating.
Can you show at least one example of a special requirement a program had that could be satisfied with init and not with systemd?
Indeed: The fact that it no longer follows the unix design or philosophy is a huge change. The fact than one piece of software has eaten up the funcionality of dozens of very-used programas is also a big change.
Linux client: Still propietary, something many *nix users actually care about.
Follows symlinks: So does almost any application out there. That's not a good thing, it's just a lack of a bug.
Automatic full resolution photo uploading from mobile: "full resolution photo" is another way of saying "large files". How does the content of a file make a difference?
Spideroak refuses to release the source for their client (though they claim they will, some day). As it is, it's just an unproven claim that it's encrypted and secure. For all we know there might be a huge security hole making it all worthless (possible an accidental one, btw).
If the graphics subsystem fails, or I have to go to single-user mode, I have nano.
If you had access to that machine and got a chance to manually install it before the graphics subsystem failed. What happes if you didn't?