See, kuzb, this would be an example of logical fallacy.
That there is a "they" that is taking choice away from someone.
It astonishes me that you can do anything with open source systems and suggest that you are having choices removed. I guess lots of people argued the same with Gnome. You know what those poor people did when their "choice" was taken from them? They chose something else.
This popcorn is delicious.
Systemd changes the way various start up and backgound processes are triggered.
The aim is to come up with something that can do more than the current init / cron et al processes in a more coherent way than at the moment, which dates back decades. Many approaches have been taken over the years, but generally try to keep the foundation of how it works the same, but make it "better". systemd throws out everything and starts over with a different approach.
The reasons why people don't like it are legion. Some because of change resistance - this manifests in many different ways. Some because of the "who" of it. They don't like source of the change. Some of the resistance has a technical foundation - the first process in the current init is very simple and everything spawns from it. With systemd, it is complex, and so the fear is that it has an increased probability of failure or instability. And linux is founded on a reputation of stability. Arguments are that it isn't very unixy - which is to have lots of small tight components that do one thing well all working together. Arguments are that having many processes spawn to do something relatively straight forward is unixy, but that doesn't automatically make it good. Arguments are that having one (main) process mediate all this stuff is better than having everything mediate itself and try to cooperate with everything else.
The difficulty with all of the arguments, is that a significant proportion of them are emotionally based, rather than technical, but all are couched in a technical setting, which makes it extremely hard to really get to grips with the real pros and cons.
I am happy to have systemd on some machines, and happy to not have it on others. With regards to this whole topic, the best bet when you see a discussion unfold is sit back with popcorn and watch either sides arguments dissolve into logical fallacy.
but there's this awesome thing called a covenant, you might want to look it up
I looked it up on Wikipedia, but I am non-the-wiser.
Can you explain what it is?
Me too! And I do it all the time.
No more, thank god.
A stethoscope is a medical device, and entirely tolerant of network failures. Add a sensor to it and wifi, and what it records could conveniently be saved to a network. It is just an internet of things device. If the network fails, it still performs its primary function.
Not every medical device is life critical, and obviously (or perhaps it isn't obvious), the ones that are life critical are less likely to be designed around a flakey network connectivity model.
Surely if a corporation wants to mine (and profit from) resources in outer space, which are owned by every one, they simply need to apply for a licence from a central body.
It should be fairly straightforward to negotiate a licence that makes it worthwhile for the mining corporation that also reflects ownership. So either a proportion of the resources or profits derived from those resources (via a tax) would be distributed to the treaty signers.
iphone users have no need for multi tasking
I can do 150 wpd on my tablet.
As long as I have a sharp chisel.
The Pdroid http://www.xda-developers.com/android/pdroid-the-better-privacy-protection/ patches are a "better" approach. They allow apps to keep the permissions they are designed to use, but feeds them fake data when they use them.
This protects privacy without crashing apps. However, it requires either a custom firmware with it already baked in, or running the patches against official firmware+root. This places it out of the comfort zone of many.
It would be fairly straightforward to have a single login authentication method that exposed a unique id to each login destination. That would eliminate cross-referencing.
Wow, I had lots of fun with pov back in the day, and Vivid before that.
Writing stuff directly in their respective scene language was a breeze too, and so easy to output from another language - so we used C to produce scenes and then leave POV to chug through them for days to produce animations.
Perhaps if Blender could import SDL, and given it can use POV as a renderer, it would make sense to stick with Blender so you only need one main tool.
You are kidding right? While everything you describe is true, the decision to exclude backward compatibility in WDDM was made to force an upgrade path, it has no technical foundation - it is purely a commercial strategy. Even MS can't design libraries that bad unintentionally.
What users need is unique to each user. How they wan things set up, and whether they want "flashy" features or not.
Of course they want function - different ones. But to differing degrees, they want some control over the form as well.
The best DE is one that can be anything to anyone and let them get on with what they need to. The worst is one that expects the users to confirm to a specifc paradigm. Gnome is heading in one direction on this continuum, KDE is heading in the other direction, and this will sometimes include flashy features that aren't entirely useful, but people still want them.
Like wobbly windows.
"Conversion, fastidious Goddess, loves blood better than brick, and feasts most subtly on the human will." -- Virginia Woolf, "Mrs. Dalloway"