They missed the fact that RackSpace offers hybrid cloud options that Amazon just can't match at this point. Got IO issues? So did GitHub when they were running on Amazon's infrastructure. Know how they solved it? They moved to Rackspace and married the cloud for front-end with physical hardware for their IO intense workloads. It seems to me these guys may just be naive. They've probably only sidestepped their problems for now.

You think a massive influx of government spending is a good thing? That's where massive deficits come from since the government always spends beyond its income/revenues and "stimulus" spending is always borrowed money on top of the normal budget. The problem is that we've created a culture where we think we can spend our way out of problems. We do it at a personal level thinking: well I can always declare bankruptcy if I rack up too much debt and don't get that promotion/new job/whatever. And we've now done it on governmental levels from the municipality up to the national stage.

What we are facing is a debt crisis that needs to be dealt with soon. We need to stop new spending, stabilize taxes for the time being and then start taking a hard look at the numbers and figure out how to reduce the national debt load. That may mean increases in taxes for everybody (not just those making over $250k), but a faster way would be to cut spending and allocate the difference to paying the people we owe the money to.

Both Republicans and Democrats have been part of the problem. We need to run all the idiots out on a rail and elect replacements who are fiscally conservative first and foremost and are willing to lay any other issues aside until we fix the problem our government has with borrowing way more than it can sustain.

At this stage are there any objections to simply unseating every single encumbent? Certainly a large influx of "freshmen" to the halls of congress couldn't make matters any worse.

The second session of the United States Congress established 14 year Copyright terms with an optional 14 year renewal. Going back to that and requiring publication for application of Copyright would be a good step.

Sorry for the error, I spend most of my time on the New Testament and got mixed up.

The oldest complete Old Testment dates to the medieval period. The oldest complete manuscripts of a single book are part of the Dead Sea Scrolls which date to the second or third century AD. There are pieces of OT books in artifacts that are from the BC period, but not much.

We, honestly, know a lot more about the NT than we do the OT because of the larger manuscript collection.

The additional books are typical for this period of church history. In the fourth century the church was hashing out the canon of Scripture as evidenced by Sinaiticus, Vaticanus and the various letters that circulated from church leaders discussing the issue. What is more interesting is that Sinaiticus doesn't exclude any of the now recognized books, it only adds to the list. And never mind that certain Christians still hold that these other books are at least useful if not wholly inspired works. If you take the historical context into account your "discrepancies" and objections are not nearly as substantial, especially if you entertain the idea that God works through the processes of history.

The text of Sinaiticus has been reviewed by scholars already and is part of the critical apparatus used to construct the UBS and NA modern Greek texts of the New Testament. Never mind that we also have manuscripts of individual books that predate even Sinaiticus by 200 years. This is an interesting development in terms of making the text more broadly available, but the impact of Sinaiticus on the actual translations we use today has already happened.

From the standpoint of textual criticism and biblical translation this is a non-story. From the standpoint of broad accessibility this is a great development. Remember that serious scholars have been able to get facsimiles for this text for years...

Yes, ignore one of the constraints. In my opinion, trying to satisfy everyone all the time is just stupid. I prefer the approach of "just do it right" and when you do screw up and do it wrong "just fix it." This runs contrary to so many attitudes in the world of browsers and even the wider world of FOSS which want to maintain "legacy support" even if it costs us progress. Transition periods will occur naturally as people upgrade and migrate on their own time tables. Web designers/developers will participate in the transition period via their designs and solutions to the transitional issues. Browser makers should focus more on making their browsers better not figuring out how to smooth the transition which when you're talking about multiple rendering modes and other solutions of that sort really just cause the software to get bloated and harder to maintain, and that isn't going to help us progress either.