No, actually. Unless by 'sucks' you mean, works imperfectly, but still better than those parts of the world that did not benefit from my tax dollars.

I say this with the benefit of experience. I've traveled to dozens of countries, rich and poor, and those with solid tax bases have dependably better public infrastructure than those without.

The cause of your crumbling infrastructure in the US is largely people not paying taxes.

Whose brainchild, specifically? I'm very interested in knowing. Because I think you'll find that the idea did not originate in Wikipedia, but that it was presented to them by others.

I hope you'll forgive my cynicism, but 'physically going' to the developing world teaches very little indeed about the broader truths of living in poverty. I say this having lived the last 11 years in a Least Developed Country, and having worked for half a generation with a parade of well-intended people who, to put it bluntly, haven't got a fucking clue, but who suck up all the oxygen in the room, making it impossible to get real, meaningful work done.

Do I sound bitter? Yes. I believe I've earned that right. Does that diminish my determination to work on real issues? Not one iota.

Yes, and instead of helping to fight this phenomenon through better policy and changed attitudes among the global institutions, what we get instead is people perpetuating the problem by empowering the very telcos who prey on those children.

Let's be perfectly clear about this: asking telcos to make a special exception for one or two services is probably the worst possible response to the situation. It's short-sighted, it generates little real benefit, and worst of all, it creates the impression that people are actually doing something, when they're doing less than the minimum needed to move the development markers.

You can defend these people all you like. I still maintain that:

a) They were misguided and wrong; and
b) The basic idea was inspired and promoted by a number of very cynical individuals to a bunch of very naïve (if well-intentioned) people with little meaningful experience in actual development work.

Let me state things clearly. These {facebook|wikipedia|whatever}.zero campaigns are a direct and unequivocal attack on Net Neutrality. They are the brainchild of some very smart, cynical people who know exactly how insidious the whole idea is, and whose job it is to set Open Data people against Open Networks people.

This is not an unintended consequence. This is the consequence.

My part of the world consists pretty much entirely of developing nations, and when we discussed these zero initiatives, we pretty quickly came to the conclusion that having offline versions of wikipedia (commonly available) was a more desirable thing than having a zero-cost version of it mediated by our friendly neighbourhood telco.

And Facebook zero was scoffed at when it was touted as a social Good.

ARRRGGGHHHHH.... CLARIFIC-I-ATION. I can't even spell it wrong when I WANT to!

Indeed. Now, most of you are out in the world seeking clarity. But, as long-time contributor Bennett Haselton writes, much more important than that is 'clarifice', the ability to explain truthiness without resorting to expertise or insight. Keep reading to see Bennett's clarification of how over two hundred years or jurisprudence can be usefully transposed onto decades-old technology....

Not necessarily. If the vulnerability du jour is catching media attention the way Ebola did, then you're probably not doing work you should be doing because you've got a CEO who just publicly pronounced that not one of your customers ever is going to get $EBOLA because of you. And suddenly your entire development cycle is in ruins, every manager everywhere has to explain in voluminous detail why his business unit will not be the cause of the next $EBOLA crisis, consultants will be hired to waste your time confirming that you really never were going to contribute to the global $EBOLA scare anyway....

... and meanwhile, your maintenance cycle is fucked, you have no budget left to do the upgrades that you need to avoid good old-fashioned data loss due to hardware failure, your children have forgotten who you are, and your wife just accidentally emailed her entire carpool pictures of her naughty bits (instead of her little piece on side, as she intended).

And your dog ran away.

NOW how does all that funding and awareness feel, eh kid?

Don't scoff. There are a number of scenarios where even several thousand bucks can go over the board without a second thought as long as there's some demonstrable benefit. In photography or video editing, your billing rate can be such that a couple of hours saved waiting on disk I/O can be sufficient to justify some serious spending on storage.

I've got 10 TB on my desk at home, and photography is not my primary work. It was nothing to me to drop over a thousand bucks on a decent hardware RAID controller and disk array. I'd seriously consider moving to SSDs as my primary storage medium if the price got down to 2-2.5 times the cost of a traditional disk.

Careful, you'll give yourself a aneurysm.

Eastern Arctic, at about the same time. Worked with Jeff Philippe a bit, too. He was operating out of Yellowknife back then. We set up what was at the time the most remote commercial ISP in the world. It was a great lesson in doing more with less, but still operating in a place where the broader context was more or less sane.

The thing that people forget when they're working in developing countries is that you can't take even the smallest things for granted. The movement of goods can resemble Brownian motion more than anything else. I've been in situations where the tool (or part) I needed simply didn't exist in the country. And I'm not talking about arcane, hard-to-find items - I mean things like the proper allen key to mount drives into their enclosures in a rack mount server. Power is abysmally poor, and UPSes degrade about as fast as bread on a hot day - and they're all hot days.

