PulseAudio met an important need at the time, which was desktop adoption. It's a kludge but was a necessary one for "ordinary" users who increasingly wanted a machine that worked out of the box. It wasn't an issue for you, but "the minor trouble of setting up jackd", config files, and christ almighty, hardware compatibility lists were NOT flying with users who were attracted to linux but feared the tinkering. When the dust settled, and yeah, there was a lot of dust, it worked and the user base grew as a result. It's probably true that there were fewer considerations from the systemd crowd about the future of the back end and that was probably realistic and pragmatic - it doesn't make the back end any less stable. If it makes front end dev easier through a modular approach and accelerates user adoption, and that's where growth needs to occur, systemd will be a plus. I'm optimistic.
Either Netflix must connect via a provider that will have to pay a fee to the 1st Tier for their imbalanced peering relationship caused by the Netflix traffic, or they can directly connect with the providers that carry the content to the consumer. Either way, fees are incurred and yes, passed on to the consumer. This is an issue of "routing" and peering not an issue of neutrality. Incidentally, if they went with the former, the Tier 1 provider may incur fees themselves if they deliver more than they accept from whomever they are peering with. And that too would be passed on to the consumer via Netflix. One might suggest that anyone who believes the Tier 1 carriers are non-profit entities is uneducated. Netflix made the probably correct judgment that peering directly with Comcast would cost them less than whatever it would cost to pay the transit fee to the 1st Tier. Or would you rather the greater cost be passed onto you?
This is no threat to neutrality. This isn't even a neutrality issue. The carriers WERE neutral. Everyone else's traffic got the same shitty treatment, or good treatment if that was the case. But all traffic was treated equally and that is the goal of neutrality. However, peering relationships typically allow your traffic to pass if you allow my traffic to pass. But any carrier of Netflix is going to cause an imbalance and Netflix's PR wing decided to conflate the issue into one of neutrality, which is rather clever on their part. But you would be wrong to listen to them, and most of the media. Net neutrality is a laudable goal, but the core of this Netflix bru-ha-ha isn't a neutrality issue.
Since a Canadian firm was contracted, apologies were likely written into the contract well ahead of time, because Canada.
You might start with looking at FEDRAMP complaint providers found here: http://www.gsa.gov/portal/content/131931 I would imagine that those listed providers also have FISMA certification so you'll be able to determine if the categorization of the data you are trying to protect is met by the provider. ITAR categorized data must be stored in CONUS and I believe AWS Government Community Cloud and the USDA National Information Technology Center offered by United States Department of Agriculture supports CONUS only storage. I believe Google Apps for Government does as well. But the key thing is to ensure the FiSMA cert matches the categorization of your data.
Can I get an app that generates car analogies?
As a corporate overlord to well-meaning young hippie-leaning techies, Canonical has always been a bit odd. I recall their early versions came bundled with video samples of Nelson Mandela. That sort of bald-faced symbolic sales pitch to the young and idealistic was cleverly successful even if it now seems a bit easier to criticize them for their recent decisions. If it's a walled garden they're building, I suppose it'll have lots of flowers in it.
My federal masters have long argued that the validation of open source code by many eyes was a losing argument. It turns out what they meant by many eyes wasn't what we thought they meant.
...until they can post, "I replaced it with Mint Touch and never looked back."
...and the problem is multiplied like by a bazillion. Linux is a perfect solution except for all those kids games like Freddy Fish and when they get older, Call of Duty etc. I learned to fear my children much more than the People's Republic of Crafty Hackers. After awhile you pretty much get resigned to it and end up teaching them how to do the internets the right way. And you'll still have to re-image every so often.
On the other side of an office door, I heard the worst noise I've ever heard from spinning drives and in my panic, didn't even see the "do not disturb" sign. Turns out it wasn't spinning drives I was hearing. The lactating woman on the other side of the door milking herself with a noisy pump nearly threw the infernal machine at me. Some things are not meant to be seen.
When I realized they took away my minimize button I damn sure needed some free beer
A movie about an evil data center housed in a thermonuclear bunker attacking the internet in revenge for a slight? Yeah, I would probably watch that movie. Especially if they called in The Joes. And Scarlett Johansson.
GovCheese (1062648) writes "Canonical, the software company that manages and funds Ubuntu, announced that the Chinese Ministry of Industry and Information Technology will base their national reference architecture for standard operating systems on Ubuntu, and they will call it Kylin. Arguably China is the largest desktop market and the announcement has important implications. Shuttleworth's phrasing of, “The release of Ubuntu Kylin brings the Chinese open source community into the global Ubuntu community,” will irk many who already feel Shuttleworth controversial, but the partnership further cements Ubuntu as an open-source influencer. This is a win for Ubuntu. Is it a win for the open-source community?"
Link to Original Source
Link to Original Source
That Canonical's citing of Wayland's limitations were mostly refuted speaks to the larger issue of Canonical just not speaking to the non-Canonical dev community. Or at least this is the perception. Now that Caonical has influence, the non-Canonical devs perceive more and more that Shuttlecock is effectively developing a closed system that abandons the cooperative consensus that has driven community progress in the past. And when their Contributor License Agreement provides for non-free copyright, if Canonical chooses, with contributions toCanonical code, the fear is heightened. Of course the lens/privacy issue confirmed that fear. Basically Canonical is seen as more and more as throwing its corporate weight in ways that aren't pretty. It may or may not be good for linux going mainstream, but it's not pretty.