>Do you believe rehabilitation is impossible or do you want revenge?

I don't believe that someone who commits mass murder can be rehabilitated, no. It isn't about revenge; it's about public safety.

Someone once pointed out that hoping a rapist gets raped in prison isn't a victory for his victim(s), because it somehow gives him what he had coming to him, but it's actually a victory for rape and violence. I wish I could remember who said that, because they are right. The score doesn't go Rapist: 1 World: 1. It goes Rape: 2.

What this man did is unspeakable, and he absolutely deserves to spend the rest of his life in prison. If he needs to be kept away from other prisoners as a safety issue, there are ways to do that without keeping him in solitary confinement, which has been shown conclusively to be profoundly cruel and harmful.

Putting him in solitary confinement, as a punitive measure, is not a victory for the good people in the world. It's a victory for inhumane treatment of human beings. This ruling is, in my opinion, very good and very strong for human rights, *precisely* because it was brought by such a despicable and horrible person. It affirms that all of us have basic human rights, even the absolute worst of us on this planet.

This is precisely why I lost all interest in Oculus the instant I heard that it had been acquired by Facebook.

As someone who's job it is to work on things like this, there's a few things that must be pointed out.

- SPDY runs over SSL. There isn't an unencrypted version -- note that SPDY was in fact faster than HTTPS.

- Many of the tricks used today to speed up page delivery, such as domain sharding, actually hurt SPDY's performance. SPDY's main benefit is that it opens up a single TCP connection and channelizes requests for assets inside that connection. Forcing the browser to establish a lot of TCP connections defeats this entirely, and the overhead of spinning up an SSL connection is very high. (And again, it should be noted that SPDY *WAS* faster, even if just a little bit, than standard HTTPS.)

There are other features in SPDY that today remain largely untapped, such as a server hinting to a client that it knows it'll need some content ahead of time -- giving the client something to do while it'd normally be idle waiting for the server to respond while it's generating the HTML it requested. (Large DB query, or whatever.)

Web engineers are clever and a smart bunch. While it looks like there's not a lot of gain to rethinking HTTP 1.1 today, given the years of organic growth we've had and time spent optimizing an older protocol, as new technology comes along that take advantage of the new foundation, things this will change. Give it time.

To the folks complaining that this guy doesn't know what he's doing, uh, he's a Chief Product Architect at Akamai. Yes he does. The folks at Akamai know more about web delivery than just about anyone.

- Bunny

Great, I await your refutation of this paper. I'm sure it'll be interesting to read.

I took a look at the paper in case I managed to understand something, and came across this:

Information Storage Capacity

If each extended kinase can either phosphorylate at the S-T site on a tubulin substrate, or not, the process effectively conveys one bit of information (e.g. no phosphorylation = 0, phosphorylation = 1). Each set of six extended kinases on either side of a CaMKII holoenzyme can thus act collectively as 6 bits of information. Ordered arrays of bits are termed âbytesâ(TM).
[...]

Logic Gates

Clusters of phosphorylated tubulin, and/or MAP attachment may serve as logic gates for propagating information. Figures 9 and 10 demonstrate two types of Boolean logic gates, an AND gate and an exclusive OR gate (XOR) in which MAPs convey inputs, with output along tubulin pathways. Figures 11 and 12 show AND and XOR gates in which MAPs convey output of inputs and processes in tubulins within the MT. The combination of XOR and AND logic gates forms a universal set for computation in which all other logic gates (NOT, OR etc.) can be conceived. Signals propagating through MT-MAP logic circuits may extend throughout cytoskeletal networks, regulating synaptic function, cognition and behavior.

Whoa. If that research is correct then that's really amazing.

Well, most code stays in the same "niche".

For instance, I made contributions to the Second Life client. Some people actually reused my code. Where could I look for improved versions of it? Well, given that it was quite SL specific due to ties to their UI code, I'd say that in other people's SL viewers.

First, no, it would not be a complete rewrite. Pretty much just the function bodies.

"just", yeah.

