stephenjudkins
I don't know how this claim could be verified in our lifetimes.
Facebook uses Blu-ray discs with a robotic storage system for its cold storage: http://www.datacenterdynamics.com/it-networks/robot-digs-thr...
HTTP/2 Is Done
This doesn't solve your problem of the $250/room cost, but if you'd like to use some other thermostats in your rooms this would work great.
The only complaint I'd have about mine is that the relay is very loud. You might want to search for a quieter one.
Software projects have an inherent bias towards unpredictability
Programming and Reasoning with Algebraic Effects and Dependent Types
Spire - Powerful new number types and numeric abstractions for Scala
Approximately $5.1B of Samsung's profits came from their phones; this is despite Samsung being an extremely diversified company. I cannot find what proportion of Apple's profits come from sales of iPhone and iPads; they do, however, make up a majority of their revenue.
Scala 2.10.0 RC1 released
The preferred method, for iOS apps at least, seems to be use reference counting. This implies that any objects with cyclical references will not be released. Thus, the semantics of this approach will be subtly different than that all JVMs, which have GCs which can detect cyclical references. Thus, the documentation suggests using "runtime and tool support to detect memory leaks".
It's a shame, but given the amount that Azul has poured into research it is not surprising.
At least we can look forward to some interesting benchmarks and code analyses, perhaps?
Azul JVM Now Available For Developers of Open Source Applications
As far as crafting input to match allocated addresses, that is an interesting idea. One could, at the very least, create data that lies within the heap's address range. The issue is, you'd need a lot of data to blacklist a significant amount of memory, and if that's the case why not just DoS with a ton of data?
In practice, a fragmented heap is probably a much bigger issue than actual leaks. As the article points out, a conservative GC cannot perform compaction.
Managed dependencies in Scala using Git
One major cause of the problem seems to be that Scala is stuck with the "precompiled bytecode in JARs" model of software distribution; while this may be appropriate for Java (where core developers go through great pains to maintain compatibility between versions) it seems like a poor fit for Scala. Not only do the core library APIs change between versions, but the conventions used by the compiler to "link" Scala code together are also altered, for good reason.
An alternative distribution mechanism that's more resistant to these kinds of issues might make sense. Even just distributing source code and build files (like, say, Ruby) could be a better solution. Building dependencies might be slow at first, but centralized caching could address this. Another solution might be an intermediate representation (after type-checking and other compiler phases, but before "linking") that gives the Scala compiler the knowledge that's missing from compiled class files.
Even namespace-mangling or class-loader magic could be helpful here. Loading multiple versions of a single dependency should in theory be possible, since OSGi manages it.
Sadly, there seems to be a pretty large investment by the Scala community in the whole Java/Maven/JAR ecosystem. It'd take a concerted effort by many people to create a more robust solution.
However, like all the Twitter Scala libraries, it's currently stuck at 2.8.1 (2.9.0, the next version, was released May 2001). Most new Scala libraries are only being released for 2.9.x, meaning that most developers are forced to make a choice between using Twitter's libraries or other, newer ones.
Further, there are several outstanding pull requests on GitHub to add 2.9.1 support. It was relatively trivial to update the libraries to 2.9.1, but they're not getting integrated. I haven't gotten any feedback about when these might get merged, or why Twitter is stuck on 2.8.1. I've heard through third parties that this is due to problems with Java interoperability with 2.9.1. Also, the custom SBT plugins used seem to, for some reason, break SBT's ability to cross-build.
Unlike with Ruby gems, using forked dependencies is non-trivial.
I intend to keep using Scala. This problem, however, is representative of the relative lack of maturity of the Scala ecosystem. I hope and anticipate this will be resolved in the future. As of now, they represent real problems that get in the way of delivering working code.
Macro vs. Micro Optimisation
Obviously Intel (once led by Andy Grove, author of "Only the Paranoid Survive") is aware of the threat posed by ARM. If someone could explain how Intel will fail to meet the challenges of getting x86's performance-per-watt to match ARM's, and how this compares to the challenges ARM vendors face in order to get raw performance up to Intel's level, I would love to read it. However, this post offers little such insight.
"Note that if W + R > ReplicationFactor, where W is the number of nodes to block for on write, and R the number to block for on reads, you will have strongly consistent behavior; that is, readers will always see the most recent write."
Could you explain why this is incorrect? It seems the Cassandra devs use the definition of "consistency" from Brewer's paper, and Cassandra offers this level of consistency.
Your point about read-repair is correct when using QUORUM consistency level, but even then you can avoid that by using the ALL consistency level.
There is a general misconception that the an entire DBMS must pick tradeoffs based on the CAP theorem. (IE, you can use a database that offers availability, but can NEVER offer immediate consistency) Instead, a DBMS may offer different CAP guarantees per operation.
The likely situation is that the US will pay down its debt through a combination of spending cuts and tax hikes. But there is no doubt that the tax hikes will be substantial.
I believe we're in a pretty poisonous political environment, where the dominant strategy for a politician seems to be to convince your constituents that they're being taken advantage of. Most people who benefit from government programs don't realize it (see http://economix.blogs.nytimes.com/2011/02/11/keep-your-gover...), and most voters have an incredibly skewed view of what, exactly, the government spends money on. When polled, voters oppose cuts to almost every major program.
That the median voter has largely incoherent views on the budget, but is very angry about it, leads us right into our current mess.
To my original point: OP's argument is big on righteous indignation, along with a narrative that allows him to cast himself as a "good guy" and short on actual facts to how to dig our way out of this mess.
* He largely ignores the potential for a catastrophic financial collapse in 2008-2009. At the time, pretty much everyone agreed that stopping the bleeding was a good idea. Among economists, that some sort of vigorous action was necessary is close to a consensus view. To completely dismiss this is ridiculous. Further, he doesn't address how expensive TARP actually ended up being, or that the majority of the money has been paid back.
* The funds weren't obtained from "new taxes levied on employed, middle class, non-drinkers who have never set foot in Heidi’s bar." There has been no increase in federal income taxes since Obama took office. The only meaningful tax increases that I can recall come as part of the Affordable Care Act.
* The author makes no concrete arguments for why no changes to financial regulations are unnecessary. Instead, there's a glib aside that the 'government also announces a series of regulations to “fix” the problem'. Really? This is important. Tell us why. If the government had stopped banks from selling Heidi's bonds as AAA-rated securities, wouldn't this crisis have not happened?
Overall, this is a simple, facile metaphor with many implicit assumptions, designed to bolster the author's libertarian worldview. To the author's credit, he does a good job explaining the fundamentals of the housing crisis.