I stole your book, made a photocopy, and put it back where you left it.

If I may say so, sir, you're into some rather strange pr0n. I suggest you talk to someone about it.

You must be new here. A member of the Church of RMS would never use the term "open source" like that.

Furthermore, RMS predicted exactly this happening like 5 years ago and worked on a copyleft license that could cover SaaS. Google "tivoization."

RMS may be very passionate and extreme in his views, but his predictions for the future have consistently been spot on.

As someone who has actually had to integrate with Facebook, in practice they can and do change their API constantly. I'd love to ditch facebook but my clients all require integration.

So, I'm guessing you think Tom Hardy camping gear is way awesome.

I don't consider mega farming corporations as having much integrity.

I don't have a dog in this fight, but come on. There obviously have existed atheists who wanted to attack religious freedoms. Consider what the Maoist regime did to the Buddhists in Tibet.

I completely agree, though, that the current political climate of America is swayed very far in favor of the Christians, who simultaneously view themselves as under attack. Which, to me, is less hypocrisy and more a very controlled manipulation campaign that started when the Evangelicals teamed up with the Republicans and will probably end in one of two ways: Either some 1984-esque dystopic future where the "chosen" await rapture and the rest toil, or nuclear winter.

Okay, I need to go take my meds now. Imagination... too... powerful.

... and then health care costs will drop. Basic insurance plans will start to makes sense as providers known they only have to cover emergencies/unpreventable diseases/etc.

This reminds me of Babylon 5 moreso than Star Wars, however.

No, "DuGNU/kem Forever." :P

Because code reviews end up being an enabler for OCD coworkers to tell me how to indent.

The cost of buying a second monitor for one developer is immaterial. The cost of buying second monitors for every developer isn't.

Also, a lot of times you don't realize that a specification is completely broken until you're balls deep into implementation.

I personally don't write tests firsts, ever. I tend to work in three steps:

1. Write a proof of concept for the nontrivial parts of the solution.
2. Build tests/specs.
3. Write your production code.

This still isn't perfect, and you're trading a constant decline in productivity for a reduction in the number of times a sprint turns into a disaster because you were solving the problem the wrong way. Also, #1 can often be done in parallel while others solidify the feature requirements more, or supply important assets like graphics comps, branding, copy, etc.

I don't think you're aware of this, so even though I think I'm stating the obvious, I'll do it anyways. Here it goes:

Passion != fun

That's a failure, certainly, but calling it the 'main failure' is a bit of a hyperbole, IMO.

Can the cores be clocked down individually?