I don't think enough users care enough about privacy for there to be a massive market there. If not why didn't more people switch to DuckDuckGo or Diaspora?
That's not a fair assessment. The problem with NSA isn't that their authority is opaque. The problem is that their authority, dating back to the cold war, is so broad that it's difficult to cabin what their doing into public policy objectives.
In other words: once you pass a law that gives the government authority to dragnet communications, no matter how specific and overt the law is, the authority you've delegated does grave and intrinsic harm to transparency.
GCHQ are pretty clear what they are doing. They hover up everything they physically can regardless. If they get caught and it turns out to be illegal they get Parliament to change the law for them.
What i find odd is that he is ranting as if it is a code problem when it is a package manager problem.
Unless i am badly off the mark, ld will use soname to tell lib v1.0 from v1.1 or v5.97. But the problem is with package manager flatly refusing to have anything to do with installing multiple lib versions side by side.
That is, if they have the same package name. End result is that one distro use glib3.xyz to designate glib 3.x, while another use glib-3.xyz Yet another use glib.3.xyz.
They all hold the same files, but for the package managers they are different packages. And will resolve dependencies based on that.
Applying containers and/or sandboxes to this is a Will E. Coyote solution...
It is not just this. It is also that RHEL 6 will have libfoo4, while Ubuntu 14.04 will have libfoo6, and then Debian Wheezy will have libfoo5. Even if the way the packages dependencies were expressed (libfoo-1-3 vs. libfoo3) were the same, the constant ABI breakage would be harmful.
But that problem is largely because of what i started out with, that their package managers can't handle having multiple version of libfoo installed under the same package name. Even tough ld and friends can via soname.
So they "avoid" it by insisting on using a specific version for the duration of the distro version.
Hey, your site is great, just a suggestion, you might consider submitting your site to PocketCasts (email support@shiftyjelly.com), it's the most popular podcasting app on Android, and you don't seem to be in their directory. I've added your feed to their app, but it would help people discover your show.
Except that Dart compiles to JavaScript so you can still 'write once' and have it run anywhere. Also I don't really see how Dart is "proprietary" since it is being standardized in Ecma TC52 and is licensed under the BSD license.
> Also I don't really see how Dart is "proprietary" since it is being standardized in Ecma TC52 and is licensed under the BSD license.
I guess most people feel that it's some OOXML-like rubber-stamping process. Or how many of Darts numerous flaws have been fixed in ECMA through the participation of other members?
No, not exactly. WebRTC has no concept of interoperability between services, only between clients. You need a signalling server to communicate the initial call between clients, and if you wish to connect clients across services, then those two services would need to connect to each other in some way, which is not detailed in the spec.
There are efforts to use SIP and XMPP for this, but that only solves the WebRTC-part. If you want SIP-clients to interconnect, you need expensive hardware/software to transcode the streams, and you loose the P2P-part. WebRTC is not a golden cow of interoperability between services.
