iterion1

You should open-source this, would love to be able to contribute!

Could also be 'surprising'. With the context of the sentence before it is basically, "I thought this would be hard to write. Ruby is surprising."

Also, the author is a contributor to ruby on github, so I doubt he is negative towards the language.

http://jisho.org/words?jap=%E6%81%90%E3%82%8D%E3%81%97%E3%81...

Your case, while very valid, doesn't address the original author's concerns related to implementing the tests. In that case I feel as if it's equivalent to using GOTO in my tests. But worse, my labels are regex.

We use cucumber extensively, our cucumber suite is not really that large, and with each new feature it becomes harder to maintain. There has to be some middle ground out there.

If attention to detail is a problem, switching to Android is not a solution. Also, this is the very first release in a massive redesign, things get missed. I'll be concerned if Apple doesn't do anything to improve from this point.

Can we add "I'm switching to iOS 7 from Android"

Or, am I the only one?

I think the writer presumes that BitCoin can't be audited. Which, I think, is a very false presumption. It isn't currently, and it should be. The best outcome for BitCoin is that it becomes second legal tender (with all the auditing and rules that go with it). This will increase competition with other currencies (and their systems) which is a good thing, IMO.

True, but 3D plans for the AR-15 are also easy to find online. Which, I suppose, is a point I should have included.

So, this attracts the ire of the state department. Yet, something like this (http://aresarmor.com/store/Item/TACMHL15) is actually approved by the ATF as not being a firearm. You just need some basic machining skills (thanks MIT OpenCourseWare) and access to basic tools (thanks local hackerspace) to have a fully operational AR-15 which does not need to be registered.

Seriously?

I feel bad that I read this while waiting for tests to run. My tolerance for staring at the screen goes down exponentially as the run time of a task increases. And, I think, even staring at the screen allows my mind to wander and lose some of my momentum.

While I agree that it's a problem, reducing waiting is the best solution for me.

An important proof of concept though. Securing such a system would be a lot of work, and they've started the work for you.

The difficulty I see is getting this to be accepted. My approach would be to focus on local governments, homeowner associations, or other such decision making bodies. Prove the technology there then start pushing for use at a larger level, e.g. county level.