And there's nothing in North America except trees and savages. What a short-sighted view you have.
There's a lot of value in having humans along. Currently, launch costs are so high that the costs of bringing along the life support for humans is prohibitive, but if it got cheaper many things would work better.
Consider Philae - if it had landed a few meters in another direction it would still be working. If it had been a manned expedition, that wouldn't have been an issue.
Or look at the Mars rovers. Great stuff, but there's little ability to improvise. Think up a different experiment you want done? Well, it'll have to wait for the next rover because that one can't do it.
Uh no, the Linux kernel is monolithic because it runs the drivers as if they were a part of the kernel rather than running the drivers as separate processes.
That's such bullshit. We didn't understand the atom until a little over a century ago. Quantum mechanics even later. Just because it's been thousands of years and we haven't figured something out doesn't mean that it's unknowable.
It isn't in the actual init system, it is an optional daemon that uses the interfaces that systemd exports so there is nothing that actually forces anyone to use it. My Debian based firewall runs systemd with unbound without any problem.
Did it actually not boot or did it seem to hang and the guy resets it after a minute? I ask because my PC had exactly this problem. Ages ago I had a drive die in my system so I pulled it but missed one of the references in
The systemd update a few weeks ago finally gave me a nice message on console to let me know that one of my fstab entries was timing out so I checked, found the entry and now everything boots faster.
And the criticism from those who are against systemd is extremely important to consider. The complaints are very sound, from a technological perspective. They're also based on decades of real world experience, which just cannot be ignored.
I'm not a total fan of every design feature of everything systemd has done but gave you actually read their supporting references? I'm most of the cases boycottsystemd has rephrased events to make the systemd folks look as bad as possible in ways that would make a Fox news reporter feel proud. A good example is their comment about requiring "bug for bug" compatibility with glibc was instead a use of a certain non posix flag needed for thread safety and complaining that it is tightly tied to Linux is about as helpful as complaining that udev is tightly tied to Linux.
At any rate, I find it very telling that they don't actually mention any of their supporters.
Or Greeks, I guess? Or the tons of other countries in which octopus is not an exotic food?
I think the most important piece of news of this story is that Wikipedia is no better than Google or Facebook, and exploits/sells search data too.
They made the assumption that if a disease is spreading somewhere, there people start looking for information about the disease on wikipedia
Imagine the potential: if a lot of search logs contain "EBOL-AAAARGH", they'll know a particularly fast-acting variant of the virus has emerged.
Before you say such things, you might want to look up the legal morass surrounging mail servers under your direct control and those not. Start with Megaupload and then follow links to the less public ones. There are DAMN good reason to keep your mail server on premises be it home or business, if you don't understand why you might want to educate yourself before giving advice.
I too am a Comcast victim, business class, and I have a mail server on their static IPs. This has been the case for years and while I have seen occasional blocking during inter-company spats, nothing blaket like you are seeing. It could just be the range you are on or it could be something else. What I am trying to say is that it is not those big three blanket blocking Comcast IPs.
I would see if Comcast can give you another set of statics in another range. That may help.
The difference being that you could have coded it from scratch - and you don't learn how to do that just by copy/pasting code.
Because nobody is making that many batteries yet and they're quite expensive? The whole Tesla "gigafactory" is so they can produce 500,000 cars per year. That's a drop in the bucket for supplying homes with batteries.
64bit... again, bragging points about how many bits you use, no functional difference to anyone. Its like when I gave the 32 bit version of Visual Studio to a colleague and he complained that he wanted the 64 bit version.... there is no 64 bit version because it isn't needed. Its just the typical knee-jerk reaction that 64 bits is somehow essential for everything, not just those programs that really do require it.
Not entirely true, x86 was famously register starved meaning you had to spend a lot of time swapping things into and out of the general purpose registers. When AMD designed the 64 bit extensions, they doubled the number of registers to 16 total, meaning software could spend less time moving things around and more time actually doing something useful.