This.

I've had so many devices that people claimed had shitty battery life, when I had no issues whatsoever. Like the Nexus 4.

(The N4 DID have some issues on initial release with the GPU frequency governor and broken wifi ARP offloading, but once these were fixed the device was great.)

Same with the Nexus 5. Google had some nasty power management bugs that killed battery on some wifi networks, but they had commits on AOSP within days that fixed the issue on the next OTA.

This is only if the phone's broadcast/multicast filters are broken.

A proper wifi chip SHOULD filter out broadcast/multicast when the device is suspended.

Unfortunately, it's a common item for vendors to screw up. The Nexus 4's ARP offload was broken for example, leading to all sorts of issues. The original Galaxy S2 had a Broadcom chip that fully supported ARP offload and broadcast/multicast filtering - but Samsung disabled the filters, allowing everything through!!! (They do this on a regular basis on multiple devices...)

So Clojure is not an interesting Lisp-like language? BTW there is a smalltalk for the JVM: http://www.redline.st/discover...

So, I see this as rationalization.

The fact is, you took a leadership position, and later turned your coat for reasons that perhaps made sense to you. But they don't really make sense to anyone else. So, yes, everyone who supported you then is going to feel burned.

You also made yourself a paid voice that was often hostile to Free Software, all the way back to the SCO issue. Anyone could have told you that was bound to be a losing side and you would be forever tarred with their brush.

So nobody is going to believe you had any reason but cash, whatever rationalization you cook up after the fact. So, the bottom line is that you joined a list of people who we're never going to be able to trust or put the slightest amount of credibility in.

And ultimately it was for nothing. I've consistently tried to take the high road and it's led to a pretty good income, I would hazard a guess better than yours, not just being able to feel good about myself.

Meh, it's easy to find people with skill. With values, OTOH...

You have a point.

It's sort of a chicken-and-egg issue. Debian doesn't get the help because Debian doesn't make itself worthy of getting the help. There have previously been paid developers working on Debian, they simply weren't paid by Debian.

The patent was not on aspirin, it was on combining aspirin with another drug.

The problem is that some factions in the non-systemd camp are pursuing systemd "emulation" by using shims and forks. That way you just get a second rate systemd, and it will remove any motivation from upstream projects to support anything else than system. Using Ubuntu's "logind" is a short term gain, but a strategic failure for the non-systemd camp. They need their own implementation of needed infrastructure, not just copying or emulating systemd.

It sounds a lot like the non-systemd camp have no idea what they are actually for, they only know what they are against. So this kind of thing is not surprising to hear.

The "UNIX philosophy" is an empty slogan that switches people's brains off. It sounds great, until you try and build a real system with the features modern users demand, and then it turns in to an exploding nightmare of combinatorial complexity as every program tries to abstract itself from every other program in the name of political correctness. As already noted elsewhere, the programs people use serverside Linux to actually run barely resemble the UNIX command line tools and that's for good reasons ...

I am beginning to be wary of systemd, but no. I am talking about anal-retentive policy wonks who believe they only make the distribution for themselves and have (perhaps without intending to) systematically marginalized Debiian and made the project a whore to Ubuntu.

There is a certain contingent in Debian that is not good for the project, IMO. I would like to see which side of a fork they are on, and pick tthe other.

Is there really someone so stupid that they cannot tell the difference between a cartoon drawing and a real child?

There appears to be an entire united kingdom whose legal system is populated with such people.

Just FYI, the rule against illegal cartoons exists in the USA too. The Supreme Court struck down attempts to use CP laws in this way as being obvious nonsense, so Congress just went ahead and amended the law to make it explicitly illegal as opposed to implicitly illegal.

Unfortunately a lot of crap like this ends up being brought into otherwise sane legal systems thanks to pressure from the USA to "upgrade" national laws to meet the "latest standards". Japan has been pressured for years to tighten its CP laws, being publicly named and shamed etc - the primary justification for not doing so was fear of false positives. Like this one. And like the notorious cases where two teenagers can legally have sex but not photograph themselves doing it.

Fact is, politicians love being able to say they made the law tougher on paedophiles. It's a sure popularity winner. So it's inevitable you end up with idiocy like this.

I was running Gentoo on my desktop and laptop to get the latest performance optimizations since most distros at the time were optimized for older processors. Ubuntu was really the first distro that was optimized out of the box for performance desktops. I don't miss debugging compilation issues with "emerge world".

South Korea is hardly the third world. If Danish shipyards can't beat them on price, why not?

Sending the content of every search request to Apple? Notifying Apple if the user sets up a non-Apple email account? That's a blatant violation of the Computer Fraud and Abuse Act unless Apple properly discloses that up front and gets the user's consent.

Apple didn't do that.

The EULA for MacOS isn't on line on Apple's own site. This matters. It violates the FTC's "clear and conspicuous" rule on disclosures. It's just like bundling spyware, which the FTC and state attorneys general have routinely hammered vendors for trying.

This puts Apple in the uncomfortable position Sony was in when they put a root kit on an audio CD.

You're correct. The wavelength of Ka-band frequencies (26-40 GHz) happens to line up nicely with the size of a raindrop in flight. That leads to more atmospheric signal attenuation, but isn't necessarily a deal-breaker; it just means you need a bigger dish to receive it and a more powerful transmitter for the return channel. (The new generation of high-speed satellite Internet services all use Ka band, despite the "rain fade" issues, because the higher frequency enables higher data rates.) In the past, the satellite industry tended to rely on lower frequency bands (such as Ku and C) to save costs on dish/transmitter size because of this concern.

For a cellular service where you're looking laterally at a tower instead of straight up into the sky, the weather issue should be less of a big deal. However, you should note that any frequency that high up will have a very very hard time penetrating indoors through anything thicker than a single-pane window. So expect that this will be used for fixed home Internet applications where a receiver can be permanently mounted outdoors or near a window, rather than traditional cellphone usage that can happen anywhere you go indoors or outdoors.