Also a lot harder than you think. GPL code is still under copyright. To protect you against chances of infringement, you'd have to pretty much start by reimplementing the app by following a header file, and spending a lot of time wondering "WTF does this function do?", "what does this function return when passed a null pointer" and "Argh, this part is horribly ugly".

It can be done, but it's a pain in the ass, and coding your own app is a lot more enjoyable.

Somebody actually threatened me with your exact scheme once. 5 years later it has yet to materialize.

Second, you get the advantages of compatibility with add-ons, plugins, etc., for free.
Third, you get binary and user compatibility, so you can get access to current users.

Until development diverges, that is. Users mostly keep using what they were using before. You're going to provide something more impressive than "what you had before, only now you have to pay for it!"

Fourth, unlike the open version, which even the original devs would have a hard time making money selling the code, you're free to optimize and sell the resultant binary code - "100% compatible but 30% faster!" Or "we've removed over 400 bugs compared to the original."

So you get a few corporate customers maybe. 95% of the userbase won't really care. See how many normal people (ie, not companies) bother with paying for RHEL vs the marketshare of the other distributions. Heck, most companies use CentOS when they can get away for it.

Your bug fixing and improvements probably will require changing the ABI.

A complete rewrite.

Sure, you could do that. But at this point it'd be really easier and more convenient to rewrite from scratch.

Heh! Actually SL still exists, and is doing quite well as far as I can tell.

This would actually be perfect for a SL web shop.

Heh! I don't care for terminology arguments. It's not important to me what it's called. It does precisely what I want it to do, and that's why I use it, and not because I'm committed to some philosophical concept of freedom.

But, most practical freedom does come with strings attached. Even back when everybody was proudly saying that America is the Land of the Free, it wasn't by any means anarchic.

If you want to write free software for the benefit of the IT community and not a certain unemployed American self-righteous zealot, you should definitely release it into the public domain or â" if you want attribution â" use some easier and more relaxed license (both to understand and read) than any GNU license.

I don't want any of those things.

I write for my own benefit, not for the "IT community". I want attribution, and your improvements to my code, or your money in exchange for a different license. I have no reason to give you code with no strings attached, no matter how much that might displease you.

GPL is perfectly usable in a closed management model when the code is used internally, for example when you provide a service not a software product like google.

That doesn't apply to software that's intended to be sold to end users, which can take advantage of the GPL. For the rest, there's the AGPL. Google doesn't seem to like it.

look at the Linux kernel being locked into GPL v2 because all the contributors of patches and new features/functionality can't/won't authorize a switch to GPL v3

Actually that's in a way a benefit. Part of what I like about the GPL is precisely the situation with the kernel. By mixing together so much code from authors that would disagree with a change, are unavailable, dead, etc, it'd take the rewrite of a huge amount of code to relicense the kernel, to the point it's not worth trying. It exists in a weird category of its own where nobody really owns it, and nobody can ever become the owner. I consider that state to be desirable, even if there are problems like with the GPL3.

BSD licensed projects have been easier sells for some, for example Sun Microsystems and Apple Computers.

They like it better for sure, but why would be that a good thing for me? Darwin last time I looked at it was unusable and pretty much dead, for instance.

My guess would be that for programmers who plan a livelyhood based on writing wholly (or near to it) FOSS code, something like the GPL protects their interests and future business possibilities in the market more than a permissive license like the 3-clause BSD. For programmers who write a lot of code under proprietary licenses, I can totally understand that they would (1) want (or rather NEED) to use permissively-licensed libraries, and (2) thus would be much inclined to release their code under those same permissive terms.

Actually I'm not so sure of that. In my experience, companies don't like to help their competition. My company releases an open source product, and you can bet every bit of code has the GPL3 on it. There's no good reason for BSD licensing anything. We have competitors, why would we help those for free? With the GPL at least if we solve some thorny problem and they take that code, we can then get the improvements to that.

Same goes for me personally. I have no interest in helping a competitor in my free time, and if unemployed I don't want to be working for free for some company earning good profit.

To me, BSD people seem to have mostly an anti-copyright and academic background.