sah
Joined 18 years ago
Karma
1,374
Submissions
326
Member since
Mar 4
Recent submissions
Comment · 13 years ago
Cucumber does indeed work. We just added an example: https://github.com/appium/appium/tree/master/sample-code/exa...
Comment · 14 years ago
The quoted statement was hyperbole. I followed it with as much nuance as I felt it made sense to get into in the broader context of the article.
Comment · 14 years ago
"If you don't like it, it must be because you haven't taken the time to understand it" is cognitive poison. What evidence will convince you that someone has understood well enough to judge that something doesn't make sense?
I've spent many years using schemas, and I know well how they work and what they achieve. I'm saying they're a lousy tradeoff.
Comment · 14 years ago
I didn't say anything about domain-specificity.
My primary point was just that SQL is old, and I think the reason it is the way it is has more to do with history and compatibility than what we'd want it to look like if we started from scratch today.
SQL is still around because it was successful. And there are reasons to value compatibility, and to avoid changing things for no reason. But my personal experience using a database without using SQL was pleasant, and I'm anxious to see the world move on to something new and improved.
Comment · 14 years ago
You're right that I was lumping transactions and data integrity guarantees in with "relational". I was thinking about normalization, and protecting data integrity in ways that lead to joins and transactions.
Comment · 14 years ago
"They don't exist, if you don't construct SQL queries by concatenating strings and variables."
My point is, people still do this. You never hear about REST-injection or memcached-injection attacks, even though those are possible in principle, because those protocols don't encourage this mistake the way using SQL as a database API does.
Comment · 14 years ago
We keep things we might need to search in regular columns (typically with indexes). The JSON object is just a way to add extra data to rows, which we can fetch and deal with on the app side. That works fine for a lot of things, and we're hoping it will give us some flexibility around when we need to do schema migrations in some cases.
Comment · 14 years ago
The connection I see is the attempt to make the syntax English-like. Expressions like "SELECT * FROM users" remind me of COBOL's "ADD X TO Y".
Comment · 14 years ago
A number of us know MySQL fairly well, and in particular I've seen how it's used by some of the biggest internet companies. We have some postgres experience on our team as well, but it's a little more of an unknown. So experience trumped feature set in this case.
One thing I would say about postgres is that it has a lot of features. As a new user, it's hard to know which ones to use in which ways, and what the downsides might be.
Comment · 15 years ago
I'm one of the authors of a Python framework called monocle for doing async programming in this style. It works with twisted and tornado. http://github.com/saucelabs/monocle
YouTube videos: https://www.youtube.com/user/hackerdashery
My twitter feed: http://twitter.com/sahazel
My website: http://awesame.org/
Side projects: http://codepad.org/ http://omgaudio.com/incoherence/