anyone else seen the new Lennart Poettering's new proposal to encapsulate everything in "runtimes"? In a nutshell it sounds like apps will be distributed with all of their dependencies (which other apps can then depend on), much like an OS X app can contain whatever libs it needs in its .app directory. The proposal also depends on btfs heavily to deduplicate runtimes with the same libraries and to create a spaghetti monster of overlays on /usr to make it all work.
move over systemd, the new controversy has arrived
I see it most often on the sed/awk/grep/perl type questions, but it does happen pretty frequently I think. A lot of times you'll find like 4 or 5 answers on a question with 0 votes and it just boggles my mind. Personally, I wouldn't bother providing an answer to a question which I did not think w...
@mikeserv Maybe they don't think the question is well written, or lazy, or doesn't show enough effort? But that answers to that question might be useful or interesting to someone? It might be about not wanting to "reward" an unworthy questioner.
@mikeserv Like I said, they think the answer might be useful/interesting to others, and, perhaps more importantly, they want more Imaginary Internet Points for themselves. Also speculative (of course).
I do sometimes answer questions as a comment with a pointer, but usually that is because I can't be bothered to write a real answer. And that is because I don't want to waste my time on someone without a clue. If they get back to me, respond sensibly, and are polite, I'm usually willing to follow up with a proper answer.
For example there are a fair number of questions that are best answered by a backport, but typically people can't be bothered to try to learn about backporting. So, I say something like - try backporting, follow up if you have questions. Usually they don't. Would it make sense for me (in the first instance) to spend time writing a detailed answer on how to backport whatever, when possibly nobody cares? No.
It's just weird to me that a question would get an answer and not an upvote. The latter thing requires almost zero effort on behalf of the viewer - it's cheap and easy - whereas the former thing requires a real effort.
Why put forth an effort for a question which was not worth the cheap, effortless thing in the first place?
If someone asks how to list a directory contents almost 10 to 15 people can give the answer at the same time. But that doesn't mean the question is a good question for which the answer could be found from a simple google search.
As it seems to me, the community as a whole - the knowledge-base as a whole - is better served when a poor question is not answered. It also seems to me, that, for sake of the same, good questions are both answered when possible and upvoted as such.