Long story short: It's tedious, difficult work with few rewards. Often you measure success in disasters averted. I wouldn't recommend it for most people, and I wish that some well-meaning people would stay the fuck away. But those who end up here, end up living a life to be envied.

Stay home. Seriously. As someone who has spent the last decade working on technology in the developing world, I can tell you that most of what I do is clean up after well meaning people who don't know enough about technology to avoid making simple mistakes, and who know next to nothing about local conditions. I cut my teeth working on the Canadian frontier, and I suggest you do something similar. Don't try to help until you're confident you can.

That's not just the Netflix perspective. It's the perspective that most sane individuals have.

Erm, even in the 1990s it was clear that point to point video was going to be an integral part of the internet. And I don't mean 'clear to me in hindsight', I mean clear to the guys selling fibre and switching gear to telcos and ISPs. I consulted with one of the largest and most advanced network equipment companies in the world, at one of their development labs. They were already talking about video on demand as a certainty in 1998, and rushing to get products to market.

If Comcast's management, in their infinite wisdom, were unable to see the writing on the wall 15 years ago, then they have only themselves to blame. The problem is that they have little incentive to invest aggressively, because they don't face substantive, effective competition in the majority of their marketplaces. So now, their complacency is such that they feel they have a right to bitch about the expense of providing a level of service that is well behind the state of the art in Europe, even lagging behind powerhouses like Estonia?

To answer your question, therefore: The money should come from reinvestment of profits. Just like it every other ISP and telco that has managed to leave them in the technological dust. If you plan to make the case that Comcast is somehow struggling to get by on the pittance they charge because of vanishingly small margins, then I'd suggest that the answer there is for them to give way to a company that actually knows how to make money in a sure-fire profitable business that features some of the more profitable corporations in the world. The fact is, they're making more and investing less than ever before.

You should pay the same because the baseline level of service should be minimum 10-20 Mbps these days. The fact that you use a vanishingly small percentage of that capacity should be your problem, not everyone else's. Pulling one or two video streams is baseline operability these days. For fuck's sake, I can do it and I live in the developing world in a place with some of the most obscenely high prices in the world!

I know that misery loves company, but just because your usage is unusually low is not justification for limiting the capacity of Comcast's entire customer base.

I missed part of the point, yes. But...

Which is kind of a sour grapes reaction to the fact that systemd is a pretty much of an all-or-nothing proposal. Back in the day, I worked on a distro that was based on RedHat, but which used DJB's service management system in order to handle the status of a couple of particularly bedeviling services. It wasn't pretty, so I have sympathy both with sysadmins who don't want to see things change utterly, and with systemd devs who don't want to have to try to shim service management onto the existing pile of cruft.

But....

They did not. They bitched and moaned and wrote their own alternatives.

They did, actually, if only implicitly. This is why none of the would-be replacements ever really took off. People do want any sysvinit replacement to be more or less transparent. And their expectation has yet to be met. You can argue the merits of systemd, you can claim that it's worth the pain, but you cannot with a straight face ignore a lot of history that led to the place we are today.

It's been tacitly understood that when introducing an incompatible system, you're swimming against a very strong tide. The refusal of both camps to achieve a workable compromise is a problem of mutually incompatible visions. The willingness of both sides to impute irrationality on the opposite camp without pausing to reflect on their own stance is a primary source of the continuing rancour.

Then they needed about half an hour to recover.

Then they came for the strippers again.

Er, not so much. Berlin in the 1920s was an island of intellectual freedom and experimentation in all kinds of artistic, social and political philosophy before the corruption and incompetence of the Weimar regime brought everything crashing down.

In the 1970s, it was haven for an entire generation of the European avant-garde. David Bowie's song Heroes is pretty much a story about two lost young lovers living in a besieged Berlin:

I can remember
standing by the wall
while guns shot above our heads
and we kissed as though nothing could fall.

It's no accident that the song is available in German as well as English.

You can go back even farther if you like. Similar to London's position as the maritime gateway to the Continent, Berlin's position at the crossroads between East and West, North and South in Europe has ensured that it's a popular mixing spot for political, social and artistic cultures.

It's pretty astounding, really, that you could feel so comfortable stating the exact opposite of the truth.

If you had actually paused long enough to RTFA, you would have found that people have been complaining about sysvinit - and writing their own supplements and drop-in alternatives - pretty much for as long as it's existed.

You've fallen exactly and precisely into the hole that the article warns systemd supporters are most likely to fall into.

I'm not suggesting this as evidence that systemd opponents are right. I am suggesting that systemd supporters, in spite of their protestations of open-mindedness and good intentions, are consistently, persistently wrong about the reasons why things are the way they are in the Linux world. They would never have invented and implemented systemd in the way they have if they weren't bull-headedly insistent on ignoring history.

... Which explains, of course, why you couldn't even be arsed to read the fucking article.