I've also experienced some production issues with Realm. I've been using it for an App Store mac app since before 1.0 (Quite risky, yes, but it's for a simple use case). In the worst cases, it caused data corruption for end users.
Over the past year, it's become a lot more stable and I've seen far fewer user reported issues with it. As others have pointed out, it's also a very nice API and very simple to get set up.
The Realm team has also been very helpful in my experience and usually have responded to my support requests almost immediately, despite the fact I'm using their free product and not the DB-as-a-service they recently shipped.
I wouldn't take exception to it's stability if they didn't call it ACID compliant. I was about to use it in a setting where failure to be ACID complaint would be fairly expensive (but not safety critical). In just 24hrs of testing I managed to end up with a corrupt DB. In the same tests SQLite's been running for almost a year without corruption...
Scientific journals don't necessarily fund research, and groups who fund research don't necessarily benefit from proceeds from journal subscriptions. Funding scientific research isn't as simple as, say, funding startups. A vast majority of scientific research, especially basic research, yields no returns on investment.
The real issue people have with the way journals work is that they seemingly don't provide a great deal of value. Imagine if GitHub worked like a science journal: You would submit your code to GitHub. They might have someone do a code review or run some tests to assure a baseline level of quality. Then they would lock your repository and charge anyone who wanted to see more than just the readme file $30 - $50. All of the proceeds from that go directly to GitHub. You, the author of the repository, get nothing.
A software developer simply would not tolerate this model, but it's the norm in science.
Sports Illustrated (si.com) is hiring a senior front-end developer in New York (NYC) to help us improve our SPA and front-end tooling. We use coffeescript, backbone, grunt for builds and mocha for testing. Looking for someone who's comfortable with the stack and enjoys having lots of autonomy.
Drop an email here if interested careers@timeinc.com
Over the past year, it's become a lot more stable and I've seen far fewer user reported issues with it. As others have pointed out, it's also a very nice API and very simple to get set up.
The Realm team has also been very helpful in my experience and usually have responded to my support requests almost immediately, despite the fact I'm using their free product and not the DB-as-a-service they recently shipped.