And an embalmed corpse that's been gone over by morticians to ensure it's presentable is any more "real"?
Last time 8000 police raided anything they were able to charge precisely 0 people with any crimes whatsoever.
What kind of idiot thought we'd reduce climate change (which most scientists agree has something to do with carbon released from fossil fuel production) by switching to another fossil fuel that still emits carbon when burned?
The reasoning is that natural gas releases less carbon than coal, so if we switch from coal to natural gas, then we'll reduce climate change. I do not have the information necessary to determine if that is a correct line of reasoning or not.
Of course it's incorrect. You're not going to reduce emissions by opening some giant new resource which does the exact same thing, and promptly drops prices all over the world for it.
No one investing in that industry is thinking "obviously we're only going to get 10 years of development out of this". They're planning to burn every last bit of it.
I want 8K phone displays. Entirely so we can use them as VR displays.
I'd love to see some example workflows of how you work on something like X - or the kernel, for different classes of bug hunting. It's the type of thing I've always wanted to dive into, but just the thought of trying to get to the stage where I can tweak/run/debug is incredibly daunting.
This is wrong. Peak oil is when new discoveries are outstripped by demand. Its the point at which the oil industry cannot grow at pace with demand, and must plateau and decline. Prices will shoot up instantly because month after month there will be less oil for per consumer available and no reasonable expectation of that changing.
Hey guess what, names for things are kind of important. You know what I don't want to install on my grandmother's computer? A program called "Gigolo" - I don't care how good it may or may not be at managing network connections.
The army of people who seem to think they're so logical and above emotions ironically are always the most upset when people want to change stuff which they think "doesn't matter".
Because labels are still stupid: if I delete something under one label, I don't necessarily want it deleted everywhere. But that isn't the interface on offer either - there's no "hardlink" style functionality.
And the schools don't dare inform parents of all the risks - parents would say "What, are you crazy? I'm going to risk my kids future so you can get a stupid trophy for your office? DIAF."
I wish you were right, but experience with the parents of brain-damaged young athletes indicates otherwise.
Maybe it's time to consider that they're engaged in willful child endangerment? Nobody, not even a concussed-out coach, wants to be labeled a child abuser.
Maybe so, but it's clear from what happened at Penn State that they just don't want the label. There's way too much tendency to turn a blind eye.
And it's also never been perfectly true, otherwise nobody anywhere ever would have had their system broken by package upgrades.
RPC allows proprietary software to leverage the functionality of your GPL software, which might go against your intent, as RPC becomes the de facto interface of increasing number of components...
Honestly, I don't buy into the whole non-GPL can't link GPL argument in the first place.
Suppose I were to tell you to grab your copy of the 3rd paperback printing of Game of Thrones and look at the second sentence on page 320. Does posting that sentence make this post a violation of GRRM's copyright? Of course not - I didn't copy anything in his book - simply mentioning that it exists and that it contains a page 320 in no way makes this post a derivative work.
Well, when you link a binary to a shared object, all you do is write a bunch of cross references saying that this function call should be replaced with an address associated with this symbol. Then a linker will replace those references when your code is loaded. None of this involves copying anything. Assuming the shared object is in RAM already being used by something else, your OS isn't even copying the GPL code at all when this happens, but even if a copy were made it is an unmodified copy of the shared object which isn't being redistributed - ie it is permitted by the GPL.
Sure, everybody says that you can't link non-GPL code to GPL code, but I am not convinced that a court is certain to uphold this. I could see issues if you try to bundle GPL and non-GPL software into a single larger work, but if you distribute the non-GPL stuff without the GPL content that problem goes away.
The main issue is no one wants to fight the court battle.
But frankly, this has all been kind of irrelevant anyway - you can distribute source packages, let the client do a compile on install, and ignore the entire affair.
It's essentially a project financed behind the scenes by Microsoft to delay the release of Linux updates-- hardware products (like Raspberry PI) that make use of Debian are currently stalled at Wheezy while the whole mess sorts itself out.
He said explanation, not a transcript of the signals you receive from the CIA in your fillings.
What unnecessary code? I'm genuinely curious what you think is completely dispensable as a system service at the init system level.
I mean we need something to launch processes, something to resolve dependencies of processes (init.d has insserv and the LSB headers), networking, disk mounting, time synchronization, authenticating and user session management (else how do your sysadmins log on from central administered sources?). We need process monitoring, logging, we'd like to have cgroups for security. We need some sort of time-based job scheduler.
Which one of these things are you going to drop? Which things are completely inseparable from systemd?
The biggest problem with the Kindle is it's very easy to forget you need to charge it "sometimes".
If there was ever a device that would benefit for long range wireless charging, even at just a trickle, it'd be the Kindle.
It also tends to be that people who forego cellphones still choose to utilize everyone else's. At some point that's a violation of the social contract - you're making yourself uncontactable, but taking advantage of that utility surrounding everyone else. Moreover, you're also starting to demand people adhere to your schedule on your terms: see complaining that people won't kowtow to your contact hours.